Make WordPress Core

Opened 3 years ago

Last modified 3 years ago

#53134 new defect (bug)

Keep current URL domain for View Post on View Post link

Reported by: chamois_blanc's profile chamois_blanc Owned by:
Milestone: Awaiting Review Priority: normal
Severity: minor Version: 5.7.1
Component: Editor Keywords:
Focuses: administration Cc:

Description

Hello,

I am using BrowserSync to proxy my remote site to https://localhost:3000 on my local machine through ssh forwarding. I have noticed that the localhost domain name is reverted to my site real domain on the backend for the 'View Post' link, when updating a post using Gutenberg. This behavior does not happen with the classic editor.

It would be great if the 'View Post' link could retain the localhost domain on post update.

Steps to reproduce:
1) Run BrowserSync or equivalent as proxy
2) Open post for edit on backend on localhost domain
3) Check 'View Post' link, it should have localhost as domain
4) Click 'Update' or 'Publish'
5) Check 'View Post' link again and it will now have the site domain instead

Classifying as bug as the behavior deviates from what the classic editor does.

Change History (3)

#1 @SergeyBiryukov
3 years ago

  • Component changed from General to Editor

Hi there, welcome back to WordPress Trac! Thanks for the report.

Could it be because the View Post link in the block editor is updated dynamically, without a page reload? In the classic editor, clicking the Update button did cause a page reload.

#2 @chamois_blanc
3 years ago

  • Summary changed from Feature Request: Keep current URL domain for View Post on View Post link to Keep current URL domain for View Post on View Post link

That's very possible. Wondering if this is maybe a Gutenberg issue instead of WordPress core. Not sure how the two interact at this level.

Note: See TracTickets for help on using tickets.