This is basically the equivalent of https://www.drupal.org/project/drupal/issues/3163226 (as well as a sibling issue to #5741) which was introduced in D 9.1.x (Change record: Core settings keys can be deprecated)
If the
settings.php
file for a site (or any file it includes) contains the legacy setting name, the deprecation warning will be generated. If code callsSettings::get('new_setting')
but'new_setting'
is not yet defined, the value of'old_setting'
will be returned.If any code calls
Settings::get()
with the legacy name, the deprecation warning will also be generated. If the replacement setting is already defined, the value returned bySettings::get('old_setting')
will be the value ofnew_setting
.
This would help us with issues similar to #4451 as well, and possibly allow us to deprecate things in the Backdrop 1.x release cycle instead of having to wait for 2.x.
Recent comments
Thanks! I tested PayPal WPS (since I also use it in my Drupal 7 Commerce shop). With the PayPal server SANDBOX mode (no real payment transaction, just simulated). And everything...
Commerce shop system from Drupal
Peter, I've done an initial port of Commerce PayPal. While I haven't tested it, I think it should work, as the module is not too complex. https://github.com/backdrop-contrib/...
Commerce shop system from Drupal
Glad you finally found it! Someone really needs to port commerce_paypal.
Commerce shop system from Drupal