Deactivation of a sharable should not be a little checkbox in the edit page.
In fact activation or not is a different kind of info. That is why it should need a different place.
I could as well imagine storing in the database a "last toggle" date to indicate since when a sharable has been deactivated or since when it has be (re)activated. This will start with the first "activate" clic by the manager.
Funny idea : instead of storing a classic bool (0 or 1), I could store a int using a method isActivated() sending true if the number can't be divided by two and false if it can. That way, I just have an info of how much times it has been activated. LOL
It's really if you don't want to create an activate table with manyToOne relationship :smile: @n-peugnet
Deactivation of a sharable should not be a little checkbox in the edit page.
In fact activation or not is a different kind of info. That is why it should need a different place.
I could as well imagine storing in the database a "last toggle" date to indicate since when a sharable has been deactivated or since when it has be (re)activated. This will start with the first "activate" clic by the manager.