There's no limit in CB, but you maybe hitting server limitation (whether PHP or SQL). Enable debug mode and maximum error reporting to expose any errors that could be occurring. If none be sure to check server error log. Alternatively add them in batches instead of all at once.
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.
we have an own server with one of the strongest hardware possible on the market right now. Apache, PHP and MySQL are set to have best limits. Really no way to hit some of these limits.
There are no errors shown wether in joomla backend, cb or server logs.
Just if we push the "save and close" button it redirects to joomla backend overview. If we push the "save" button it redirects us to the cb backend configuration
This takes just 1-2 seconds.
The dropdown field has about 200 entries ...
For example, in adsmanager it is no problem to create and save same dropdown field with about 200 entries ...
Wo optimized some things like max input vars... Now it seems to work...
Wo optimized some things like max input vars... Now it seems to work...
Yup, that'll do it. Each field option is 3 inputs in POST (id, label, value). So 200 options is 600 inputs. Add in all the other inputs and it stacks up pretty fast. When you get to a point of having that many values though I suggest using CB Query Field and its Query Select type with a custom database table to hold your options; it'll avoid overloading the field edit display (parsing 200 inputs into repeat usage is probably slow).
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.
krileon
