Skip to content

Add beta Prepublish checks for shared content blocks - #30

Open
MortenFriisSiteImprove wants to merge 3 commits into
mainfrom
feature/shared-block-prepublish-beta
Open

MortenFriisSiteImprove wants to merge 3 commits into
mainfrom
feature/shared-block-prepublish-beta

Conversation

@MortenFriisSiteImprove

@MortenFriisSiteImprove MortenFriisSiteImprove commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Shared blocks need their own draft checks before review and approval. The plugin now clears the previous page context, offers only Prepublish for a shared block, and captures its current same-origin HTML preview as a fragment. Returning to a page restores the usual page context and tabs.

Requires Latest UI, existing Prepublish access and a customer-provided block preview template. Supports visible Preview mode and All Properties capture; inline blocks, media, missing templates and cross-origin/headless previews without a bridge are outside this beta.

Current main is integrated, including the admin redirect and regional-language URL/fallback fixes. The project retains main's 4.3.5 development version and manual-only release-candidate workflow. Block regressions and regional routing tests are both retained. The merge resolves the project-version and testing-document conflicts.

Validation

Integration commit: d30ee7775ec54d3e72f4632847317da8d0166f0f.

All required GitHub checks passed:

  • Backend/browser workflow: 85 backend tests on each of .NET 6 and .NET 8, 58 Chromium/Firefox functional checks and 10 blocked-preview observations.
  • Package/CMS workflow: unit and package verification, all 14 CMS scenarios on each of the two locked profiles, and the 4.3.3 package upgrade check. Shared-block regressions and real regional fallback/routing cases run together.
  • Local Node unit checks (20) and Python unit checks (16) also passed after integration.

The PR is conflict-free against current main. Release-candidate execution is manual-only, matching main; publishing a beta tag no longer automatically starts the stable-version release workflow on this branch.

The published 4.3.5-beta.1 remains tied to its original tested commit e6643bc79ef4da7b78a8d02fc24aa46f818dc9cc and SHA-256 47f73c192cb2bf099cfdb4b4d5719517f69cdcd0680d45f41167c31e5bacf28c. Its package, tag and customer ZIP are unchanged by this integration.

That exact beta passed all 8 CMS scenarios on each of UI 12.34.6/Core 12.24.0 and UI 12.32.5/Core 12.22.6, the verified 4.3.3 upgrade, and supporting backend/browser/package checks. Real Siteimprove scans detected and cleared a draft image-alternative issue after autosave and reload. A representative visible Full Width/Restricted Width preview reported speeling as one potential misspelling with two occurrences, highlighted both and cleared it after the saved correction. These were local reproductions, not the customer's deployment.

Customer prerelease, installation/rollback instructions, validation and screenshots: https://github.com/Siteimprove/CMS-plugin-Optimizely/releases/tag/v4.3.5-beta.1

@MortenFriisSiteImprove
MortenFriisSiteImprove marked this pull request as ready for review October 13, 2026 18:49
@MortenFriisSiteImprove
MortenFriisSiteImprove requested a review from a team as a code owner October 13, 2026 18:49

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant