- 🇺🇸United States drakythe
Attempting to maintain the security considerations I offer this patch. If the password field is empty it loads up the callback object entity and if that entity is not new then we access the existing config and set the password field to what it already is in the database. If it was already empty no harm no foul, but if a password exists we don't lose it.
- Assigned to TomTech
- Status changed to Closed: duplicate
10 months ago 3:40pm 28 February 2024 - 🇺🇸United States TomTech
The issue stems from the
PluginSelectWidgetin commerce core.When a plugin edit configuration form is initially loaded, the configuration is properly passed to the plugin before the form process begins. (This is in the
PluginSelectWidget ->formElement()method.)When the form is posted back, though, the configuration was not being passed to the plugin.
A fix has been committed in [#33021571] that resolves this. This should be in the next commerce release.
If you need it before then, you can apply the diff from that MR as a patch.
Closing this out as (Duplicate), since the fix is in commerce core.