[SOLVED] CB Conditionals 3.0.10 causes error

Have reviewed your install and installed 3.0.10 with the fix applied as well as cleared caching. Your jQuery error appears to be gone. Please also note you have a lot of 1 way conditionals. This means they will not reverse themselves so your issue could purely be a configuration issue. Please review your conditionals carefully and check conditionals are still not working properly.

Thanks for this! Confirm that jQuery error is gone.

Still fields are not saving (eg. cb_apcurrcountry). Setting a field to "Show" instead of "Hide" Condition and also 2-way does not help. Field visible on profile and profile edit by user via frontend - as it should.

Logically also the one-way configuration was alright - as fields are normally shown and should just be hidden under a certain condition.

Worked before conditionals were applied. Rules seem configured exactly as they should be applied. Fields are shown and hidden exactly the way they should. Just contents not saved.


PS: Getting this upon backend user profile change:

Notice: Undefined property: moscomprofilerUser::$cb_verifiedimg in /components/com_comprofiler/plugin/user/plug_cbcore/cb.core.php on line 2443

Such a variable doesn't exist and is not being used in cb.core.php. Has CBs core files been modified in any way? Please install CB over top of it self to remove any core modifications and confirm if your issue persists.

As for your conditionals I don't know what to tell you. The jQuery conditioning works off of raw values in the DOM. PHP however will apply translations. Perhaps your values are being translated causing validation to fail. Edit your conditionals and set translate value to disable.

krileon wrote: Such a variable doesn't exist and is not being used in cb.core.php.

This is a field name. An IMAGE field - deleted it as it was unpublished anyways and message is gone.

krileon wrote: Has CBs core files been modified in any way?

Not that I am aware of.

krileon wrote: Please install CB over top of it self to remove any core modifications and confirm if your issue persists.

Hence, I will wait with this...

krileon wrote: Perhaps your values are being translated causing validation to fail. Edit your conditionals and set translate value to disable.

Disabled Translations in Conditionals already. Conditionals are applied correctly. Changes to fields are not saved upon frontend profile edit.

Have reviewed your install and believe your conditions are failing because the field your testing against is read only. That means it has absolutely no POST value. So during save conditional checking it's not finding a value to check against. Disable read only usages and see if it'll work.

You may need to use Custom Value and substitute in the field using [cb_usertype] to be able to condition against it on POST, but this usage will only work in profile edit as custom value conditions only work for values that exist so you'll need separate conditionals for registration and profile edit if you want to keep it read only.

Have set readonly to "No" as it does not make any relevant change. Field [cb_usertype] is on a Tab not displayed on profile.

As before, conditionals are applied correctly. Just on user profile change from frontend data is not saved in fields.