Duplicate into the same database

that would cause issues because you would be duplicating data, and it would cause more trouble than it was worth.

I don’t understand, isn’t that the purpose of this plugin? I have several websites running on one database without any issues.

Hi Ewout,

The plugin uses a generated dump sql file of your database when you create the package. The dump file is a snapshot in time with only the data you had in your DB at that exact point.

So when you go to create a new database or connect to an existing one, that data that is used is unique and should not be mingled with other data because the plugin is not capable of handling different versions of your data…

Hope that helps!

Thanks for explaining. So if I duplicate a wordpress site that is in a database it also copies all the tables from other wordpress sites? I still don’t really see how there are ‘different versions’ of my data, since it’s just as if I would install another site on that db right?

The data becomes different because when you create a package its all from that point in time. So if you add new posts, get comments or change any settings then the data becomes different from the package that was made.

Also the plugin does not merge or append data. It creates brand new tables with each install. So if you had a table named wp_posts then it would overwrite that table with the new data.

Hope that helps!

Isn’t that always the case no matter what db you are using? As long as the table prefixe
s are different, they have become two completely separate installs (which is the reason for duplicating in the first place). So you’d have two (or more) installs on the db, each with their own tables:

• db1 > wp_posts
• db1 > wpbeta_posts
• db1 > anotherwp_posts
• etc

instead of

• db1 > wp_posts
• db2 > wp_posts
• db3 > wp_posts
• etc.

This is default wordpress functionality, since it will ask you which prefix to use on install, which is why it’s possible to have multiple installs (each with their own data) on the same db.

Either way, thanks for explaining, I guess I’ll just have to create another db :o)

Hi Ewout,

Yes your correct if you were creating brand new tables that currently don’t exist then your scenario would be true. This might be a feature in the future… Possibly something like ‘ignore existing tables’

Thanks

Thanks! I think letting the user define a new prefix (on export or on import) would make more sense, especially if I’m going to duplicate into the same db. My duplicated install would then be wp_ and the new something like dupewp_

Thanks for this great plugin and excellent support!

Good suggestion and thanks for the feeback!

Just wanted to report here that I noticed that if you duplicate a site that’s on a shared database with multiple wordpress installs, it copies all tables from the other installs (with different table prefixes) too.

Thanks for the update @ewout…

it is one of the best plug in i found, and that will be a really great feature if you allow user to add a prefix in future.