`%%dbSSL%%` variables left behind in civicrm.setting.php after install
This doesn't come up with
cv core:install or any method that uses civicrm-setup, but does come up with drush and the legacy installer (e.g. sites/all/modules/civicrm/install/index.php). It will be fixed going forward but anyone who used e.g. drush, wp-cli, or the legacy installer to install civi since 5.31 will likely have the
%%CMSdbSSL%% variables left behind in CIVICRM_DSN and CIVICRM_UF_DSN in civicrm.settings.php.
Since it gets ignored during parsing/usage, it's mostly cosmetic at the moment. So:
- Having an upgrade message seems like it's asking people to do something that's optional, which should maybe be handled a different way.
- Having a status message will just get ignored by most staffers since they can't fix it anyway. And the tech people who deal with civicrm.settings.php might never see it. In some orgs it's the same person, but it will miss many.
- Maybe in the docs in the version-specific steps, but again many people will miss that, but then at least it's not bothering anyone.
- Stackexchange - e.g.
Why do I have %%dbSSL%% in my civicrm.settings.php and can I remove it?