WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I cleaned up an old-site from pasted tags, manually created lists, etc, and I'd like to keep the old posts as "revisions", so we can easily "compare" with the old posts and retrieve/revert the original content if needed.

So I should either injecting the revision rows in the new DB or just naturally create them in the old WP installation, by batch-updating all the posts…

…or starting from the new cleaned-up dev installation and injecting the revisions.

The problem is the old site didn't even use revisions (version 1.6 or 2 or so), so before I even try anything, I should MAKE wordpress to generate the right revisions itself (so the injections just adds content in existing rows, not whole rows with missing references etc)

I know there are several places where the revisions and actual posts are linked/related/referenced so the process should be mostly done by wp functions and the fewer manual DB manipulations.


share|improve this question

It is probably better to upgrade the old installation to a current wp version and reapply the changes. Unless it is a very big site you are probably going to waste more time in researching , coding and debugging an automatic solution then what it will take you to manually edit the posts.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.