[#4800] Cb conditional issue

Some fields may not be able to have their values conditioned away. Specifically calculated fields like Gravatar or Delimiter. I'll be looking into this further when upgrading CB Conditional. I do not have a quickfix or anything further to suggest, sorry.

I tried to filter a "Query" field in the userlist but it does not work the same, so CB Conditional works in the userlist only with the fields contents in the table comprofiler. If it is possible for the next version to filter with CB Conditional in the userlist also fields (Delimiter, Query, Gravatar) that are not directly related with the user and are not available in the users list, would be comfortable. For now I load a value via CB Auto Action during registration without that user know, then I filter it in the userlist, is a solution uncomfortable because a given load on the server to no avail, but it works.
Thanks.

Right, that's a bug. CB Conditional should have no issue hiding calculated fields in userlists, but it won't due to a bug. I'll be investigating the issue and fixing it for next release.

In CB Conditional I set a condition to hide a field type "image", the problem is that it hide the photo but remains visible the default image:



It can be hide completely?
Thanks.

Avatar field doesn't have a blank display. The way CB Conditional works is it nulls the fields value for the user object then does normal field parsing behavior. The behavior for image fields is to show the default image. In CB 2.0 it's possible to set the default image to None for image fields, but for CB 1.x it's working as intended.

With CB 2.0.2 and CB Conditional 3.0.13 when I access in the user profile gives me the following error:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 79 bytes) in /membri/pasquale8/components/com_comprofiler/plugin/user/plug_cbconditional/cbconditional.class.php on line 375

I can not understand what generates it. Can you help me?
Thanks.