[SOLVED] Conditional Field Strict Standards Error Message

My conditional fields no longer work (only the conditionals code is displayed - which also appears truncated)...
www.betta-blinds.com.au/j3/customer-resources/order-forms/awnings-order-forms
(the conditionals are in the dropdowns)

I'm currently running CB 1.9.1 on a Joomla 2.5.27 site and getting error reports on every page of the frontend with error reporting set to maximum:

These are the errors I'm getting. I've checked the code on each line and can't locate the problem. I suspect it's the same problem for conditionals as it is to the one I'm experiencing with Geomunity...


Strict Standards: Declaration of cbconditionalField::getFieldRow() should be compatible with cbFieldHandler::getFieldRow(&$field, &$user, $output, $formatting, $reason, $list_compare_types) in <span>/</span>home<span>/</span>betta/public_html/j3/components/com_comprofiler/plugin/user/plug_cbconditional/field.cbconditional.php on line 119

Strict Standards: Declaration of getGeommunityLocatorTab::getDisplayRegistration() should be compatible with cbTabHandler::getDisplayRegistration($tab, $user, $ui, $postdata) in <span>/</span>home<span>/</span>betta/public_html/j3/components/com_comprofiler/plugin/user/plug_geommunitylocator/geommunitylocator.php on line 1163

Strict Standards: Declaration of getGeommunityLocatorTab::saveRegistrationTab() should be compatible with cbTabHandler::saveRegistrationTab($tab, &$user, $ui, $postdata) in <span>/</span>home<span>/</span>betta/public_html/j3/components/com_comprofiler/plugin/user/plug_geommunitylocator/geommunitylocator.php on line 1163

Any help appreciated.

They're just PHP 5.4+ strict standards warnings. They are safe to ignore (disable Joomla error reporting). Believe they're already fixed for their CB 2.0 release and will be rechecked on CB Conditional upgrade release.

Thanks krileon,

My main concern is not the errors but the fact the conditionals don't work at all!

This may have nothing to do with the strict standards warnings, but for some reason the conditional code appears in the front end (without the curly bracket at the beginning, even though it is there in the page content)...

www.betta-blinds.com.au/j3/customer-resources/order-forms

This is the content as it appears in admin:

{cb:[cb:if user_id=""]
Sorry, it appears you don't have permission to view this document. Please contact our Help Desk for further assistance.
[/cb:if]}

{cb:[cb:if gids includes "11" or gids includes "8" or gids includes "18" or gids includes "26" or gids includes "29" or gids includes "32"]

{pdf} www.betta-blinds.com.au/downloads/order_forms/panel_glides_order_form.pdf|height:780|width:1024|app:google{/pdf }

[/cb:if]}


This is what appears in the frontend:

Sorry, it appears you don't have permission to view this document. Please contact our Help Desk for further assistance.

[cb:if gids includes "11" or gids includes "8" or gids includes "18" or gids includes "26" or gids includes "29" or gids includes "32"]

{pdfhttp://www.betta-blinds.com.au/downloads/order_forms/panel_glides_order_form.pdf|height:780|width:1024|app:google{/pdf}

[/cb:if]}


The code appears truncated with the curly bracket missing at the beginning from both the conditional and pdf plugin. The curly bracket is also missing in the code to call up the .pdf file (once again it IS there in the page content when viewed in admin). www.betta-blinds.com.au/j3/customer-resources/order-forms



The warnings don't bother me (except on the members list which presents multiple instances and takes forever to load.. www.betta-blinds.com.au/j3/community/visit-the-betta-blinds-community

That's not CB Conditionals, but substitutions using CB Content Bot for substitution support in Joomla articles. As you're not on CB 2.0 you can't use the latest CB Content Bot, which fixes the issues you're experiencing. Mainly you're using other content bots inside of CB Content Bot parsing, which doesn't work in your release (e.g. your {pdf} usage is breaking it).

OK. My original plan was to fix any issues before upgrading to Joomla 3.3 and then update my extensions.

I will now upgrade first and see what happens.

Sorry, it's been ages since I've worked with CB and I'll have to reacquaint myself with a lot that's been done. Thanks.

And thanks for the tip about the PDF usage. I fixed that and it all works again