Changed behavior of (de)activating an item within the change form: 
Changed behavior of (de)activating an item within the change form: 

Instead of changing all descendants' active status to the current item's, it will only change the descendants' active status if the item is False.

As it makes sense to have an item active, but its children inactive, it doesn't make sense that an item is inactive, but its descendants are active.

This doesn't change the activate/deactivate admin actions. They will always  affect an item and its descendants.
Nekmo/django-categories,DylannCordel/django-categories,GabrielDumbrava/django-categories,webu/django-categories,gavinhodge/django-categories,msaelices/django-categories,WarmongeR1/django-categories,lincolnloop/django-categories,s1n4/django-categories,epicserve/django-categories,theatlantic/django-categories,theatlantic/django-categories,epicserve/django-categories,kjefes/django-categories,callowayproject/django-categories,WarmongeR1/django-categories,callowayproject/django-categories,lincolnloop/django-categories,miceno/django-categories,GabrielDumbrava/django-categories,epicserve/django-categories,gavinhodge/django-categories,miceno/django-categories,Nekmo/django-categories,miceno/django-categories,Nekmo/django-categories,DylannCordel/django-categories,ZhiweiWang/django-categories,kjefes/django-categories,kjefes/django-categories,s1n4/django-categories,callowayproject/django-categories,lincolnloop/django-categories,msaelices/django-categories,DylannCordel/django-categories,ZhiweiWang/django-categories,theatlantic/django-categories,gavinhodge/django-categories,msaelices/django-categories,WarmongeR1/django-categories,s1n4/django-categories,webu/django-categories,ZhiweiWang/django-categories,GabrielDumbrava/django-categories,webu/django-categories