Feature #8095
open
Allow overriding the default text formatting in each project
0%
Description
It would be good to let the text formatting be selected per project, rather than only a global default. It would be useful for bigger installations that have more diverse set of users.
Files
Related issues
Updated by Ebrahim Mohammadi about 14 years ago
It would be nice to let formatting of project's Wiki be selected independently of issues (and other parts') formatting.
Updated by Ebrahim Mohammadi about 14 years ago
I did an implementation found in per-project-formatting in: https://bitbucket.org/ebrahim/redmine-patches/qseries (I've attached an snapshot of the patch)
I'd like to receive reviews and comments on the implementation. I'd also like to know if it could be merged upstream.
Updated by Toshi MARUYAMA about 14 years ago
Redmine has tests.
https://bitbucket.org/redmine/redmine/src/f4d8b015a399/test/
Could you add tests for this patch?
Updated by Ebrahim Mohammadi about 14 years ago
Shall I change and extend existing tests, or shall I write a new test case in a separate file? May you give me an starting point? (I'm not deep into Rails.)
Updated by Ebrahim Mohammadi over 11 years ago
And now the plugin thanks to a-ono: http://github.com/a-ono/redmine_per_project_formatting
Updated by Toshi MARUYAMA over 11 years ago
- Related to Feature #5995: Text formatting can be dfferent base on project added
Updated by Toshi MARUYAMA over 11 years ago
- Related to deleted (Feature #5995: Text formatting can be dfferent base on project)
Updated by Toshi MARUYAMA over 11 years ago
- Related to Feature #617: wiki: thoughts of WYSIWYG added
Updated by Toshi MARUYAMA over 11 years ago
- Related to Feature #4015: Make app settings overridable at project level added
Updated by Toshi MARUYAMA over 11 years ago
- Has duplicate Feature #5995: Text formatting can be dfferent base on project added
Updated by Toshi MARUYAMA over 11 years ago
- Has duplicate Feature #5624: the Text formatting configuration in each project. added
Updated by Toshi MARUYAMA over 11 years ago
- Has duplicate Feature #12095: Per project wiki formatter setting added
Updated by Go MAEDA over 10 years ago
- Has duplicate Feature #19112: Markdown for specific projects added
Updated by Go MAEDA about 10 years ago
- Has duplicate Feature #19591: Text formatting (textile/markdown) configurable on a per project basis added
Updated by Go MAEDA about 10 years ago
- Related to Feature #5112: Texting formatting setting is global (Allow override in module level) added
Updated by George Notaras about 10 years ago
Are there any plans to implement this?
Updated by George Notaras about 10 years ago
Alternatively, a special control tag could be invented, for instance #markup:textile or #markup:markdown, which, if found as the first line of the text, it would indicate the parser that should be used. This is an easy way to add maximum flexibility without having to make decisions about the used markup at the web site or project level. Such a solution would also be helpful in cases where markup needs to be migrated at slow pace page per page.
I hope someone looks into this issue more closely, because right now, IMO, Redmine is doing it wrong.
Thanks in advance.
George
Updated by Jean-Claude Wippler almost 10 years ago
+1
As the original requestor of the Markdown formatting feature, I have to shamefully admit that I have not yet Flipped The Big Switch.
The reason for this is that conversion from Textile to Markdown is an all-or-nothing proposition right now. Having this setting per-project would make it much simpler: not only to convert a site gradually, project-by-project, but also to start new projects off with Markdown. I wouldn't mind sealing some projects and starting fresh ones in some cases, just to force this formatting transition on its users.
So here's my vote to making the Textile/Markdown flag settable for each project!
-jcw
Updated by Jean-Claude Wippler over 9 years ago
What is the status of this feature request? Could and will a per-project Markdown/Textile setting be implemented?
With such a feature, migration becomes a per-project issue, and new projects could be set up appropriately.
That last benefit alone would solve a major headache for me - as it is, I can't even set up a new Markdown area.
I'm eagerly looking forward to a response / verdict from one of the maintainers...
-jcw
Updated by Go MAEDA over 9 years ago
- Related to deleted (Feature #5112: Texting formatting setting is global (Allow override in module level))
Updated by Go MAEDA over 9 years ago
- Related to Feature #5112: Texting formatting setting is global (Allow override in module level) added
Updated by Go MAEDA about 7 years ago
- Related to Feature #28823: Multi-format markup for text fields added
Updated by Go MAEDA about 7 years ago
- Related to Feature #3492: Specify different text formatters for certain parts of Redmine added
Updated by
Updated by Gérard L over 6 years ago
We are using Redmine for several years with textile formating and we would like to switch to Markdown progressively.
Will this feature request be implemented soon ?
Updated by Peter Volkov almost 6 years ago
Currently, we use the following plugin:
https://www.redmine.org/plugins/per-project-formatting
but it would be nice to have this upstream. Or even per page formatting!
Updated by Holger Just over 2 years ago
- Has duplicate Feature #37365: Allow users to choose textile or markdown formatting added
Updated by Stefaan Ellebaut over 2 years ago
+1 on this.
We have a redmine instance containing projects of over a decade. We would like to switch to CKeditor but up till now all is done in textile formatting. Changing the global setting to the new editor would break all existing wiki pages and issue descriptions and notes, which makes a switch impossible now.
Updated by 
Updated by 
Updated by