Support » Plugin: NS Cloner - Site Copier » Creates unnecessary tables

  • Thoughtlessly creates tables with the prefix of a child site, including those plugins that do not support multisite. That is, it takes all tables and adds the site prefix to them. Thus, useless unnecessary tables appear in the database. Tried another similar plugin, there is no such problem, so the problem is with this plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Never Settle

    (@neversettle)

    @5qwert5 would you provide the names of the tables so we could improve the plugin? We do already exclude all the core WP multisite tables and a number of plugin-specific tables, but there are a lot of plugins out there and no standard way to detect tables that should vs. shouldn’t be cloned to child sites, so it requires maintaining a hardcoded list (which always has some possibilities for expansion), and we in part depend on users like you to inform us tables that should be added. So a suggestion or support ticket is always an option and is appreciated over leaving a negative review right away 🙂

    Thread Starter 5qwert5

    (@5qwert5)

    For example WP-Recall. There were more, but I don’t remember, I tested it a month ago. Why can’t you do it differently? For example, there is a child site with id2, it has 10 tables with the wp_2 prefix. When cloning, create 10 copies of these tables with the prefix wp_3. I manually cloned the child site this way and everything works fine, you can also do it with a plugin.

    Plugin Author Never Settle

    (@neversettle)

    That’s actually the way that it is intended to work (and currently is for everyone else as far as I’m aware). If cloning the main site (prefix wp_) it uses the predefined list to skip WP and plugin tables that are known to be multisite only (like wp_blogs) and copies all the other tables starting with just wp_ and no number following to wp_2 or whatever the new child site’s prefix is. Then if cloning a child site, it copies all plugins starting with wp_2 to wp_3 (or whatever the new site prefix is) as described.

    Anyway as mentioned we haven’t had anybody else report the issue you experienced, so there might have been something unique going on with your environment in some way. It sounds like you moved on and found another solution, but if you wanted to try the NS Cloner again with debug logging enabled and send us the log when finished at support@neversettle.it we could always take a quick look at it.

    Thread Starter 5qwert5

    (@5qwert5)

    But why use a predefined list? You can’t cover all plugins anyway. There are 10 tables with the prefix wp_2, you need to copy all these 10 tables and you will get 10 tables with wp_3. No more, no less.

    If the plugin has a table without a prefix, then you do not need to copy this table and add a prefix to it. And for some reason your plugin does it. You just don’t need to do this, then you don’t need a predefined list.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Creates unnecessary tables’ is closed to new replies.