Added migration code and pipelines to migrate Magento pages to Statamic#189
Open
indykoning wants to merge 1 commit intofeature/statamic-6from
Open
Added migration code and pipelines to migrate Magento pages to Statamic#189indykoning wants to merge 1 commit intofeature/statamic-6from
indykoning wants to merge 1 commit intofeature/statamic-6from
Conversation
kevinmeijer97
approved these changes
Apr 30, 2026
Member
|
Let's wait for the Statamic v6 PR, when that's merged we can merge this one. |
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.
This PR adds the ability to migrate HTML into Statamic bard fields.
As an example (since every Magento and Statamic installation has them) a cms pages to statamic pages migration command has been added using this migration.
Making use of pipelines for most of the HTML transformations so the migration and transformation process can be customized to a customer's needs.
e.g. currently iframes are transformed into urls, since Statamic does not support iframes in bard.
If a user has a fieldset for iframes, the
TransformIframescould be removed. And a custom step for turning it into an iframe fieldset could be used instead.