Hi Julo,

To begin, I want to extend my heartfelt apologies for the delayed reply, 

which is due to an unexpectedly high volume of inquiries. 

-

Can you tell me do you just have that one additional Separate DB Connection in the Main Plugin settings,

or do you have more than one there?

Basically, this issue happens if we have "Separate DB connection" enabled, but without any DB connection credentials, 

then the settings will have issues getting saved when making changes.

-

Also, if you create a separate DB connection, but if the connection credentials are not correct,

in that case you would also have issues.

-

But if you add a separate DB connection, and hit "Test connection" such as in your case

- if the connection works with the correct credentials,

then you should not have any issues like this and all settings you change should get saved when you hit "Save Changes".

Can you please double-check do you have more than one External DB Connection set up,

and do all of them return a success when you try to Test the Connection with our Plugin?

If any of them gives an error, that will be an issue.

For the moment, whenever you hit "Save Changes" in the Plugin, it tests all your additional DB connections and if one of them fails, the issue happens.

So, see if you have all of your Connection Details written down somewhere,

then you could delete any Connection that causes an error ,  then try to save just this one External DB Connection by Testing it , then hit "save Changes", refresh the Page and see if it gets saved after that?

I know this is not ideal, our developers are working to fix this behaviour by adding a new logic that will only check for each DB connection individually when "Saving Changes".

Let me know if that helps.

Hi Julo,

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.

-

I found one very strange detail in your Video.

At the start, i notice that the Separate DB connection ( Use Separate DB connection) option is checked/enabled, but for some reason the credentials beneath are completely blank.

So, you first have to click in "Add New Connection" in order to  'reveal' the fields for the credentials of that Database Connection input.

It should not be like that.

A screenshot how it looks for me - If i enable to "Use separate connection" , i don't have to go to "Add New Connection",  it rather already brings up all the credentials input fields for the Connection name, Vendor, password, etc.

We did not see an issue like that before, but it seems that on your installation, it has somehow "saved" a  "blank Additional DB Connection" without any credentials;

So now when you hit "add a new one" - it does add another, additional DB Connection and when you do "Test Connection" , for that second one it works - but the first/original Connection somehow gets saved as with blank credentials, and i believe this is the root of the issue.

I propose to try these steps :

First completely remove using the Additional DB Connection, uncheck it and hit "Save Changes" on top right.

After that, please check do you have the latest wpDataTables Plugin version 6.0.

If you have some older version, please update it.

If you activated the purchase code in wpDataTables Settings/Activation, the update should be offered in the Plugins section. On some WordPress installations, you need to deactivate the plugin first in order to see the update offered, so please try that.

If that doesn't work, try going through Dashboard/Updates. See if you can update the plugin through there, and if that doesn't work either, you can follow the manual update procedures explained in this Article :

Updating the plugin to the latest version.

After this ( if you update, or if you already have the 6.0 Plugin version), please purge all cache on your Site.

Then, refresh the Page and now click to enable the "Use Separate DB connection" setting.

This time, it should offer you all the input fields for that DB Connection right away - without having to hit "Add a new connection".

Now, input all the connection details exactly as you did before, and try "Test DB settings" to check if it works.

After this, if the Test is successful, wait a couple of seconds, for that floating notification to go away, that says "Connection Test OK" - and hit "Save Changes" for the Plugin on top right - and check does it say "Success! Plugin settings saved successfully" as on my screenshot :

If you see that, now try again to check going to any other Tab, then coming back here - and it should become saved.

I hope that works - and sorry to see this inconvenience happen, our developers are working to make improvements on how all these settings are saved, and to add improved 'error handling' notifications in future updates.