Cross-site replication
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 53
- Forks
- 38
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
yes
Describe the solution you'd like
I have a formally running WordPress site. For safety reasons, I installed the same WordPress configuration locally. When publishing a post, I need to publish it on the local server first, and then publish the same post on the formal server after confirming that there are no errors after a few days. This reduces the impact on the formal server.
Why do you think this feature is something we should consider for the Yoast SEO plugins?
Because there is no such function.
Additional context
Because the local server and the official server have exactly the same configuration, including the same page editor and content, the clone must be exactly the same as the original site. This is the true meaning of cloning.
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
The issue names no files, tests, or entry points. Start by reviewing the duplicate-post plugin’s current scope and the WordPress requirements for cross-site replication, then clarify whether staged post publishing or full-site cloning is required. Done needs explicit acceptance criteria for synchronization, safety, and matching site state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100