Repository navigation
Let WordPress.com choose the plugin's main screen - #9
Merged
Merged
Conversation
Main_Screen asks public-api.wordpress.com which screen is main, keeps the answer for its ttl, and falls back to BlogVault when it has never had one. Every e2e blueprint answers the endpoint from a must-use plugin. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The sidebar row, the Settings link and the activation redirect lead to the Reprint screen only while the main screen flag says so; otherwise to the BlogVault screen. Both stay reachable at their URLs. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The flag goes by reverting this PR; the markers only added noise. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A deactivation that skips its hooks, as the upgrader's does, left the stored answer in place; activation now clears it too. The fetch no longer follows redirects, each of which would get its own 2 s timeout. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
WordPress.com serves it at wpcom/v2/migration-plugin-config. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The next wp.org release makes the Reprint screen the plugin's main entry point (#7), but the WordPress.com side of the Reprint flow may not be live on release day. This lets WordPress.com decide which screen is main, so the plugin can ship independently: WordPress.com flips to Reprint when its UI is ready, and can flip back without another plugin release.
The flag is temporary. About two weeks after release we revert this PR, and the plugin behaves as trunk does today.
What
Reprint\Main_Screenasks WordPress.com whether the main screen isreprintorblogvault, and caches the answer for the time the server specifies.Testing instructions
public-api.wordpress.comMigrate to WordPress.comlink in the wp-admin sidebar/wp-admin/admin.php?page=wpcom-migration) and not the Reprint screen (/wp-admin/admin.php?page=wpcom-migration-status)🤖 Generated with Claude Code