Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.After this was committed https://www.drupal.org/project/flag_lists/issues/3179178 a route entity.action.collection was added that is provided by the core "Actions" module. If navigating to the config page "admin/config/flag_lists" without the Actions module enabled you'll be presented with a wsod since the route is not yet loaded.
The Core "Actions" module should be added as a dependency.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Route_Not_Present-3194926-5.patch | 1.58 KB | sl27257 |
| Add_dependency_for_core_action_module.patch | 273 bytes | gcalex5 |
Comments
Comment #2
sl27257Thanks for the report!
Either it is simply added as a dependency or alternatively checked if the module is enabled and if not enabled then remove the route?
Do you think it is too much overhead to force Actions to be enabled? Let me see how much changes it would require to remove the route if the module isn't enabled!
Comment #3
sl27257Comment #4
aritrika.d CreditAttribution: aritrika.d at OpenSense Labs commentedComment #5
sl27257What I had in mind was something like this.
Comment #6
gcalex5 CreditAttribution: gcalex5 at Inclind Inc commentedThat's probably the better approach if "Action" doesn't provide any core functionality. Haven't personally used the core Action module so wasn't sure exactly what that'd impact.
Comment #8
sl27257Comment #9
sl27257