- Issue created by @alen simonyan
- Status changed to Postponed: needs info
about 1 year ago 10:39am 3 November 2023 - 🇬🇧United Kingdom adamps
It works for me and no one else has reported. Maybe it is related to something on your site? I suggest to test with creating policy for one of the Core modules.
- 🇦🇲Armenia alen simonyan
Hi Adam,
I also tried with one of the core modules and it behaves the samehttps://drive.google.com/file/d/1X7qqCv8DMaqXBZTSUGuKdzdOqpFZPy49/view?usp=sharing
- 🇺🇸United States scotthreha
I just completed a Drupal 10 upgrade and I'm getting this same error when I try to add a new element to an existing policy. It worked without problems during the entire development process, but now that I've pushed the upgrade to production it fails.
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "" plugin does not exist. Valid plugin IDs for Drupal\symfony_mailer\Processor\EmailAdjusterManager are: mailer_url_to_absolute, email_bcc, email_body, email_cc, mailer_default_headers, email_from, mailer_hooks, mailer_inline_css, email_plain, email_priority, email_reply_to, email_skip_sending, email_subject, email_theme, email_to, email_transport, mailer_wrap_and_convert in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of /var/www/web/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
I should add that this is a policy for email receipts in Drupal Commerce.
- 🇷🇴Romania andreic
The problem was competing form actions. There was $form['add_actions'] as type 'action' and then $form['actions'] as type 'action.
The $name variable was always empty (attached screenshot) when clicking the Save button, hence the error in this issue.
The solution was to make $form['add_actions'] a container within the existing $form['actions'].
Patch added. - 🇬🇧United Kingdom adamps
Thanks. Drupal.org now uses requests instead of patches please.
- 🇬🇧United Kingdom adamps
Please put your changes in the 3398364-the--plugin branch then create a merge request. This will cause the tests to run. Thanks.
- First commit to issue fork.
- 🇬🇧United Kingdom adamps
Thanks. For me the result is worse than before. Before the select and button were on the same line, and now they are one below the other - see screenshots attached.
I believe that the buttons are no longer in the container because they still have
$form['add_actions']
. Instead it worked for me like this:$form['add_actions'] = [ '#type' => 'container', '#weight' => -1, '#attributes' => ['class' => ['container-inline']], ];
Please can you check if that still works for you, then update the MR?