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

Converting legacy keys to new format #19

Closed
mvirenius opened this issue May 31, 2017 · 1 comment
Closed

Converting legacy keys to new format #19

mvirenius opened this issue May 31, 2017 · 1 comment

Comments

@mvirenius
Copy link

How can I convert a legacy key to the new 2.0 compatible format?

I would be nice to have a single function, which takes old key as a parameter and returns a new key.

@atanas-dev
Copy link

atanas-dev commented Jun 1, 2017

Hi @mikkovirenius

Currently we do not have a migration script for legacy data, however, we have a Legacy Storage Service bundled which dynamically loads old data and converts it to the new format (all in memory - no changes are made to your database) so if your datastores do not find any data in the new format it will fallback to whatever old data can be found.
Once you edit a post/theme option/term etc. the data will be stored in the new format.

The downside of this approach being that some old data may be left over and old data that is not updated will not be usable in some of the new features of 2.0 (e.g. complex meta queries).

EDIT:
I'll close this ticket since this is the docs repo rather than the main CF repo.

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

2 participants