- Issue created by @flefle
- π©πͺGermany flefle
The ones dealing with this issue, please consider to add an config/install/system.action.commerce_price_adjust.yml before enabling your Module (maybe update hook) or implement a post enable process (Route + Controller) running following code:
try {
$entity_type_manager = \Drupal::entityTypeManager();
$module_handler = \Drupal::moduleHandler();// Save the bulk delete action to config.
$config_install_path = $module_handler->getModule('mbkovanie')->getPath() . '/' . InstallStorage::CONFIG_INSTALL_DIRECTORY;
$storage = new FileStorage($config_install_path);
$storageRead = $storage->read('system.action.commerce_price_adjust');
$entity_type_manager
->getStorage('action')
->create($storageRead)
->trustData()
->save();
} catch (\Exception $e) {
return new Response('Already exists.');
}.... fun fact, if you are running a Commerce Module that evolved meanwhile, it is possible that the DC Actions are not active (available) and should be reinitialised by a similar process. My issue was solved by this, and wanted to provide the community my solution. Happy coding.
- Status changed to Fixed
6 months ago 10:36pm 10 June 2024 - π΅π±Poland Graber
Thank you for sharing your findings, hopefully itβll help someone.
Basically the core bulk form needs that extra configuration while the Views Bulk Operations field doesnβt, it discovers all available actions. Automatically closed - issue fixed for 2 weeks with no activity.