Hi Giuliano,

This usually happens if a user changes their domain name - or migrates all the data to another site/database;

or if you changed your WordPress Database table prefix.

Can you tell me, did our Plugin work before and you were able to make tables, etc - then this started happening after some time?

If so - did you do any changes to your site or database as advised above?

I will advise how you can fix it, to change our Plugin's database prefix - so it will 'match' your new DB table prefix going forward.
And also if you use linked tables like CSV/Excel etc, as additional advice.

First, to check what is the "new path" for tables on your new site,

you can create a new table linked to any Excel file ( or CSV file), and it should generate just fine. 

Once you do that, access your database, and open 'wp_wpdatatables' database table.

( the wp_ prefix is default WordPress Database table prefix, on your site it might be different)

In the "content" column, you will see the path related to the new table. 

So, if the new file is stored in (for example):

/var/www/html/your_NEW_site/wp-content/uploads/2021/02/file-one.xls

And your old files are in:

/var/www/html/your_OLD_site/wp-content/uploads/2021/02/file-two.xls

You need to modify the content column for each row, and replace the path.

To do that, you can run this SQL command on your database ( via your database management tool, such as PHPMyAdmin):

UPDATE `wp_wpdatatables` SET content=REPLACE(content,'this_part','that_part')

Please bear in mind that wp_ is the default prefix of WordPress, 

but on your site it could be anything, so you should run `your_prefix_wpdatatables` and actually replace the part of the path in "this_part" and "that_part" sections.

Additional step if you have Manual Tables, then most probably you also have a different SQL Database Table Prefix now on your new Site.

If you can access directly to your Database, via PHPMyAdmin or any other DB Management Tool ( you can ask your hosting support if you're not sure how to access it);

then you can run this Query on your Database, in order to update to your current DB Table Prefix in our Plugin's data:

UPDATE `wp_wpdatatables` SET mysql_table_name=REPLACE(mysql_table_name,'wp_','NewDBPrefix_');

Please bear in mind that wp_ is the default table prefix of WordPress,

 but on your old and new site it could be anything, so check what is your DB table prefix,

then you should run `your_prefix_wpdatatables` and actually replace the part of the path in wp_" and "xyz_" sections.

That replaces the prefix in the "mysql_table_name" column. 

Once you do this, you should be able to simply load all your manual tables without issues.

-

If you're unsure how to do this, we can do it for you if you can provide me with a temporary WP-Admin user (administrator) credentials, 

and database (phpMyAdmin) URL with access credentials.

If you send us access, just mark the reply as PRIVATE, so it is safe, then only we can see it.

I hope that helps.

Hi Giuliano,

It would be very helpful for other users who might experience the same issue, if you could perhaps try to provide a summary of some major 'points'/steps you did to determine the root of that issue and what you have changed to provide the needed permissions.

I presume that perhaps our Plugin did not have the right permissions to read/write data in your WordPress SQL Database, so during the installation it was unable/blocked from creating our Plugin's tables needed for it to function?

@Henrik, 
Yes, you probably have the same issue. This is very rare to happen, and usually it has something to do with wrong permission configuration on the WP Hosting database - something prevents our Plugin from creating the tables it needs in the database.

The most important table it needs is the wp_wpdatatables.

Please note : wp_ is the default WordPress DB table prefix - on your Site it can be anything else, so it would be named 'yourDBprefix_wpdatatables'.

I will share some advice we have from the last user's ticket who had a similar issue like this, I hope this might shed some light on the matter :

We got this SQL Query from our Developers - it is used to manually create the wp_wpdatatables table in the Database;

When I run this Query on my Server/Site in PHPMyAdmin, it works and it creates the wp_wpdatatables.

But in that situation, for the user's WP Database ( the user who had this issue), when we tried it, there were the following errors.

MySQL said: 

#4109 - Failed to generate invisible primary key. Auto-increment column already exists.

I am sending you the SQL Query ( which is used to create the said table) here as a zipped file.

3. After that, we installed the WP PhPMyAdmin Plugin on the user's Site just to try what happens that way.

We tried to go in the PhPMyAdmin from this Plugin, another error appears :

'phpMyAdmin - Error 

Wrong permissions on configuration file, should not be world writable!'

This indicates that there is some kind of a configuration/permissions issue on the Hosting Server Side for that Database.

It seems some write/read permissions are not correct, which are needed for our Plugin to create new Tables in the WP Database.

If you have the same issues as shown here - I advise if you can please reach out to your WordPress Hosting Support have them fix the permissions, your WordPress and Plugins need to have full permission to create Tables in the WordPress SQL Database.

I hope that helps. 

We will be here to provide advice as much as our Support can cover.

Thank you.