Repository navigation
feat(explorer): stage and remove-from-staging selected item (#4546) - #4551
Merged
Merged
Conversation
Editor/Admin can Stage and Remove from Staging a selected page or asset from Content Explorer (same kind rules as Publish Now / Take Down). HTTP 200 FORBIDDEN / BADCONFIG / NOSTAGING_SERVERS is not success. Parent: #4530. > Co-Authored by Grok Build 1.0.34 using grok-4.6 with agent night-issue-prs.
This was referenced Sep 17, 2026
natechadwick
approved these changes
Sep 18, 2026
Collaborator
Author
|
Human QA handoff: #4553 assigned to @vijaya-boddipudi (
|
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Content Explorer slice 2 of parent #4530: an Editor/Admin can Stage and Remove from Staging a selected page or asset from the React Explorer toolbar/context menu.
Follows the Publish Now / Take Down peer (
itemPublish.ts+actionDispatch.ts): confirm,resolvePublishKind(folders/templates stay unavailable), injected Finder actions (CX catalogs omit them), classic sitemanage GETs (/publish/page|resource/staging/{id}and/takedown/page|resource/staging/{id}), andmapPublishResponseso HTTP 200FORBIDDEN/BADCONFIG/NOSTAGING_SERVERSis an error, not success.Out of scope: schedule dates (#4547/#4535), Take Down (already #4533/#4545), PublishingShell history (#4536–#4538 / PR #4549). Duplicate filing #4534 is not a second PR.
Operator: Grok: night-issue-prs (model grok-4.6)
Fixes #4546
Parent: #4530
Test plan
python docker/scripts/perc-devctl.py qa-upthenqa-healthwithQA_CMS_HOST_PORTfrom qa-up stdout (this run:http://127.0.0.1:9993).python docker/scripts/perc-devctl.py qa-deploy-webui;qa-healthagain.spa.jsp?entry=explorer). Confirm Stage / Remove from Staging appear; they stay hidden on Sites/folders.npm run test:surface -- --path tests/explorer-action-dispatch.spec.js(FORBIDDEN / NOSTAGING intercepts) andnpm run test:golden.FORBIDDEN/NOSTAGING_SERVERSshows Server actions error and does not refresh as success.Checklist
product-docs/8.2/admin/content-explorer.md(Stage / Remove from Staging rows)mvnw clean installonWebUIandmodules/perc-qa-automationexplorer-action-dispatch.spec.js@explorer-staging+ golden smokefinal/API shape change)C3 evidence
WebUI,modules/perc-qa-automationcd WebUI && JAVA_HOME=/usr/lib/jvm/java-21-openjdk ../mvnw clean install→ BUILD SUCCESS (Surefire Tests run: 69, Failures: 0; Vitest Test Files 443 passed, Tests 4289 passed)cd modules/perc-qa-automation && JAVA_HOME=/usr/lib/jvm/java-21-openjdk ../../mvnw clean install→ BUILD SUCCESS (npm ci; no Java tests)final/public Java API change)C5 UI proof
python docker/scripts/perc-devctl.py qa-up→TEST_CMS_URL=http://127.0.0.1:9993QA_CONTAINER=perc-matrix-cms-h2RESULT:OK STEP:qa-health HTTP:200 HEALTH:healthy URL:http://127.0.0.1:9993/Rhythmyx/rest/mimetypespython docker/scripts/perc-devctl.py qa-deploy-webui→RESULT:OK; qa-health againRESULT:OKnpm run test:surface -- --path tests/explorer-action-dispatch.spec.js→ 5 passed (including Stage FORBIDDEN and Remove from Staging NOSTAGING_SERVERS);npm run test:golden→ 2 passedpageerrorlisteners empty on staging tests)RESULT:OK(this agent owned the cell)