Yoast / Yoast/duplicate-post

Rewrite and Republish feature displays permalink field in editor, but this field is not used

Open
#437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
53
Forks
38
Avg merge
4d 8h
Merged PRs (30d)
1

Description

  • I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened

A user created a rewritten post using "rewrite and republish", but then didn't publish the rewritten post because they thought it would be at the wrong URL. The rewritten post's editor showed a permalink that didn't match the original URL, so it wasn't clear that the draft rewrite would replace the original.

To Reproduce
Step-by-step reproduction instructions
  1. Create a post and set its permalink. Publish it.
  2. Use the "Rewrite and Republish" functionality to create a draft rewrite
  3. Edit the draft rewrite.
Expected results

I expected either of the following:

  1. The editor in the rewritten post should display no permalink controls
  2. The editor in the rewritten post should display the same permalink as the post it is a rewrite of
Actual results
  1. The editor in the rewritten post shows a control for setting the permalink, and this contains a value that is not the value of the original post.
Screenshots, screen recording, code snippet

If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.

Technical info
  • If relevant, which editor is affected (or editors):
  • Block Editor
  • Gutenberg Editor
  • Classic Editor
  • Other:
  • Which browser is affected (or browsers):
  • Chrome
  • Firefox
  • Safari
  • Other: All
Used versions
  • Device you are using: Laptop, desktop
  • Operating system: Any
  • PHP version: 8.2
  • WordPress version: 6.9
  • WordPress Theme: custom
  • Yoast Duplicate Post version: 4.5
  • Relevant plugins in case of a bug:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue through the WordPress Block Editor or Gutenberg Editor using Rewrite and Republish, then trace the editor entry point that renders the permalink control. Done means the rewritten draft either hides permalink controls or shows the original post's permalink, with the behavior verified against the reported steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.