Date Period
October 02, 2026
October 01, 2026
insites-cli test run upgrades it automatically on its next run.September 30, 2026
insites-cli env add on the private stack now signs you in through the Insites Console in your browser. Check that the sign-in page shows the code the CLI prints, then approve. You need at least edit access to the instance, and --url is now optional.env add --instance-uuid <uuid> works out which stack the instance is on by itself.--console-tier <tier> option picks the production (default) or staging Console, and --timeout <seconds> stops waiting for the sign-in sooner.env add messages: which stack the instance is on, the sign-in code highlighted, how long the CLI will wait, and the deploy command to run next.env add now saves the stack with each environment, so an instance on a custom domain no longer falls back to the shared stack.September 25, 2026
insites_core's shared admin layout and external CRM activity scripts from EOL 0.x releases to 1.19.0insites_core's dependency partialsupload_restrictions schema and a shared validate_upload function, so file-upload limits are declared once and enforced consistentlycrossorigin to the moment.js tag on the Event Stream viewid alongside uuid and its reference label, on every methodYYYY-MM-DDGET /insites/core/administrators/:uuid now returns 404 for an unknown or malformed uuid instead of 200 with an empty result setadd_event leaking into the response body on 36 unwrapped v2 external API endpoints, and guard it so a blank Event Stream response cannot throw ParseJsonTagErroris_archived: false explicitly on every Contact create path, so new contacts cannot be created in an indeterminate archived stateSeptember 25, 2026
GET /asset/api/v2/assets listing endpoint now requires an instance API key. External integrators must send their instance API key on this endpoint or the request will be rejected.September 24, 2026
September 22, 2026
September 18, 2026
September 16, 2026
Error responses keep the page's content type: A page that sets its content type, from its format or via {% response_headers %}, no longer has an error rendered afterwards re-negotiated against the Accept header. Unrecognised formats render as text/plain, and errors on .js pages return a JSON string literal so the browser never parses an error message as script.
Clear response when an instance has no object storage: Requesting a presigned upload URL used to return nothing, and sync reported a failed fetch. The endpoint now returns 501 with a direct_upload_unavailable error, and the CLI falls back to uploading assets through the instance.
Host-relative asset URLs with local storage: When an instance serves its own assets from disk, asset_url now returns a host-relative URL instead of pointing at a CDN that never received the files, or raising when no asset host is set. Instances using a CDN are unaffected.
Dynamically cached pages without a layout: A page combining dynamic_cache with layout: "" rendered on the first request and then failed on every cache hit. Pages that declare no layout are now served from cache as-is, which fixes cached sitemap.xml pages.
Redundant Liquid context on cache hits: The layout no longer builds a second Liquid context and reparses the layout value on every dynamic cache hit.
Partner Portal URLs on non-default ports: An instance registered against a portal on a non-default port dropped the port, so later token validations went to the default port and surfaced as a plain 401. Local setups and private stacks were affected; production was not.
Swapped exception names in low-level error logs: IP spoofing attempts were logged as missing-parameter errors and vice versa. The 403 and 406 statuses returned were already correct.
September 15, 2026
Filter by
Date Period