Please Log in or Create an account to join the conversation.
Added a bug ticket as was able to confirm. It shouldn't show tabs that don't allow fields on them.When we assigned the Username field to a new tab, the username field became no longer viewable in the backend field list. I believe this is because the tab we assigned the field to is not visible in the field list, although it was available as an option to assign the field to.
The tab was CB Articles ... I realize that this wasn't the best choice to assign the field but it was a troubleshooting step.
I've changed the username field's tab assignment in the database and now I'm able to see the field again. I wanted to make you aware of this issue, however.
CB Conditional is not completely CB 2.0 compatible. It may not be parsing the parameters out correctly. I can't make any sort of guarantee it'll even work. After I'm done upgrading CB Connect I'll be upgrading CB Privacy then CB Conditional. You can try using an older version of CB Conditional instead of latest as the older version doesn't use the Registry API, which may or may not help with params parsing problems.So, our issue that remains is #1: the conditional tab display. We have a tab that we would like to only display to the profile owner. We have made sure that the username field is visible on the profile, but the tab still shows to non-profile owners.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
krileon wrote:
forge.joomlapolis.com/issues/4806
Please Log in or Create an account to join the conversation.