I am looking for which part of the UNA code is force setting content filter boxes to be checked after it checks the profiles date of birth field.
I am seeking to modify this so that the boxes are not by default checked, but instead are offered to the user to be checked if the requirements are met for the rating to be offered to the user.
As it stands right now, if someone that is age 21 or over, the following is displayed.
✅G
✅PG
✅PG-13
✅R
✅X
What I desire, by default, when someone who creates a profile that is 21 or over, have the following by default.
✅G
🔲PG
🔲PG-13
🔲R
🔲X
Reason: Not everyone wishes to see such content above their comfort zone right out of the gate, and with age verification laws going into effect, we must start disabling and hiding R and X until a user has paid to have these unlocked, such as purchasing Premium so that a transactional history data is logged to verify age to meet law requirements.
I've already discovered how to hide the options R and X for users, but this doesn't stop the UNA script from automatically checking the boxes upon profile creation....
Disregard this request, after research how this feature was introduced, it seems it is controlled by database input defaults, resolved with the following SQL:
ALTER TABLE `sys_profiles` CHANGE `cfw_value` `cfw_value` INT(10) UNSIGNED NOT NULL DEFAULT '1';For reference on what this does, by default the INT was set to an absurdly high value "2147483647" so it seems like this is a failsafe the devs added in to ensure that at least "G" is on by default, but with it being such a high value, it fell back on the date of birth checks and updates and only then, updates the values to their correct values after the script was done.
In this case, setting cfw_value default to "1" will ensure that G is always selected and nothing else upon profile creation.
Issue: When a user updates their date of birth, the boxes get re-checked by default, workaround is to hide the date of birth picker from the edit profile page and only show it for site staff in case corrections to someone's DoB is required.
Without a built-in option to force the UNA script to NOT check those boxes by default, it adds extra staff workload.