Issue
- When users try to change configurations using .config files, these may not always be reflected.
Environment
- Liferay DXP 7.4
Resolution
The concerns outlined above mostly happen when the configuration is saved in the database, overriding the configuration provided in the files. There might be multiple entries for the .config files, so it could be beneficial to delete all of the configurations from the configuration_ table before making changes to the UI.
Now, the UI and osgi configuration files are directly in sync.
The following are the steps which can be used to confirm this:
- Export the file, add it to osgi/configs, and perform certain changes to it.
- Now, refresh the portal 2-3 times, and the changes of the config file should be reflected on the UI.
- Again perform the changes to the UI.
- The above UI changes are automatically reflected in the config files without manual interventions.
However, as highlighted in the 'Single Read Only Value' page, assigning a config parameter's value via the portal property has precedence over DB and Config.
-
Therefore, the following actions would be helpful in case the issue persists:
- Export the current ES config
- Make the desired changes to all the parameters.
- Now, pick each parameter, and add it to the portal property like:
configuration.override.com.liferay.portal.search.elasticsearch7.configuration.ElasticsearchConfiguration_username="test"
- Save this portal property and take a restart of the system. This will ensure that only the values provided from the portal property will take precedence here.
Additional Information
- Please ensure to test the behavior in lower environments first before proceeding with the production environment.