It drives me (and many others) nuts that, for whatever reason, when we try to force line breaks WP strips them out. There is a lengthy discussion at http://wordpress.org/support/topic/73161.
This problem is not limited to Macs and absolutely drives me nuts. There are times when we want to force an extra line between text and WP should not prevent us from doing so.
I set up my wife's blog, and she is forever battling with the editor trying to make it display how she wants.
She needs to use the WISIWIG editor as she is not HTML proficient, but I am forever having to dive into the raw HTML to fix things that the editor mucks up.
Heartily agreed. Ever since 2.0.5, the editor seems to be doing some wacky things, more than just not putting line breaks in. It's been removing some of my paragraph breaks as well.
This seems related to
Line break conversion...
http://wordpress.org/extend/ideas/topic.php?id=154
ohh yess.
Please.. i hate the fact that ALWAYS i must go to the HTML editor to fix line breaks and paragraphs format.
PLEASE... im beggin'
xD
SIllA!
Please, please, please make this change! I have been up most of the night working on this. I have tried everything suggested to no avail. I have one last idea. I have modified both the js/tinymce/tiny_mce.js file and the wp-includes/js/tinymce/tiny_mce_gzip.php file as instructed. Now, I am not a programmer by any means. In fact, I'm only just now beginning to learn css. However it seems to me that if these two files work together in any way they have to not be fighting one another, so I went back into the js/tinymce/tiny_mce.js file and changed the top three parameters back to the original:
this.defParam("force_br_newlines", false);
this.defParam("force_p_newlines", true);
this.defParam("convert_newlines_to_brs", false);
and changed ONLY the fourth parameter to:
this.defParam("remove_linebreaks", false);
Then I went back to the wp-includes/js/tinymce/tiny_mce_gzip.php file and changed only a single parameter:
remove_linebreaks : false,
I don't know if it's going to work, but it's worth a shot.
This fix is absolutely necessary. If WordPress purports to give any sort of control to its users as authors of their work, please look into this as soon as possible.
As a summary, here is the user problem: Line breaks and indents at the beginning of paragraphs are removed as soon as they are inputted. This forces all text to run together, making for a very cluttered textual experience.
Fruitvale, you mention indents in addition to line breaks. There is no HTML equivalent for just putting an indent at the beginning of a paragraph - tabs don't exist and leading spaces are ignored (as are multiple spaces).
So yes to the line break issue, but if you want your paragraphs indented, you'll have to use CSS and create a style for it.
the only correction that worked for me is use &nsp; and then use another /br/ tag
I still have this problem and its really doing my head in.
Like others on all the other threads about this...
http://wordpress.org/extend/ideas/topic.php?id=154&page&replies=3
(2 months ago, 3 replies)
http://wordpress.org/extend/ideas/topic.php?id=11&page&replies=11
(2 months ago, 11 replies)
http://wordpress.org/support/topic/76657?replies=2
(9 months ago, 2 replies)
http://wordpress.org/support/topic/74129?replies=32
(9 months ago, 32 replies)
http://wordpress.org/support/topic/73161/page/2?replies=46
(10 months ago, 47 posts)
http://wordpress.org/support/topic/52958?replies=19
(1 year ago, 27 posts)
...I can't believe that WP has messed this up so badly and for so long (over a year).
All we want is line breaks. Is that really too much to ask?
When I did what cutout suggests in one of the threads above I thought I'd solved the problem (for a moment), because when I clicked on html button and manually added and then update, the line break were still there, and when hit html again they were still there too, but as soon as I actually hit save and viewed the page, there were no line breaks!
I've tried changing some of the parameters in the tiny_mce.js file too, but to no avail.
Please, please, please, someone fix this bug!
I'm on WP 2.0.2 but from what I hear from friends 2.1 still has this problem.
HELP!
/me cries
Just a suggestion, but WordPress should keep any and all HTML tags entered in via the Code tab and only do filtering/parsing like this if the you use the Visual tab.
Warning - I haven't tested this extensively ...
The following appears to work for me (Firefox 2.0 Windows; WordPress 2.1.3):
1) Disable the visual editor via the User options screen
2) add the following line in
wp-includes/formatting.php
as the first line in the wpautop() function:
if ( preg_match('/<!--DISABLE_WPAUTOP-->/', $pee) ) return $pee;
Basically what I'm doing here is saying that if I put in a specific HTML comment in my post, then I disable the wpautop() function for that particular post. And I do step #1 above because if I add this hack with the visual editor turned on, then when I go back to edit posts, I end up with all of my HTML that I added getting removed.
So, I figure that this is a nice way to solve this problem for people like myself who want to have complete control while still allowing other contributors for my blog to continue using Word Press as a WYSIWYG HTML editor.
This is something that is needed, but it wouldn't make me use the 'visual editor'. If I want some shiny piece of garbage that can't take advantage of half the features Wordpress has, then I'm perfectly capable of downloading Windows Live Writer :P
Either there are a lot of people here who don't know how to type a linebreak, or this has been fixed in a recent WordPress 2.1 release.
In WordPress 2.1, in the visual editor, using Firefox: Typing Enter gives you a paragraph break. Typing Shift-Enter gives you a linebreak. Just like a word processor.
Paragraph breaks cause a new P element to be started, linebreaks are translated to BR elements.
No HTML knowledge is required. No hacks are required.
Yes, I know how that works and I don't have a problem with that. My problem (and I suspect I'm not the only one) is that WordPress insists on adding BR and P elements into my Post or Page entry even when I use the Code tab. If I go to the trouble to use the Code tab, then WordPress should use the HTML EXACTLY as I entered it and NOT put in any extra elements.
That is why I came up with a hack to get WordPress to quit messing with my HTML! And this isn't an issue of me being picky and wanting my HTML just so (though if that were the case, I don't think there is anything wrong with that). There have been several times where I wanted to put something in a Post, like a Java APPLET and WordPress decides to add in P elements inside my APPLET tag (only PARAM elements should be inside the APPLET element).
You must log in to post.
This idea is under consideration.
