Using version 0.6.22
I'm trying to update the Client Settings by requiring email confirmation and requiring certain fields. I'm multi-selecting the fields that the user must fill out when registering. Unfortunately, when I click the Update button, I get a Configuration Saved message but the field selections remain unchanged. I'm getting a lot of bogus signups so any assistance would be appreciated.
Hello,
I am unable to replicate this problem (see the attachments to my post).
I know that the multi-select box can sometimes throw people off, if you aren't already make sure you are holding the control button on your keyboard so that it actually selects multiple items in the list.
Also if you're seeing spam, you might want to enable the "spamchecker" module.
From within it's settings you can enable an integration with StopForumSpam, configure ReCaptcha, and enable functionality that prevents the usage of temporary (disposable) email addresses.
Unfortunately the spamchecker settings aren't being saved in the database, nor the client signup settings. The activity logs reports this:
Updated extension "mod_spamchecker" configuration
Updated extension "mod_client" configuration
Which table(s) is being updated when these settings are saved?
(07-26-2024, 01:56 AM)cryptdoughnut Wrote: Unfortunately the spamchecker settings aren't being saved in the database, nor the client signup settings.
Oh I see.
If memory serves me correctly, the last time I saw this the culprit was an overly aggressive caching layer that was placed between the FOSSBilling instance and the browser.
The updated data was indeed being written, however the aggressive caching meant the previous page content was being sent to the browser, resulting in the visual appearance that nothing was actually being updated.
What's your server setup?
If you check the network tab in your browser, does it give any indication that the page contents were cached?
As for which table it's being written to.. IIRC it's the extension_meta table, however the configurations written there get encrypted so it's not really something you can just go in and edit.
After conducting an investigation, it was determined that the "Salt" value had been modified. Upon reverting the "Salt" back to its original value, normal functionality of both reading and writing encrypted configurations was restored.
