Hi Joe,

What is possible, if you see an error with saving changes in the Plugin is,

if you for example added an "Separate DB connection" in the Plugin settings

and if for some reason the "Connection Test" is failing for it,

or if there are blank credentials, like in my screenshot here :

In that case, any changes in the Plugin settings you try would fail;

Our devs are working on fixing this in one of the future updates,

I can't say an exact ETA,

but you can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

For the time being, we have to make sure, if we add any Additional DB Connection here to check if the "Test DB settings" return as 'success' ,

if not - you will have to remove the additional connection which has an issue,

then you should be able to change any Plugin settings.

-

Let me know if that was the case?

Thank you.

Hi Joe,

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.

Thank you for that update with the new details you found.

Yes. I believe there is some kind of a permissions issue with how your Hosting set up your WordPress SQL Database.

It seems our Plugin does not have the full permission there to make the tables it needs in order to properly function.

In the moment when you install and activate our Plugin, then some new Tables need to be made in your WP Database.

Our Plugin usually creates them automatically when the WP Database permissions are correctly set.

The most important Table is the wp_wpdatatables.

But please note , the wp_ prefix is the default WP DB prefix, on your Site it could be anything else.

So it is best to check what is your current WP DB prefix.

For that, you can either install a Plugin Brozzme DB Prefix, which can show you what is the current WordPress DB prefix;

or you can log in your DB and check directly.

-

This indicates that there is some kind of a configuration/permissions issue on your 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 your WP Database.

We advise if you can please reach out to your Hosting Support ( that holds that Database) and to ask them if they can make sure that your Database User ( and the WordPress and our Plugin) has the full/correct permissions on the Database, in order to create new Tables?

We have tested this on our own Test Sites and we can confirm that it is not a bug - so the issue does not come from our Plugin.

*Just a small disclaimer : I am not a developer, so I am not 100% sure of the exact terminology used for these Database Permissions - But from the Support experience I do my best to guide you to isolate the issue/when it does not come from our Plugin.

For now, I can only say the issue is coming from some bad permissions on the WP Database.

Let me know what the Hosting Support says - and we can go from there to see if we can provide additional advice/what you could try next, etc.

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

Just note, on the first line where it says :

CREATE TABLE `wp_wpdatatables`

You would change the wp_ to your WP Database SQL Table prefix, so it would be :

CREATE TABLE `YourPrefix_wpdatatables`

Let me know how it goes.

Thank you.

Hi Joe,

Do you know, did your WordPress Database Prefix change at any point recently?

Was it always wp_af54k5_  and still the same, or was it maybe that before, and now it changed to a new Prefix?

Can you please install the Plugin Brozzme DB Prefix and then, go to  "Tools/DB Prefix" and check is your current WP prefix showing as 'wp_af54k5_' or is it a different one?

If it shows a different Prefix as 'existing prefix', that means your DB prefix changed and now you need to change this in our Plugin's data.

Let me know how that check goes, and if your DB prefix shows correct there, then we will need to investigate it with the help of our developers.

But for safe debugging, we don't wish to mess up anything on your Live Site;

It is best if you can make a separate, Staging version of the Website, then send me the URL to that Site;

and send us Administrator user credentials, along with FTP credentials and access to the PHPMyAdmin. ( It can be URL to PHPMyAdmin with credentials or access to the Hosting panel).

If you send that, just ensure to mark the reply as PRIVATE, then only we can see it.

Thank you.

Hi Joe,

I am glad to see you fixed this issue, at least for now;

but I can see you opened a new ticket for the Table which is freezing.

It could be connected, but not sure yet, at first glance I think it is a different issue, but we will follow up on that one and going to close this case.

Thank you.