Please Log in or Create an account to join the conversation.
krileon wrote: Strange, please PM backend super administrator login credentials and will take a look.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
krileon wrote: I've fixed the bug and installed a fixed release for you.
krileon wrote: I've fixed the bug and installed a fixed release for you. Note erilam, you do not need this quickfix as I've already applied it for you and confirmed is working. Please also confirm is now working fine for you.
Please Log in or Create an account to join the conversation.
krileon wrote: I've fixed the bug and installed a fixed release for you.
Please Log in or Create an account to join the conversation.
That's legacy usage and it'll only remove if the current value matches exactly the value it was set to. So should be working assuming the field wasn't change manually or by anything else. I suspect you've something doing a user store somewhere that's conflicting, but I've no idea where it's coming from.But I have also test a radio button with Remove value on plan deactivation set on YES and no value on plan deactivation. It doesn't work in that case.
Don't understand the question. You're wanting to mass-fix users who have incorrect values? you'd need to do this in database by adjusting _comprofiler table for all rows that are messed up. There's no tool to fix this.Just a question more, for other members should I use CB tools to synchronise their fields or theses tools are not available for CBsubs and I have to do it by SQL in the database ?
Please Log in or Create an account to join the conversation.