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

Update method that keeps the VPIDs #906

borekb opened this Issue Apr 11, 2016 · 1 comment


None yet
2 participants
Copy link

borekb commented Apr 11, 2016

Currently, the only reliable method to update between VP releases is to deactivate the plugin, upload the new version and re-activate. This unfortunately makes a thick line between the current and previous installations of VersionPress – all connection to the past is lost, VPIDs are re-generated, INI files created from scratch, etc. This is because the INI format still changes between releases and migrations are hard, see #275.

Until we have proper migrations, or until the format stabilizes so that we don't really need to change it, there could be a simpler method for the meantime: keep the wp_vp_id table, and when re-generating INI files from scratch, use this table to assign the same VPIDs to the newly created entities. This would have two main benefits:

  1. I'd be able to track history of e.g. a post between VP activations.
  2. Changes in INI files are usually quite small so reusing the same file would save a lot of data in Git repository. (Currently, all the files are deleted and new ones created, which is a big waste if there is a vast amount of entities.)

@borekb borekb added this to the 3.0 milestone Apr 11, 2016


This comment has been minimized.

Copy link

borekb commented Apr 11, 2016

I'd personally find this very useful and the effort required could be quite reasonable so I'm assigning it to the 3.0 milestone; we'll re-schedule if there's not enough time to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment