Hello,

When you are moving on live site from local or stage site (or vice-versa) we can suggest using Plugin Duplicator. We use it and it's working fine because it will transfer all the files and also the tables to the database. 

Other than cloning the site, another option would be to copy all database tables (wp_wpdatatable_#) along with tables wp_wpdatatables, wp_wpdatacharts, wp_wpdatatables_rows and wp_wpdatatables_columns. Then, in wp_options table, you would also need to export the following option_names:

• wdtPreventDeletingTables
• wdtUseSeparateCon
• wdtSeparateCon
• wdtTimepickerRange
• wdtTimeFormat
• wdtTabletWidth
• wdtTablesPerPage
• wdtSumFunctionsLabel
• wdtRenderFilter
• wdtRenderCharts
• wdtIncludeBootstrap
• wdtIncludeBootstrapBackEnd
• wdtPreventDeletingTables
• wdtParseShortcodes
• wdtNumbersAlign
• wdtBorderRemoval
• wdtBorderRemovalHeader
• wdtNumberFormat
• wdtMobileWidth
• wdtMinifiedJs
• wdtMinFunctionsLabel
• wdtMaxFunctionsLabel
• wdtLeftOffset
• wdtTopOffset
• wdtInterfaceLanguage
• wdtGeneratedTablesCount
• wdtFontColorSettings
• wdtDecimalPlaces
• wdtCSVDelimiter
• wdtDateFormat
• wdtCustomJs
• wdtCustomCss
• wdtBaseSkin
• wdtAvgFunctionsLabel
• wdtInstallDate
• wdtRatingDiv
• wdtMDNewsDiv
• wdtTempFutureDate

It is rather cumbersome to do all this, but unfortunately at the moment, it's the only way. 

Important to note, for tables linked to an existing data source, you would need to change the file path, because at the moment the file path depends on the domain, so if you change the domain, the URL to the file will also have to be changed.

Our developers will be working on adding an easier solution to export everything, but we can't say an ETA on this.

- There are also certain export functionalities, to export individual tables using Table Tools.

- If you also need to switch domains;

 In our store you can go to "My Licenses" and click on the "Manage Domains" button:

From there, you will be able to deactivate the old domain (while it's still active), and then simply activate the new domain in wpDataTables settings/Activation, once you move the site.

I hope that helps. 

Let me know if you have any additional questions about that.

Hi Ricardo,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

1. If i understand, you do not wish to move/migrate the entire cloned Site, but you are just trying to manually copy only our Plugin's Data to the other Site?

2. You use a Separate DB connection for your SQL Query Tables, if i understood.

Is it exactly the same DB Connection as you were using on your 'old Site' or do you need to modify the SQL DB Connection parameters and a different Connection Name?

If you need to change the DB Connection, but your old SQL Tables still 'memorized' the old Connection details;

Here is what you can try.

For each table, during creation we have to manually select the DB connection from the dropdown;

and the only way to change that after the tables were already made by our plugin,

is to go in the database where your WordPress is,

there find our plugin's database table named 'wp_wpdatatables'.

( the wp_  is the default WordPress Database table prefix,   on your site's database that table prefix might be different, but it should be easy to recognise, all tables would have the same DB prefix,

so check for "yourTablePrefix_wpdatatables")

This table holds the details and settings for each table from our plugin.

If you wish to sort it by table type, you can hit the Header of column 'table_type' and just look for 'mysql' type tables,

or you can do a "search" on wp_wpdatatables to only show this table type.

Then check under the "connection" column, here the "external DB connection" name is set.

You can edit that field for all MySQL tables you need from our plugin and change the DB connection name.

Under the "content" Column of the wp_wpdatatables, you will also see the SQL Query used for each table,

and of course, in the ID field, it will show each wpDataTable's ID,  as they would show on the Shortcodes.

Here is an example screenshot from a user's database that has two different external DB Connections and how that looks in the table's data :

So, first make sure that you add this external DB Connection in your actual Main Plugin Settings/Separate DB connection, and try to use the same Connection Name as you had on the 'old Site', this way you will maybe not need to edit anything in the Database wp_wpdatatables Table.

Insert all the Connection Details, then do a Test if the connection works.

If that works - hit "Save Changes" and, refresh your "Browse Tables", check if they load now.

-

If your Tables still say "unknown Connection" for the selected DB Connection, then you will also need to do the step explained above, edit this detail in the Database, and let us know how it goes.

Thanks.

Hi Ricardo,

First, please check under your Main Plugin Settings/Separate DB connection/Connection Name :

If you named your Connection, as you said as "Clouding", then just make sure that the "Test connection" works.

If that is successful, hit "Save Changes" on top right.

-

Now, you need to go in your PHPMyAdmin, and run an SQL Query that will update your 'connection' Column for the wp_wpdatatables  Table.

As mentioned before, the wp_ is the default WP Prefix, but i see on your screenshot, you have wptg_ as the Table prefix ( i apologise if i did not write it correctly looking from the image/ that is why it's best to highlight the table, then copy and paste it to avoid any typo).

UPDATE `wp_wpdatatables` SET content=REPLACE(connection,'your Old Connection Name','Your New Connection Name')

So, copy this 'current' Connection name, what it says in the field, as the "old connection";

and for the new one, write your new Connection name, i suppose as "Clouding", but make sure to check how it is written in the actual Connection name settings.

Let me know if that works.

-

If not, we can remotely help, but we need access :

Please provide me a temporary WP-admin (administrator) user for your website where this happens, 

as well as FTP credentials and access to the database ( either link with credentials for PHPmyAdmin, or access to Hosting Panel),

so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Thank you.

Hi Ricardo,

My apologies once again for taking so long between replies.

Thank you for the screenshots, i can see, it seems this is not just an issue of the SQL Connection, but it seems there is a bigger issue for the Plugin files/ looks that maybe the Plugin files are not fully copied over from the old to the new Site.

Can we log in remotely and we take a look?

But for safe troubleshooting, if you can make a separate Staging Site and move all the same Data there;

Then send me the URL to the Staging Site,

along with WP-admin (Administrator) user, 

FTP credentials ,

 and the database access ( URL with credentials for PHPMyAdmin or access to Hosting Panel), so our developers can debug the plugin, and see what's going on?

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Thank you.

Hi Ricardo,

No problem about your delayed response, you can always take your time.

I sincerely apologise now once again for my end's late reply.

Thank you for passing all the details. We are passing this to our QA Team and the Developers - it might help them when they work on easier way to automate the migration of the Plugin with options for the future.

Thanks again, and of course, I am happy to see you managed to find a solution for migrating the data in your use-case with the Separate connection details.

If anything else comes up, please don't hesitate to open new tickets.