Closed (fixed)
Project:
Workbench Email
Version:
8.x-1.x-dev
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Feb 2017 at 15:00 UTC
Updated:
17 Aug 2017 at 06:35 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
larowlanRight, because the transition config entity has third party settings that point to the template.
This means the transition config entity has a dependency on the template (you should see this in the yaml).
This is standard behaviour in core.
Eg. if you create view that depends on a field, and then delete the field, the view is also deleted.
The alternative is that it will be horribly broken.
E.g. the transition depends on a config entity that no longer exists.
Comment #3
fdyckhoff commentedSorry, but then I don't think this is designed very well... ^^"
When I delete an email template, which I consider is only an addition to a moderation state transition entity, the whole transition entity is deleted? Why? When my transition has more than 1 relation to an email template and one of them is deleted, will the transition also be deleted?
If this is really the preferred behaviour, than - please - add an information about it in the delete form of the email template. We did have the use case that we wanted to delete an email, but we did not want the remove the transitions on the same time and were suprised by that
Comment #4
larowlanYep, I think that it's a good idea to warn about what you're going to remove.
Comment #5
dpiAdded a patch that uses the config entity delete form so the user is warned (see screenshot) that dependent configuration is removed.
This should mitigate the problem that transitions are removed without warning. However I think this issue should still be open. Dependent transition configuration should not be deleted, but updated to remove the templates being deleted.
Comment #7
larowlanThanks, let's open a new issue for updating the dependents in a preDelete or some such.