decidim / decidim

The participatory democracy framework. A generator and multiple gems made with Ruby on Rails
https://decidim.org/
GNU Affero General Public License v3.0
1.43k stars 395 forks source link

Category-subcategory misbehaviour with proposals #1255

Closed xabier closed 7 years ago

xabier commented 7 years ago

This is a Bug Report

:tophat: Description

:clipboard: Additional Data

xabier commented 7 years ago

Mmmm, it seems that this mistake is the result of deleting subcategories. So it needs to be rewritten: when subcategories are deleted, the proposal should inherit the category it belonged to

andreslucena commented 7 years ago

IMHO this kind of deletion and renaming need to be clear and explained well before the destructive action. It's tricky to do it right.

For instance, Discourse doesn't allow to delete an user if the user has any post, you can only anonimize it; if you really want to delete it, first you need to delete the posts:

imatge

On this case, my proposal is that before deleting a Subcategory/Category that has any content associated, we should give a warning like "you can't delete this category until you move or delete all the posts that belongs here". @xabier how do you see something like that?

xabier commented 7 years ago

@andreslucena sounds good to me, we were experimenting with metadecdim process, cleaning categories, this should not happen with participatory processes, at most proposals should be potentially re-categorizable.

I think it is good to show the warning and to make impossible to delete a non-empty category. As I said it would be good to have the option to re-categorize a proposal (this doesn't change the content, although some misuses of this functionality are imaginable).

mrcasals commented 7 years ago

I'm +1 on not deleting the category if it has any content first