Conditional-Tabs not turning red for missing field

12 years 9 months ago - 12 years 9 months ago #172170 by WiZaxx
Well this conditional pluging really drives me nuts..

Besides conditional not working at all ( here is the thread ) and still waiting for some help :angry:

Now I have found out that the tabs are not workings either.
They should be turning red and hold on the page if a mandatory field is missing. NOPE
They all stay nice and grey and they let you go forwards just to get trapped by joomla that shows an ugly messages in a new unwanted page.

Can anyone help?
I'm runnig:
CB conditional
  • 1.1.2
  • CB 1.4 (also tested 1.7 that gives the same results)
  • Joomla 1.6.6

Please Log in to join the conversation.

12 years 9 months ago #172186 by krileon
Please do not create duplicate threads. Have linked your previous thread to this one and locked your previous thread. Please understand your PM was received on Saturday, I am not here on Weekends except for a minimal amount of time to address emails. Onto your issue.

You're using a CB 1.4 on a J1.6 install, please upgrade and remain upgraded. There are known issues with CBs core regarding J1.6 and J1.7 critical to your installs success; whether this applies to CB Conditionals or not is irrelevant.

The reason the registration is not behaving properly is because you've a jQuery conflict. The below fatal JS error is preventing CBs validation code from operating properly.
jQuery.validator is undefined
index.php/community/login-register
Line 34

The above happens with or without CB Conditional and is clearly not the cause. CB Conditional is tested as working perfectly fine. The problem is the conflict preventing it from working as it's 90% jQuery (JS) driven.

Upon further review switching to Default Joomla template resolves the issue. This is due to your Template loading jQuery. This normally isn't a problem, but your template is loading 1.6, which changes how many selectors operator and results in many if not all jQuery calls written for <6.0 failing. Please contact your template developer and instruct them to run jQuery in a noConflict state (routing $ to their own custom selector) or checking if jQuery is already loaded before loading it.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

Please Log in to join the conversation.

12 years 9 months ago - 12 years 9 months ago #172203 by WiZaxx
Sorry, But I thought those were two different issues as they are affecting two different parts of the plugins.

My sincere apologies.
I will contact the templete developers and report back to this forum asap.

Cheers

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.204 seconds

Facebook Twitter LinkedIn