Check for the real default media source value and don't use a fixed v…#16962
Check for the real default media source value and don't use a fixed v…#16962Jako wants to merge 1 commit into
Conversation
|
@Jako @Ibochkarev: You're misinterpreting what the purpose of this line is—It's to prevent the built-in Filesystem Source (which should always be id 1) from being deleted. That source is not necessarily the default source in a multi media source setup. As such, no change is needed. Perhaps a short doc block above the line in question explaining this could be helpful though. |
|
@smg6511 After I have seen the installations of one client, I think a bit different about this: the media source 1 of several installations was changed into a 'Client Media Source' and pointed to something like If we don't want that media source 1 to be deleted, we also have to make sure that it can't be edited, too. Since this would be a bit too restrictive to me, the check for the |
|
@Jako - We actually already more clearly established the |
|
Then at least the default_media_source system/context/user setting check should be added there to disallow these sources too. |
|
@Jako You raise a good point and the UX can definitely be improved. I think the best way, rather than disallow the removal of a non-built-in source that's specified as a default, would be to mark the current default in the Sources grid (maybe via an icon or asterisk after the name) and maybe add a variation on the current warning/confirmation dialog that addresses the implications of removing that source. |
|
The getlist processor can check for the default media sources in the system/context/user settings and return these values. The warning message can be extended with the value of the processor. |
What changed and why
Check for the real default media source value and don't use a fixed value.