Galette » Plugins » Auto

This also concerns any other vehicle property. Not only models.

Otherwise, instead of a warning, would it be possible to disable the remove buttons in such cases in the lists ?

I suppose it would require a way to check if a model or any other property is used.

But then, if this check if possible, wouldn't it be easier to restore batch removal on models and properties ? : this check could simply be used also to disable the corresponding checkbox for batch actions in the lists.

Guillaume AGNIERAY a écrit (#note-1):

This also concerns any other vehicle property. Not only models.

Indeed, I've edited the title and the description.

Otherwise, instead of a warning, would it be possible to disable the remove buttons in such cases in the lists ?

For a quick answer, I'm not in favor of this change because it should be the same behavior everywhere a foreign key is involved (in other plugins and in core).
You can open an evolution request we can talk about; but honestly this does not seem a priority :)

For now, adding a warning is the the most quick and simple solution.

But then, if this check if possible, wouldn't it be easier to restore batch removal on models and properties ? : this check could simply be used also to disable the corresponding checkbox for batch actions in the lists.

Honestly, I'm not sure having batch removal on all screen as it was before is really required; and I'd prefer to limit the amount of work as possible for the release to come.

If users complains, we can reactivate.

Johan Cwiklinski a écrit (#note-3):

For a quick answer, I'm not in favor of this change because it should be the same behavior everywhere a foreign key is involved (in other plugins and in core).
You can open an evolution request we can talk about; but honestly this does not seem a priority :)

For now, adding a warning is the the most quick and simple solution.

I agree.
I'm not a user of this plugin. It was just a suggestion ;)

Honestly, I'm not sure having batch removal on all screen as it was before is really required; and I'd prefer to limit the amount of work as possible for the release to come.

If users complains, we can reactivate.

+1