I would like to report a bug in Joomla Component Builder.
Environment:
Joomla: 6.1.3
JCB: 6.1.5-rc2
PHP: 8.3.30
Local stack: MAMP / Apache
Issue:
Global Configuration for com_componentbuilder opens correctly through com_config, but saving does not persist any value.
Steps to reproduce:
Open JCB Global Configuration
Change any option
Click Save
Actual result:
The form submits successfully
No values are saved
#__extensions.params for com_componentbuilder remains unchanged
After saving, Joomla redirects to Global Configuration instead of keeping/saving the JCB component configuration
Validation already done:
POST request to com_config is sent correctly
HTTP response is 200
com_content options save correctly on the same Joomla installation
Therefore, com_config itself is working
The problem appears specific to com_componentbuilder configuration
Steps to reproduce the Bug
Steps to reproduce:
Open JCB Global Configuration
Change any option
Click Save
Which Joomla version are you compiling in?
6.1.3
Which PHP version are you compiling in?
8.3.3
Which Joomla versions are you targeting?
6.1.5-rc2
Which PHP version are you targeting?
8.3.3
Which Web server is JCB running on?
Apache
Which Relational Database is JCB running on?
MySql 8
Which OS is JCB running on?
MAMP
Which JCB version are you using?
6.1.5-rc2
Where in JCB did this issue occur?
Other
On which browsers did you encounter the issue?
Firefox, Safari, Brave
Additional Comments
Browser-extension console noise was excluded from the diagnosis
Missing image assets (404) do not appear to be related
Issue is reproducible consistently
### What Happened?
Hello,
I would like to report a bug in Joomla Component Builder.
Environment:
- Joomla: 6.1.3
- JCB: 6.1.5-rc2
- PHP: 8.3.30
- Local stack: MAMP / Apache
Issue:
Global Configuration for com_componentbuilder opens correctly through com_config, but saving does not persist any value.
Steps to reproduce:
1. Open JCB Global Configuration
2. Change any option
3. Click Save
Actual result:
- The form submits successfully
- No values are saved
- #__extensions.params for com_componentbuilder remains unchanged
- After saving, Joomla redirects to Global Configuration instead of keeping/saving the JCB component configuration
Validation already done:
- POST request to com_config is sent correctly
- HTTP response is 200
- com_content options save correctly on the same Joomla installation
- Therefore, com_config itself is working
- The problem appears specific to com_componentbuilder configuration
### Steps to reproduce the Bug
Steps to reproduce:
1. Open JCB Global Configuration
2. Change any option
3. Click Save
### Which Joomla version are you compiling in?
6.1.3
### Which PHP version are you compiling in?
8.3.3
### Which Joomla versions are you targeting?
6.1.5-rc2
### Which PHP version are you targeting?
8.3.3
### Which Web server is JCB running on?
Apache
### Which Relational Database is JCB running on?
MySql 8
### Which OS is JCB running on?
MAMP
### Which JCB version are you using?
6.1.5-rc2
### Where in JCB did this issue occur?
Other
### On which browsers did you encounter the issue?
Firefox, Safari, Brave
### Additional Comments
- Browser-extension console noise was excluded from the diagnosis
- Missing image assets (404) do not appear to be related
- Issue is reproducible consistently
Thank you for taking the time to report this issue and contact us for support.
This is something that quite a few users have already run into with JCB.
JCB is a large and feature-rich component, and to run it efficiently and get the best results from it, we strongly recommend making sure that your PHP configuration is set up as explained here:
All our development systems use these settings, and in that environment they do not pose a security risk. So please make sure your PHP configuration matches those recommendations. Once that is in place, you should be able to save changes without these issues.
Please note that saving changes in JCB configurations can still be inherently slow because of the amount of processing involved, but with the correct PHP setup it should complete successfully. A little patience may still be needed. 😉
For additional context, these related issues may also help:
Hi @xfabio76x
Thank you for taking the time to report this issue and contact us for support.
This is something that quite a few users have already run into with JCB.
JCB is a large and feature-rich component, and to run it efficiently and get the best results from it, we strongly recommend making sure that your PHP configuration is set up as explained here:
[PHP Settings](https://git.vdm.dev/joomla/Component-Builder/wiki/PHP-Settings)
All our development systems use these settings, and in that environment they do not pose a security risk. So please make sure your PHP configuration matches those recommendations. Once that is in place, you should be able to save changes without these issues.
Please note that saving changes in JCB configurations can still be inherently slow because of the amount of processing involved, but with the correct PHP setup it should complete successfully. A little patience may still be needed. 😉
For additional context, these related issues may also help:
- [Unable to save anything via Component Builder Configuration #1204](https://git.vdm.dev/joomla/Component-Builder/issues/1204)
- [Joomla Component Builder: In the options, saving is slow #1240](https://git.vdm.dev/joomla/Component-Builder/issues/1240)
I have the same problem in JCB Version 6.1.4. Please test with Field Name Builder and Field Type Name Builder in the Compiler Section, switch to Legacy Mode. Not working. The Result is, JCB go to Joomla System Settings. Ubuntu 24 and Joomla 6.0.3.
In new Version JCB 6.1.5 works fine, juuhuu!
Thanks for your Test
René
I have the same problem in JCB Version 6.1.4. Please test with Field Name Builder and Field Type Name Builder in the Compiler Section, switch to Legacy Mode. Not working. The Result is, JCB go to Joomla System Settings. Ubuntu 24 and Joomla 6.0.3.
In new Version JCB 6.1.5 works fine, juuhuu!
Thanks for your Test
René
I know that usually the the problem is related to the max_input_vars since the JCB options is a large data set that breaks before the whole json object is stored... and so it will direct to the Joomla System Settings and not update the database.
I am happy to hear that JCB v6.1.5 is working for @pctechnikch but if it still fails for other, please check the PHP settings as @Lemuel pointed out.
I know that usually the the problem is related to the `max_input_vars` since the JCB options is a large data set that breaks before the whole json object is stored... and so it will direct to the `Joomla System Settings` and not update the database.
When reading https://git.vdm.dev/joomla/Component-Builder/wiki/PHP-Settings#4-max_input_vars-7000 you will see how to fix this issue.
I am happy to hear that JCB v6.1.5 is working for @pctechnikch but if it still fails for other, please check the PHP settings as @Lemuel pointed out.
It's strange; sometimes it works, and sometimes it doesn't. I know exactly what the PHP settings for JCB should be. Despite that, the error keeps recurring. Switching browsers didn't help either. I really hope it works as it did in the last version, as tested, and stays that way.
Thanks
It's strange; sometimes it works, and sometimes it doesn't. I know exactly what the PHP settings for JCB should be. Despite that, the error keeps recurring. Switching browsers didn't help either. I really hope it works as it did in the last version, as tested, and stays that way.
Thanks
I can confirm that the issue has been resolved after:
updating to JCB 6.1.5
increasing max_input_vars to 7000
After these changes, the Global Configuration of com_componentbuilder saves correctly.
Thanks again for your help and quick responses.
Hello,
thank you for your replies and support.
I can confirm that the issue has been resolved after:
- updating to JCB 6.1.5
- increasing `max_input_vars` to 7000
After these changes, the Global Configuration of `com_componentbuilder` saves correctly.
Thanks again for your help and quick responses.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What Happened?
Hello,
I would like to report a bug in Joomla Component Builder.
Environment:
Issue:
Global Configuration for com_componentbuilder opens correctly through com_config, but saving does not persist any value.
Steps to reproduce:
Actual result:
Validation already done:
Steps to reproduce the Bug
Steps to reproduce:
Which Joomla version are you compiling in?
6.1.3
Which PHP version are you compiling in?
8.3.3
Which Joomla versions are you targeting?
6.1.5-rc2
Which PHP version are you targeting?
8.3.3
Which Web server is JCB running on?
Apache
Which Relational Database is JCB running on?
MySql 8
Which OS is JCB running on?
MAMP
Which JCB version are you using?
6.1.5-rc2
Where in JCB did this issue occur?
Other
On which browsers did you encounter the issue?
Firefox, Safari, Brave
Additional Comments
Hi @xfabio76x
Thank you for taking the time to report this issue and contact us for support.
This is something that quite a few users have already run into with JCB.
JCB is a large and feature-rich component, and to run it efficiently and get the best results from it, we strongly recommend making sure that your PHP configuration is set up as explained here:
PHP Settings
All our development systems use these settings, and in that environment they do not pose a security risk. So please make sure your PHP configuration matches those recommendations. Once that is in place, you should be able to save changes without these issues.
Please note that saving changes in JCB configurations can still be inherently slow because of the amount of processing involved, but with the correct PHP setup it should complete successfully. A little patience may still be needed. 😉
For additional context, these related issues may also help:
I have the same problem in JCB Version 6.1.4. Please test with Field Name Builder and Field Type Name Builder in the Compiler Section, switch to Legacy Mode. Not working. The Result is, JCB go to Joomla System Settings. Ubuntu 24 and Joomla 6.0.3.
In new Version JCB 6.1.5 works fine, juuhuu!
Thanks for your Test
René
I know that usually the the problem is related to the
max_input_varssince the JCB options is a large data set that breaks before the whole json object is stored... and so it will direct to theJoomla System Settingsand not update the database.When reading https://git.vdm.dev/joomla/Component-Builder/wiki/PHP-Settings#4-max_input_vars-7000 you will see how to fix this issue.
I am happy to hear that JCB v6.1.5 is working for @pctechnikch but if it still fails for other, please check the PHP settings as @Lemuel pointed out.
It's strange; sometimes it works, and sometimes it doesn't. I know exactly what the PHP settings for JCB should be. Despite that, the error keeps recurring. Switching browsers didn't help either. I really hope it works as it did in the last version, as tested, and stays that way.
Thanks
Hello,
thank you for your replies and support.
I can confirm that the issue has been resolved after:
max_input_varsto 7000After these changes, the Global Configuration of
com_componentbuildersaves correctly.Thanks again for your help and quick responses.