Rewrite scoped URLs when importing a Playground export #2989
+435
−7
Conversation
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
When exporting a Playground and restoring it in a different scope, image and media URLs break because they still reference the original scope path segment (e.g., /scope:abc123/). This change fixes that by recording the site URL at export time and replacing it during import. The export now includes a playground-export.json manifest containing the site URL. During import, if the old URL differs from the new one, we run SQL UPDATE queries to replace all occurrences across wp_posts, wp_postmeta, wp_options, wp_usermeta, wp_termmeta, and wp_comments tables.
Inline the manifest filename constant and remove the exported interface. When the manifest file is missing (legacy exports), infer the old site URL from the database by querying the siteurl option directly with SQL.
adamziel
added
[Type] Enhancement
When importing a Playground export into a different scope, we now replace just the /scope:xyz/ path segment rather than the entire site URL. This is more targeted and avoids accidentally replacing URL substrings that happen to match but aren't scope-related.
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.
Summary
When exporting a Playground and restoring it in a different browser tab or session, image and media URLs break because they still reference the original scope path segment (e.g.,
/scope:abc123/). This change fixes that by recording the site URL at export time and replacing it during import.playground-export.jsonmanifest containing the site URLwp_posts,wp_postmeta,wp_options,wp_usermeta,wp_termmeta, andwp_commentstablesThis is a simple approach using SQL REPLACE queries that handles the ASCII-based scope pattern (
/scope:xxx/) reliably. It can be upgraded to use the WordPress-importer URL rewriting pipeline once it's reusable outside of the WXR import pipeline.Fixes #2982
Test plan
npx nx test playground-blueprints --testFile=import-wordpress-files.spec.ts