Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overridden config values are still in forms, prevent form save. #12

Closed
rosiel opened this issue Aug 11, 2023 · 3 comments
Closed

Overridden config values are still in forms, prevent form save. #12

rosiel opened this issue Aug 11, 2023 · 3 comments

Comments

@rosiel
Copy link
Contributor

rosiel commented Aug 11, 2023

A number of values such as the Broker URI (Islandora Settings form) are set using Drupal's config override by specifying values in the settings.php file. However, the values that an admin sees in the form are those provided by the starter site (which is confusing, as the admin can't see what value is actually being used). Furthermore, for all forms with validation (including the Islandora settings form) the admin cannot change any settings in that form without first finding the valid value for that setting. This is frustrating and time-consuming.

Screenshot 2023-08-11 at 2 20 25 PM
@rosiel
Copy link
Contributor Author

rosiel commented Aug 11, 2023

This could be mitigated if we install Config Override Warn

@nigelgbanks
Copy link
Contributor

This is oddly intentional, though they plan to change the behavior in D11, apparently.

If we were to install Config Override Warn, that would have to be done on the https://github.com/Islandora-Devops/islandora-starter-site repository.

@nigelgbanks
Copy link
Contributor

Closing this as I've raised an issue in Islandora-Devops/islandora-starter-site#112

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants