Possibility of disabling categories and entries per site / language

[bzin]

Description

Add the possibility of disabling categories per site/country/language.

The scenario I am having is that I have a list of brands (which are in a stored in Categories) that I use the multiple sites. The functionality is required since I do not want to use this category in a specific site or give access to it to an editor of a particular site/country/language.

[carlcs]

What I think you really want is something like this: #2386, but for categories. Because a disabled category would still show in “Add a category“ modals, with the enabled attribute set to false.

[bzin]

@carlcs I believe that would definitely work.

It would be great to have something like this when adding a category to a category group

[bzin]

Thinking better on this, I believe it would be better not to remove the propagation because I do not want to lose the relation that this gives to the data.

[bzin]

Issue Update
Renamed the title of the issue since I tried to achieve the same result by using a Channel section with the propagation on instead of categories (suggested by @carlcs).

In that case, the issue is still the same. Disabling one data item disables all in different languages. It makes sense that this would not happen, and in this case, we do not want to remove the propagation since the data relation can be necessary for various reasons.

Scenarios
A News Channel with multiple language translations. The article (entry) is the same but translated into various languages. I cannot expect that all entry is corrected transcribed at the same time. In this case I should be able to disable this without disabling in all other languages.

From a Category Group, some categories are only relevant on specific languages. I would like to disable some on different websites. Again, the relation of these is necessary to do different relations on the data added to the CMS.

Need
Have categories and entries that can be disabled in the different languages existent on the CMS installation.

[carlcs]

I‘m still understanding correctly that “disabling” means hide in the CP element indexes for you, because on the front end all of this is possible very easily.

I think the planned Smart Sources feature might help in the future #1630, and currently you could look into modifying sources via the provided hooks.

[brandonkelly]

This is a duplicate of #2122.