Description of the need
Now that config values can be overridden via settings.php
, we've created a system that can also be very confusing for admins and editors. When a value is overridden it appears as though the forms are broken.
For example, when CSS aggregation is set to FALSE
in settings.php
, visiting the form at admin/config/development/performance
appears as usual, but when I attempt to check the box for "Aggregate and compress CSS files" and submit the form, it submits as usual, and the message The configuration options have been saved.
is printed to the screen. However, when I scroll down to the checkbox for "Aggregate and compress CSS files" it remains unchecked.
Proposed solution
@herbdool posted a proof of concept PR that contained some interface components that indicated when a config value was overridden. I'm not sure how far this proof of concept is from a workable solution, but I really liked where it was heading:
Additional information
This is a follow up to https://github.com/backdrop/backdrop-issues/issues/2805
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface