[#3977] CB content tabs not showing in tabs

CB conditional is up to date and I guess that all plugins are now up to date.
By the way this is much too difficult to follow on your updates without some sort of dashboard from the website admin. You need to make a simple view with all installed plugins, their latest releases and the release installed.

To come back to CB conditional, the content module fails with hiding and showing a field depending on another field value (empty in this case). It always shows both fields whatever values

This works well on profile but not on content module, even with latest version and load template and load js activated.

By the way this is much too difficult to follow on your updates without some sort of dashboard from the website admin. You need to make a simple view with all installed plugins, their latest releases and the release installed.

We'll be handling this with CB 2.0 where ideally you'll even be able to update them without leaving your site.

To come back to CB conditional, the content module fails with hiding and showing a field depending on another field value (empty in this case). It always shows both fields whatever values

Strange, the show/hide depends on the "reason". Ensure you've set the reason for your substitutions to "profile". If you did not change the reason then it's defaulted to "profile" so this could be some sort of strange bug in CB or CB Conditional; did you leave the "reason" parameter untouched or was it set to something other then "profile"?

No all is set to profile. Here is the screenshot.

Seams to be working perfectly fine in my tests. Please provide the exact substitution you're using so can test further.

These are very simple substitution for two delimiters fields (html including 2 other fields):
[cb:userdata field="cb_accesanonyme2" /]
[cb:userdata field="cb_argufournacces" /]

and the conditions are as attached:


for first one


for second one

Filling or emptying conditional field does not change anything, both fields are always displayed

Was able to confirm, seams to be only affecting Conditional Self. Have created the below bug ticket for further investigation.

forge.joomlapolis.com/issues/3977