Post Link Doesn't Conform to Permalink Settings

[dlim_vernier]

The link shown in the sidebar is incorrect/incomplete if I have a custom permalink structure. The link shown only shows the postname only.

I have one site that uses the post ID as the link URL and it is obscured when the author types in a title. They can only figure out the true URL by previewing the post or understanding that the post ID is in the editor URL.

Another site I work on has the post ID prefixed to the post title. The editor sidebar only shows the post title but the full URL does include the post ID prefix.

[dlim_vernier]

Screenshot of Post Link using permalink structure and not

[hellofromTonya]

Hello @dlim_vernier,

Welcome back to WordPress Core's Trac.

I'm doing triage today for bugs reported on 6.6.1 or 6.6.2 (i.e. via Version) and then updating ticket information.

Resetting the Version, as 6.6.1 did not change the code reported in this ticket. Once the root cause is found, then the Version can be updated with the WordPress version that introduced the bug.

[hellofromTonya]

In testing the Page UI in the Inspector on different versions:

• <= 6.5.5: shows "URL' which has the full link.
• >= 6.6.0: replaces "URL" with "Link", which shows only the slug, rather than the absolute path.

Setting the Version to 6.6. Looking at the issues in Gutenberg (e.g. ​this example and ​this one), I'm wondering if it was an intentional design decision for readability due to length.

Pinging @jameskoster (who authored the above examples) and @vcanales (6.6.x co-lead). Is this change by design? Or is it a bug that should be reported upstream in Gutenberg?

[hellofromTonya]

Looking more deeply at the UI, it is by design.

Clicking on "Link" opens the popup which says:

Customize the last part of the URL. ​Learn more.↗

Looking at the ​"Learn more" docs:

{ermalink: Once your post or page is saved as a draft, you can edit the last part of the URL (also called the URL Slug). Depending on your Permalink settings, the URL Slug will be appended to the end of your site’s URL. For example: ​https://example.com/[slug]

Thus, only the slug for the post/page being edited is shown by design as that's the part that can be edited. The absolute URL is shown in the popup box.

Marking this ticket as a close candidate as I'm thinking it's not a bug, but rather a design decision. Will wait for confirmation from the Editor team.

[jameskoster]

Thus, only the slug for the post/page being edited is shown by design as that's the part that can be edited. The absolute URL is shown in the popup box.

That's correct. In the given example the user cannot edit the post id, so it isn't included in the slug field.

[dlim_vernier]

Thanks for the background. While you can see what is editable, it doesn't show what the canonical URL will be without an extra interaction and could mislead users in what the link is for the post from the editor view.

Looking at the ​original issue, the solution seems aimed at pages rather than posts.

[hellofromTonya]

Thanks @jameskoster for confirming.

Thanks for the background. While you can see what is editable, it doesn't show what the canonical URL will be without an extra interaction and could mislead users in what the link is for the post from the editor view.

@dlim_vernier the change and UX are design decisions, rather than a bug.

Looking at the ​original issue, the solution seems aimed at pages rather than posts.

You're right. That particular issue was specifically "polishing" for a "static homepage". The change was already in place before that issue.

As this is a decision decision, closing this ticket. I think its resolution is reported-upstream, as its code is maintained in Gutenberg (not in Core).

@dlim_vernier are you wondering what the next step could be to reopen this design decision for reconsideration? If yes, I'd suggest ​opening an issue in Gutenberg.

Why in Gutenberg? The discussion and resolution will happen in Gutenberg, where the code is maintained and published (via the npm packages).