Skip to content

Justflows 0.4.1

Choose a tag to compare

@NOOBBase NOOBBase released this 09 Nov 11:21
13e1d55

[0.4.1]

Added

  • Content can be restricted by role, by user, or by a plugin rule. A content type can set a default visibility rule and an entry can override it for all its translations, with allow and deny lists and a Check access tool that shows which rule decided. A hidden entry answers 404 and is left out of lists, totals, search, menus, sitemaps, feeds, and exports, and pages with a rule are never cached or exported. Plugins add rule types with ctx.visibility.registerRule in SDK 0.1.8. A rule that is missing, fails, or gives an invalid answer denies. Files in a hidden entry stay reachable at their direct URLs. (#283)
  • Security regressions run against real shared databases. CI now exercises prior-to-current schema upgrades, durable job claims across workers, transactional quota-style concurrency, and plugin schema upgrades on PostgreSQL and MySQL. The focused test:security command also covers upload admission, media/storage reservations, image jobs, durable job failure handling, and the trusted-proxy boundary. (#268)
  • CI fails on a committed credential, and a release needs a valid SBOM. The security job runs the tracked-file secret scan, and packaging stops if the SBOM is missing, describes another version, or omits a direct dependency. (#267)
  • Operators have an incident response guide and an extension trust reference. The guide covers evidence, containment, trusted reinstall, secret rotation, restore, and notification. The reference states what SDK permissions and signatures constrain, what same-process code can still reach, and that untrusted extensions are not supported. SECURITY.md now states the supported versions and how reports are handled. (#198)
  • A plugin update that adds permissions needs an administrator's approval. Upload, Marketplace install, and manual updates show the new permissions and stop before the installed version is replaced. Approvals are recorded in the audit log, and automatic updates wait for a manual update instead of adding permissions on their own. (#261)
  • The installation root can back up and restore its sites independently. Admin → Tools creates one portable file for the root site or a separate file for every subsite in its workspace, reading each site through its owning database without crossing tenant boundaries. A validated file can be restored into the selected root site or subsite without changing other sites. Existing media is staged for rollback, database replacement is transactional, and failed restoration puts the target site's previous media back. (#257)
  • Backup jobs can deliver archives to FTP/FTPS, email, or an external S3-compatible bucket. Admin → Tools stores destination credentials encrypted, never returns them to the browser or includes them in portable archives, and reports delivery failures. Email attachments are limited to 10 MB; larger backups remain available through local download, FTP, or S3. (#19)
  • Admin Tools can create, validate, and restore a portable site backup. The cancellable backup job reports progress and produces database-independent JSON with a versioned manifest, SHA-256 integrity checking, content and design configuration, plugin/theme inventory, and original media from local or S3 storage. Missing media stops creation instead of producing an incomplete backup. Restore is limited to a clean target, preserves its administrator and secrets, rewrites site ownership, stages media, and rolls back database and staged-file changes on failure. (#256)
  • Security Center reports backup evidence. Backup readiness now shows automatic backup state on the installation root and warns about a failed or stalled schedule. It never passes on a created backup alone. A new guide covers archive protection, recovery objectives, and restore drills. (#265)
  • Shop fetches Stripe payment methods automatically. Payments settings can activate or deactivate overridable methods on the current test or live Stripe account and provide proper controls for checkout, capture, subscriptions, wallets, fraud handling, and Radar review behavior. Active methods are individual checkout choices with bundled logos and constrain Stripe to the selected method; Apple Pay and Google Pay stay inside Stripe's express-wallet flow.
  • Security Center checks installed versions against signed advisories. The feed is verified against the pinned release key on every read. A tampered, replayed, expired, or unreachable feed shows as unknown rather than clear, and a withdrawn version shows as a failure with a recovery path that keeps site data. (#262)
  • Shop handles Stripe refunds, disputes, and Radar signals. Refunds carry Stripe reasons and Shop metadata and reconcile failed webhooks; disputes expose deadlines and accept evidence uploads/submission; orders show Radar risk, early fraud warnings, and reviews, with optional auto-refund and capture blocking. Dispute submission is also available as a capability-protected agent tool. (#240)
  • The security program has a published threat model, release runbook, and extension review requirements. They cover actors and trust boundaries, the path from private report to advisory with release evidence, and what a Marketplace listing does and does not mean. (#258, #263, #266)
  • Shop manages Stripe webhook endpoints and replay. Stripe linking registers the exact supported event list and securely stores rotating signing secrets. The idempotent inbox hydrates sparse events, covers payments through Connect/payout lifecycle events, exposes failed deliveries for admin replay, and reports webhook failures in Diagnostics. (#239)
  • Shop subscriptions can use Stripe Billing. Sites can choose Shop-managed off-session renewals or Stripe Billing for new subscriptions. Billing mode synchronizes catalog and promotion objects, supports trials, quantities, prorations and Customer Portal, and drives Shop renewal orders and subscription states from signed Stripe webhooks without duplicate scheduling or dunning. (#238)
  • Shop customers can save Stripe payment methods. A signed-in customer's first Stripe checkout creates and attaches the per-site test or live Stripe Customer with their current profile and billing address. Card checkout has an explicit save-for-later choice, SetupIntents let customers add or remove reusable methods, safe card details appear in customer and admin views, and subscription renewals can charge off session with SCA recovery. Customer export and deletion cover the Stripe mapping. (#237)
  • Shop supports Stripe's regional and delayed methods. Eligible local bank methods, SEPA Direct Debit, and buy-now-pay-later methods appear through Stripe based on currency and billing country. Delayed payments stay pending until a signed webhook succeeds or fails, and SEPA mandates are disclosed and recorded. (#236)
  • Shop supports Stripe express wallets. Stripe Payment Element checkout can show Apple Pay, Google Pay, and Link through Express Checkout, and Payments settings can register the site's wallet domain in test and live mode. Wallet orders use the same webhook-authoritative lifecycle as card orders. (#235)
  • Shop offers Stripe Checkout and Payment Links. A shop can use hosted or embedded Stripe Checkout instead of Payment Element, with exact order totals and webhook-driven completion. Staff can issue a fixed one-off Stripe Payment Link for a named customer's unpaid order. (#234)
  • Concurrent file integrity scans share one run. Requests that arrive during a scan wait for its result instead of hashing every installed tree again. Route tests now cover who can read and run Security Center checks. (#264)
  • Shop accepts Stripe Payment Element checkout. Stripe.js keeps card details off the Justflows server, supports SCA/3DS and configurable payment methods, and offers automatic or manual capture. Signed Stripe webhooks remain authoritative for paid orders. (#233)
  • Shop Stripe payments have a reliable API foundation. The Shop plugin can create and read Stripe PaymentIntents and safely reconcile, capture, void, and refund them through a pinned, idempotent Stripe client with bounded retries and typed provider failures. (#232)
  • A plugin can have its own sidebar section. Menu items with domain: "plugin" are listed in a section for that plugin, above Extensions. adminSection in the manifest names it and sets its icon, which can be an emoji or an image from the plugin's admin app. (#146)
  • A plugin can add a card to Platform → Workspace. workspacePanels in the manifest embeds a plugin admin screen there, and the admin bridge passes workspaceId. (#146)
  • A content editor section can embed a plugin admin screen. An editorPanels entry with app shows that screen for the entry being edited, including a draft, and the admin bridge passes contentId. (#146)
  • Plugins hear about new comments. The comments.created action runs when a visitor or moderator comment is stored as pending or approved. Spam and trash do not run it. It carries ids and the status, but no email, IP address, or comment text. (#146)
  • A website's Features list can turn a plugin off. A plugin that registers the website flag <plugin id>.enabled gets a switch; off hides that plugin's admin pages on the website. A flag registered with whenUnset: "off" stays off until a plan or an operator turns it on. (#146)
  • A hosted site can read its plugin's main-site secrets. ctx.network.mainSiteSecrets reads them, so a subsite can use a connection the main site saved. It cannot write them. (#146)
  • A plugin admin screen can use the whole content area. bridge.setLayout("fill") keeps the sidebar and section tabs and gives the frame the rest. A sidebar section icon can be an image. (#146)
  • SDK: plugin blocks load their own scripts and styles only where they are used. assets.blocks in a plugin manifest maps one of the plugin's block types to scripts and stylesheets, and assets.markup does the same for pages containing given markup (#id, .class, .class-prefix*, or [attribute]), such as a page the plugin fills through an HTML block. The host adds them only to pages that render that block or contain that markup, including in the header, footer, or a widget area, with content-hashed URLs that browsers cache for good. Per-page stylesheets are linked before /theme.css, so the theme and Additional CSS still override them. (#195)
  • Themes load block-specific code only where it is used. assets.blocks in justflows-theme.json maps any block type, core or plugin, to scripts and stylesheets that load only on pages rendering that block. They are served with content-hashed URLs that browsers cache for good, and only declared files are reachable. (#195)

Fixed

  • User administration fails closed at the site boundary. Reading, updating, or deleting a user from another site returns not found and leaves that account unchanged; display-name-only updates no longer report success or emit update side effects for an inaccessible account. (#259)
  • Client-IP controls trust named proxies instead of path positions. TRUST_PROXY now accepts false, named ranges, and explicit addresses/subnets, while ignoring true and numeric hop counts that can become spoofable when request paths have different lengths. A site still configured with one of those values boots on loopback, logs a warning, and passes the Security Center check with a note that the value is ignored, so updating never takes it offline and asks nothing of the operator. A proxy on another machine still needs its address set, or visitors appear as that proxy. A resource-limit matrix documents which throttles, uploads, quotas, image jobs, and background jobs are database-shared or intentionally per process, including bounded failure behavior and real-database verification commands. (#260)
  • Extension updates cannot silently downgrade installed code. Manual and automatic Marketplace update paths now refuse an equal or older SemVer before downloading the archive. The extension trust guide documents fail-closed registry behavior, signing-key rotation and revocation, and the deliberate recovery path for a withdrawn release. (#261)
  • Platform signup settings keep the separate database. Opening Admin → Platform from the menu showed Current database until the page was refreshed, and saving there moved new signups onto the installation database. The form now shows the stored choice, and a save that leaves the choice out keeps it.
  • Stripe checkout retries reuse the failed order. Retrying the same cart after a failed Stripe payment updates the existing order and payment row instead of creating a duplicate. Newly created or action-required PaymentIntents remain pending until Stripe reports success or an actual failure, and Stripe webhook amounts remain in minor units so successful payments reconcile instead of staying pending. Stock reserved by a failed order stays available to its cart's retry but not to other shoppers. Successful payments empty their cart and clear its retry pointer, including legacy orders and repeated notifications, so later purchases are not blocked. Payment timelines and documents use the actual gateway instead of a Mollie fallback; processing or authorized provider payments remain protected from replacement. (#233)
  • Plugin installs and updates work on a release install. A release runs the server as one bundled file, and the installer looked for its archive worker next to that file, where it was missing, so every .jfpkg install or update stopped with "Archive processing failed". The bundle now ships the worker files beside it, a hosting build copies them into the installer too, and the server log records why a worker fails. (#208)
  • A translation keeps the dates of the entry it translates. A new translation takes its group's creation date, and when it is published for the first time it takes the group's publish date, so every language shows the same date in lists, feeds, and on the page. Migration 0052_translation_group_dates gives existing translations their group's dates and leaves updated_at alone.
  • A workspace page shows its limits panel once. The limits editor and plugin workspace panels now keep distinct identities while navigating between workspaces. (#23)
  • A subsite's Security Center shows only checks that belong to that site. Installation details such as the Node.js version, core updates, debug mode, the install wizard, session-cookie policy, public URL, trusted proxy, file integrity, and web-server setup stay on the main site. (#198)
  • The Security Center opens a focused security event view. Administrators can review site-scoped authentication, MFA, session, API key, privilege, extension, update, integrity, and security-configuration events without unrelated content activity. The server enforces the event category and keeps the complete audit trail available separately. (#251)
  • Security event email alerts are opt-in per site. Administrators can send the site's administration address a redacted alert for high-value authentication, privilege, API-key, extension, update, integrity, and security-configuration events. Audit rows provide a durable cross-worker delivery claim, alerts are capped at ten per site per hour, attempts and failures use the existing email delivery log, and in-app events remain available when mail is disabled or unavailable. (#252)
  • Security events have an explicit lifecycle. A Settings button on the audit log opens a dedicated page for email notifications and retention controls. Administrators can export up to 5,000 redacted site-scoped events, apply the configured retention window, or permanently delete security events with an exact confirmation phrase while retaining a count-only deletion marker. Audit storage is bounded per site, write failures are visible, and the interface documents that local logs are not tamper-proof and do not yet provide an external sink. (#253)
  • Self-hosting security guidance covers the full deployment boundary. Operators get verified guidance for TLS and public URLs, explicit proxy trust, edge-origin restrictions, least-privilege OS/database/object-storage access, secret rotation, supported runtime updates, writable directories, and Docker, nginx, Apache/LiteSpeed, Passenger, and direct-Node differences, plus an external verification checklist. (#254)
  • Edge protection has a provider-neutral integration guide. Operators can place a CDN, WAF, bot layer, or DDoS service in front of Justflows with explicit origin lockdown, proxy trust, cache exclusions, route-aware WAF and bot policy, upload/WebSocket handling, privacy-safe evidence, failure and rollback decisions, synthetic verification, and a supported no-paid-provider baseline. Application throttling is explicitly not presented as upstream capacity protection. (#255)

Changed

  • The admin loads only the code the open screen needs. Every admin screen is its own download, fetched the first time you open it, and the page builder, math formulas, and animations load only with the screens that use them. Opening the dashboard now downloads about 154 KB of compressed JavaScript instead of 546 KB, in 5 requests instead of 10, and the screen keeps its server-rendered content while the rest loads. (#195)
  • Public pages load only the scripts they use, and browsers keep them. A page gets the menu, notice, sign-in, animation, and interactive-block scripts only when it contains that markup, so a plain page loads 1 KB of core script instead of 8 KB, and the math formula stylesheet loads only on pages with a formula. Only the colour-scheme script still runs before the page shows; the menu and notice scripts no longer hold up the first paint. Core scripts, theme.css, and theme.js use content-versioned URLs that browsers cache for good, so a repeat visit makes no revalidation requests for them, and theme.js is left out when the theme has no scripts. A page cached before an update still gets working scripts. (#195)
  • Core no longer names any plugin. The Helpdesk and Shared files sidebar groups are gone; a plugin gets its own section with the plugin menu domain and adminSection. A menu domain the host does not know falls back to Extensions instead of stopping activation. Core's catalogs no longer carry Shop menu labels or product block strings, the menu editor labels plugin content types with their own names, and the default theme's contact page uses an email button instead of a plugin form. ctx.ai.complete takes the plugin's own system role; core keeps only the rule that the text is data. (#146)
  • A signed release archive includes a core file manifest. The archive lists the files an update replaces, and an update can check those files after it copies them. Uploads, storage, themes, plugins, and installed extensions stay out of that manifest. An installation without the manifest stays unverified. (#120)