Project

General

Profile

Actions

Defect #843

closed

BR tags no longer working in textile

Added by Rocco Stanzione about 16 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Wiki
Target version:
-
Start date:
2008-03-12
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix
Affected version:

Description

I have lots of <br> or <br /> tags in my wiki pages, which are now rendered as text. From the docs I don't see another way to force a break. I wasn't paying very close attention but I assume this was changed in r1216. Could we add this to the list of respected HTML tags? Better yet, could we make that list configurable?

Actions #1

Updated by Jean-Philippe Lang about 16 years ago

Actually, there's no need for br tags. You can just use the carriage return.

This:

line 1
line 2

Displays:

line 1
line 2

Do you have an example where a br tag is needed ?

Actions #2

Updated by Rocco Stanzione about 16 years ago

Yeah carriage returns will do line breaks, but like other whitespace consecutive ones aren't respected. Where I'm using the br tags is mostly after wiki tables, where there's an unattractive lack of whitespace between the table and the, say, h2 that comes after it. So, I really only need it for vertical whitespace, not just line breaks. I'll do an example here...

this is a table
with just two rows

And this is a header

There are three carriage returns between the table and the header, and I don't seem to have a way to add actual whitespace between them.

Actions #3

Updated by Mateo Murphy about 16 years ago

Your issue might be better handled by modifying the wiki's css styles to add margins to the bottom of tables and/or the top of the headers. Are you finding you need extra whitespace after something other than a table?

Actions #4

Updated by Rocco Stanzione about 16 years ago

r1259 made me happy - if no one else wants br tags, this issue is safe to close.

Actions #5

Updated by Jean-Philippe Lang about 16 years ago

  • Status changed from New to Closed
  • Target version set to 0.7
  • Resolution set to Fixed

Fine. Reopen if needed.

Actions #6

Updated by Morbus Iff about 16 years ago

  • Status changed from Closed to Reopened

Reopening. This killed my wiki.

I have complex HTML needs for a wiki (such as a global Navigation box that appears in the header of every page, and includes <div> formatting) and also go back and forth between a local HTML document and the wiki. I need the ability to include raw HTML in the wiki and have it work as expected. I've now got a 100 page (private) wiki which is horrifically broken due to the escaping :(

Perhaps we could get some sort of <raw> or <html> tag? Textile is not everyone's savior.

Actions #7

Updated by Morbus Iff about 16 years ago

+1 to allowing ALLOWED_TAGS be editable in the admin, per project.

Actions #8

Updated by Eric Davis about 16 years ago

+1 to allowing ALLOWED_TAGS be editable in the admin. I use blockquote all the time to reference quotes and it's hard to use the Textile bq. on every paragraph. Should have the same rules for issue descriptions.

Actions #9

Updated by Jean-Philippe Lang almost 16 years ago

  • Target version deleted (0.7)
Actions #10

Updated by Jack Christensen over 15 years ago

+1 to editing ALLOWED_TAGS. I need to have line breaks in tables and now I have to monkey patch to allow br's.

Actions #11

Updated by Arndt Lehmann over 15 years ago

+1: I am also looking for a way to have line breaks within table cells.

Actions #12

Updated by Eric Voisard about 15 years ago

+1: I see many reasons why consecutive line breaks should be respected: readability, page layout, respect to copy&paste structure of text files such as logs, traces, etc... well, all pertain to readability in fact...

Maybe convenience as well: we should expect people updating wikis not all being web developers but MS Word and the like users: with the tools they are used to, when they press <return> several times, it puts space between their lines of text. It's basic and it's the most straightforward way to adjust page layout.
When they (well me too!) do the same in Redmine's wiki editor, I think they expect the same behavior, especially since they can enter blank lines in the editor...

Besides this, thanks to Redmine's Team for the very nice software
Eric

Actions #13

Updated by Richard Pecl about 15 years ago

+1: for advanced wiki formatting <div> is essential

Actions #14

Updated by Emrah KAVUN almost 15 years ago

Any update regarding this issue?
I am using Redmine 0.8.4.stable.2819 and my html tags are not interpreted. E.g.: <br /> doesn't put a line break. (seems to be the case here too)

Any possible changes I could make in redcloth3 configs?

Actions #15

Updated by Jack Christensen almost 15 years ago

Put the following in an initializer:

RedCloth3::ALLOWED_TAGS << "br" 
Actions #16

Updated by Emrah KAVUN almost 15 years ago

Thanks a lot, it worked perfectly fine.

Actions #17

Updated by Jean-Philippe Lang about 14 years ago

  • Status changed from Reopened to Closed
  • Resolution changed from Fixed to Wont fix

+1: I see many reasons why consecutive line breaks should be respected: readability, page layout, respect to copy&paste structure of text files such as logs, traces, etc

Using pre tags is great for logs or stack traces.

Actions

Also available in: Atom PDF