Conditional Required Fields issue

Still doesn't work here.

Response: 530 Login authentication failed

Please PM the backend URL to your clone site and will just install debug builds of the plugin.

Just noticed that for some reason the new details I thought I sent in a pm to you never actually sent, so I re-sent them in another pm to you. Sorry about that...

Jeff

Ok, found the cause. It's not a bug in CB Conditional but in core CBs router.php that handles SEF URL rewriting. It's stripping the view from the URL, which CB Conditional checks to determine where it's at and what it needs to do from there. As it can't determine that it's processing a user save it doesn't remove the fields from the fields object array to stop their storage processing, which results in the validation error. So for now you need to either not use SEF or leave the fields as non-required until I can get this fixed in our router.php for next release.

forge.joomlapolis.com/issues/5286

Strangely I am unable to duplicate this locally though. Will continue to investigate to see what could be going on.

Ok investigated further as couldn't confirm here. It's due to "System - K2". Specifically it's due to K2s CB integration loading in CBs API too early when it should be loaded in at use and not in a Joomla system plugin before CB can even initialize. This can be fixed by setting "Community Builder integration for avatar, user names and user pages" to "Disabled" within K2 > Parameters > Advanced.

krileon wrote: This can be fixed by setting "Community Builder integration for avatar, user names and user pages" to "Disabled" within K2 > Parameters > Advanced.

Well, thanks for catching this, but unfortunately, turning that off reverts back to K2 styling that ends up breaking my template on profile view from K2.

Any way around this without turning off the K2 stuff? Or just have to settle with leaving the items as not required?

I don't have a workaround, sorry. The K2 integration with CB is loading CBs API too early is my guess. I don't know why it's causing this issue in particular as I don't know how they utilized CBs API exactly. That parameter also breaks upgrading from CB 1.x to CB 2.x and we've a bug ticket for this already and have noted this issue in it as well to see if we're able to fix this somehow on our end.