The attached patch adds an nl2br option to the field configuration of Views.
Situation:
* one cck text area using plain text added to my node type
* newlines are presented as br tags on the node page
* Using the same field in a view just pints the newlines, letting HTML ignore them
I know that this presentation issue could also be solved by using filtered text instead.
But the added overhead does not seem worth it as it would also make me dependent on better_formats.
The patch works for both 2.x-dev and 3.x-dev
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 991202-nl2br_option-3.patch | 1.63 KB | dawehner |
| #7 | views-3.x-nl2br_option-3.patch | 1.96 KB | helmo |
| #3 | views-3.x-nl2br_option-2.patch | 1.97 KB | helmo |
| views-3.x-nl2br_option.patch | 1.88 KB | helmo |
Comments
Comment #1
dawehnerUpdate status
Comment #2
dawehnerIt would be cool to provide a link to php.net so the user can inform what nl2br does.
Comment #3
helmo commentedGood point, I added the php.net link to the patch.
Comment #4
dawehnerEven i don't understand why you have to add target blank, the rest looks fine.
Comment #5
helmo commentedIf the target attribute were absent the php.net page would be loaded in the same window. Thus losing the current drupal page.
Comment #6
dawehnerPersonally people should be intelligent enough to use tabs.
Additional target isn't XHTML strict.
Comment #7
helmo commentedIn my case Firefox is clever enough to know I prefer them in a new tab.
But as for the xhtml strict spec... I've removed the target attribute from the patch.
What do you think about the rest of this patch?
Comment #8
merlinofchaos commentedThere's no need to expose nl2br() at all to the user. Telling them we'll convert newlines to br tags is good enough.
Comment #9
dawehnerRemove the comment about nl2br
Comment #10
helmo commented@merlinofchaos: I can understand that we should not overload the user with extra info.
Comment #11
merlinofchaos commentedCommitted to D6-3.x and D7-3.x