The "sticky" setting doesn't get copied when used classic editor
Open
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
To Reproduce
Step-by-step reproduction instructions
- Enable classic editor
- Create a post, set this to sticky, and publish it
- Then try to use the Rewrite and Republish
Expected results
- The edit screen should have sticky enabled since the original post had been set to sticky.
Actual results
- Sticky checkbox is empty when editing in Rewrite and Republish.
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:
Used versions
- Device you are using: MacBook pro
- Operating system: Sonoma 14.5
- PHP version: 8.0.0
- WordPress version: 6.5.5
- WordPress Theme: Twenty Twenty Four
- Yoast Duplicate Post version: 4.5
- Gutenberg plugin version: N/A
- Classic Editor plugin version: 1.6.3
- Relevant plugins in case of a bug:
Classic editor
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through the Classic Editor: create and publish a sticky post, then use Rewrite and Republish. Trace how the sticky setting is handled in that flow; the work is done when the edit screen retains the original post's sticky state.
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
- Clearly specified
- Newbie friendliness
- 48/100