Hi Joshua,

can you please check,

when you go in the main Plugin settings and change the Maximum functions label,

and press "save changes" at the bottom right,

do you see the message as "Success , plugin saved this correctly",

or do you see any kind of error in the upper right corner when you try to save changes?

I also attached a Video of our test, we are not able to reproduce the issue.

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,

then you should be able to change any Plugin settings.

-

Let me know if that was the case?

Thank you.

Hi Joshua,

My sincere apologies - In the meantime we figured out why this happens.

Basically, if you use any 'password manager' directly in your Browser, like for Google Chrome, it has the 'saved passwords'.

This saves the username and password as the browser's cookie information.

That is a security issue, and for the time being, in our Plugin, in the Max function label - it is always going to pull your Admin username there as the "max function label".

Here is a screenshot from my LocalHost Site, where 'root' is the Admin username.

Our developers will do their best to try and somehow improve this - but that is basically, not an issue coming from our Plugin itself - it is rather how the WordPress handles these passwords for that specific functionality;

A solution is to use something like the "BitWarden", which we use for storing credentials ( username and passwords information).

So if you switch to something like BitWarden, then remove any passwords and username you got saved in your Browser's cookie like "password manager' or similar;

and then it will stop showing there as the Admin username in your "Max function label" by default.

I will still double-check about all this with our QA Team and the developers, if we make any progress, we will report back to let you know as soon as possible, but for the time being, that is the only secure way.

Thank you.