- Issue created by @promo-il
- Issue was unassigned.
- 🇧🇪Belgium dieterholvoet Brussels
I can reproduce this by setting up a field to use the 'Required by role' plugin, uninstalling the Required by role module and saving a node with that field.
I'm not sure what the best way to go would be though. I think the safest may be to fallback to the default behaviour (always required) when the chosen plugin is missing, but log a message to remind the site administrator to reconfigure the field.
I'm going to move this issue to the Required API module since this is something that needs to be fixed over there.
- 🇧🇪Belgium dieterholvoet Brussels
I added the fallback and error log in the MR. What still needs to be done:
- Show in the field edit form when a non-existing plugin is selected and allow to set back to default or another plugin
- See what happens when you completely uninstall the Required API module when fields are configured
- Merge request !16Add fallback if plugin doesn't exist & log error message → (Merged) created by dieterholvoet
- 🇧🇪Belgium dieterholvoet Brussels
Show in the field edit form when a non-existing plugin is selected and allow to set back to default or another plugin
Done!
See what happens when you completely uninstall the Required API module when fields are configured
The config related to Required API is removed from all fields and those fields are set to be always required. This seems like acceptable behaviour to me.
-
dieterholvoet →
committed 3b4d2a9c on 3.0.x
Issue #3436602 by dieterholvoet, promo-il: The "required_by_role" plugin...
-
dieterholvoet →
committed 3b4d2a9c on 3.0.x
Automatically closed - issue fixed for 2 weeks with no activity.