Closed Ramoonus closed 2 years ago
Cool to see this ticket! Some previous discussion:
I think a good first goal is to ensure versioning the Pods configurations themselves works correctly. A main issue with versioning the configs themselves are dealing with table schema changes, field renaming (meta keys won't match, etc), field deletions (meta values will still be there, table columns/values will still be there).
it will be tough, but a huge functionality improvement
FYI - I'm already storing dumps of my entire WP dev installation in git and dumping changes into the dump in branches. So may be able to give some insight into handling Pods config changes via git...
I am using Pods for my projects, so I started to play with VersionPress support.
podsrel
table and related entities to start tracking data and it seems that it also works, but I will test also renaming fields, etc (PR incoming).Some related questions:
test-relation-field
there are 2 similar postmeta with ID values _pods_test-relation-field
(serialized value) and test-relation-field
(simple value). I am not sure about the second one (there is no prefix), is this postmeta important?old_name
is changed, but when I change it once again, there is no relation to previous name (and that is why mentioned postmeta test-relation-field
will not work correctly)?Nice work @pavelevap! 👍
https://blog.versionpress.net/2017/07/versionpress-4-0-beta/