Nicolas Franck

@briri There is a problem with this commit: https://github.com/DMPRoadmap/roadmap/pull/2333/files If I add a label to every theme, it automatically changes the attribute `for` so it points to the tinymce iframe.

btw archived templates, are those visible somewhere? Otherwise they would disappear from sight.

Possible solution (in `TemplatesController#unpublish`) * On "unpublish" check for plans * If there are plans, duplicate template (`template.create_version!`) * Set `published=false` and `archived=true` on old template (not sure if archived=true...

Or update `Template.generation_version?` from ``` def generate_version? published end ```` to ``` def generate_version? published || plans.count > 0 end ```

Or: on "unpublish", if there are plans for this template, generate a new unpublished version for this template, i.e. with the same family_id. And redirect to that new template controller.

My analysis of the situation. Correct me if I'm wrong. The controller that [unpublishes](https://github.com/DMPRoadmap/roadmap/blob/master/app/controllers/org_admin/templates_controller.rb#L292) the template, fetches all versions, sets the flag `published` to `false`, and then returns to the...

@raycarrick-ed because it is put on the template page. That page states that you can only view other templates if you change to that organisation. It does not state that...

why would you even put project details in the csv? cf. https://github.com/DMPRoadmap/roadmap/issues/3002

What do you mean by "consolidating the functionality"? Merging the functionality of the contributors into the collaborators (would be helpfull)? That would require also adding bitfields for those new roles,...

Some people are inserting tables with links, styling etc... that leads to a lot of html; without css that leads to a lot of characters that users are not aware...