Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Payload 2.0 Migration Path #50

Open
timofei-iatsenko opened this issue Oct 13, 2023 · 0 comments
Open

Payload 2.0 Migration Path #50

timofei-iatsenko opened this issue Oct 13, 2023 · 0 comments

Comments

@timofei-iatsenko
Copy link

We've used this plugin in our PayloadCMS setup. Now we want to upgrade to Payload 2.0 but we've blocked by this plugin.
The application just crashes when the plugin is included somewhere in the code, the issue is like here

So we decided to migrate to Payload's native lexical support.

I've found that data structure stored into the field in DB is pretty similar, but not the same. Payload 2.0 saves jsonContent directly into the field, where this plugin has an additional level in a structure.

I prepared a migration script which is going across all collections & globals and update field values accordingly, check this out here https://gist.github.com/thekip/eff1611f7957360be400c9ad23a83330

Unfortunately, after migrating the DB i've found that Payload's implementation is not that functional as in this plugin. It doesn't support Tables which we used and probably some other features, i did not test them all. But if your integration with lexical used only default set of features you would be good to go with my migration.

I'm continuing investigating...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant