Using editor commands on sites with the Default view active results to a 404 redirection

[jimjasson]

Quick summary

When the Default view is used for pages and someone creates a new page and uses CMD + K to navigate to "Single Posts", they they get redirected to a 404 page.

Steps to reproduce

1. Set up a new Creator site.
2. Navigate to the Pages tab.
3. Select the Default View.
4. Create a new page.
5. Click CMD + K.
6. Select "Single Posts".
7. See the 404 error.

What you expected to happen

I expect to be redirected to the template as expected.

What actually happened

I am redirected to a 404 page.

Impact

All

Available workarounds?

No and the platform is unusable

Platform (Simple and/or Atomic)

No response

Logs or notes

I can replicate this issue both on Creator and Woo Express sites.

Here's a short video:

T6wZRV.mp4

[rickmgithub]

📌 REPRODUCTION RESULTS

VIDEO:
Please see video provided by OP

STEPS TO REPLICATE

• Set up a new Creator site.

• Navigate to the Pages tab.

• Select the Default View.

• Create a new page.

• Select blank template

• Click CMD + K.

• Select "Single Posts".

• Get the "refused to connect" error.

• Tested on Simple – Replicated

• Tested on Atomic – Replicated

📌 ACTIONS

Triaged

[lsl]

The nested iframe isn't able to navigate the top level page, we need the URL to be swapped with a wpcom one similar to what we do for other wp-admin urls:

wp-calypso/apps/wpcom-block-editor/src/calypso/features/iframe-bridge-server.js

Lines 706 to 710 in 955b956

	const manageReusableBlocksAnchorElem = popoverSlot.querySelector(
	'a[href$="site-editor.php?path=%2Fpatterns"]'
	);
	const manageNavigationMenusAnchorElem = popoverSlot.querySelector(
	'a[href$="edit.php?post_type=wp_navigation"]'

[inaikem]

@mmtr 👍

[obenland]

@inaikem @mmtr What's the status on this? Why is this a blocker?

[lsl]

Not a blocker. High maybe. Was hoping this would have been fixed by the editor iframe removal by now 😬

[mmtr]

What's the status on this?

@xavier-lc was working on a fix and already merged, but don't know if's been shipped. Xavier, can you confirm?

Why is this a blocker?

@ianstewart flagged it as a blocker on the last Dotcom Triage Group session. Every navigation issue (i.e. you click on something and you don't land on the expected place), including commands from the command palette, should be considered critical issues.

[mmtr]

Looks like @xavier-lc forgot to deploy the changes, and @lsl did that today (D164295-code), so we can close this one out.

[lsl]

I was still seeing this in production after deploying that change. Maybe a Firefox only issue now or something?

[xavier-lc]

Tha nks for the deploy, @lsl. With I was still seeing this in production after deploying that change you mean you can still reproduce the error? I've just checked on brave and firefox and it worked.

[lsl]

Yes. Might be a browser cache/setting, can't repro on mobile. Will look into it more tomorrow.

[mmtr]

@lsl note that the wpcom-block-editor scripts are cached for 24h, so you might still be loading the old ones.

[xavier-lc]

I've found that pressing the ENTER key on the commands wasn't working properly, here's the fix: #95575

[lsl]

so you might still be loading the old ones.

I invalidated those, p1729574805314119/1729487009.644859-slack-CRWCHQGUB I think I must have been using the enter key 😄