Yes, both CB Conditional and CB Privacy have to parse every field 1 by 1. It's the only way to do field value comparison checks and privacy checks. They do have a lot of internal caching to improve on this, but you are still going to get a performance hit using them. There's no way to eliminate that, sorry. To test disable both CB Conditional and CB Privacy then see how much your load times improve.
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.
Having some fields in the database but not shown anywhere should have little to no impact, right? So I can remove some fields from the profiles without actually deleting them in case I want to use them later on?
krileon
