The text editor, used across many parts of your Ning Networks, has just been revamped with some fixes and improvements.
As many Network Creators have pointed out, the text editor on the Pages feature can add unwanted line breaks when switching between HTML and Visual mode. The issue: <br /> tags were added at the end of each line of text after switching back to HTML view.
This has now been fixed, and should no longer occur on Pages.
We've added a new "Autorecover" feature to the text editor to help anyone who accidentally loses what they were working on in the text editor. After working on a blog post, discussion or broadcast message that is at least 50 characters long, you'll notice an "Autorecover" link appear at the bottom of the editor:
If you refresh the page (or your browser crashes for some reason and you return to the page), you'll see the Autorecover link appear. Click it, and the last-saved version of the post will appear! This Autorecover link will be available for up to 20 minutes (new versions are saved every 60 seconds).
If you use the blockquote function a lot, you may have noticed that there can be a problem with the blockquote tool in the text editor: You can't un-blockquote text after you have turned blockquoting on.
That problem was caused by turning off a rule in the text editor that wraps your text in <p> tags, even when using HTML mode. To fix the blockquoting issue, we're testing out a new option for NCs to force all text to be wrapped in <p> tags, even when using the HTML view — which today uses <br /> tags each time you hit return.
You can find the new checkbox on the Text Editor page in your Dashboard, under the "Features" section of your Settings:
Hit the checkbox for "Switching to WYSIWYG view forces all text in paragraph tags," and all of your paragraphs will use <p> tags. And, your blockquote button should work correctly.
We'd love your feedback on how you like this option. We're considering rolling it out platform-wide, but we want to hear how you use it.

Permalink Reply by Patrick Chappelle on July 19, 2011 at 4:54pm
Permalink Reply by ismail shah on July 19, 2011 at 5:00pm 
Permalink Reply by Speed Racer on July 19, 2011 at 6:00pm 
Permalink Reply by Writer Chick {Diane} on July 19, 2011 at 6:26pm
Permalink Reply by Kath on July 19, 2011 at 7:03pm
Permalink Reply by Emmanuel Ace on July 19, 2011 at 6:31pm 
Permalink Reply by soaringeagle on July 19, 2011 at 7:07pm i love love love thre autocomplete feature theres just 1 thing id like to see fixed
someimes when i say fix a typo (i typo alot) then use the down arrow key to bring the curser back to the end of the typed text the curser looks like its at the end however when u hit enter, it inserts the <p> or </ br> after the 1st letter you typed in the post (i often dont watch what im typing so it really screws me up)
example
intended post
hi i like ning sites theyre cool blah blah blah
so umm i got nothing much to say blah blah blah
gee never thought making up phony text would be so boring
now say i typed nothimg and corrected that after typing the last blah on that line hit down arrow to get to the end of line 2 then enter to start line 3 you get this
h
gee never thought making up phony text would be so boring
i i like ning sites theyre cool blah blah blah
so umm i got nothing much to say blah blah blah
this issue happens to me all the time
Permalink Reply by Arnold Burian on July 20, 2011 at 4:34am 
Permalink Reply by soaringeagle on July 20, 2011 at 5:36am it drives me insane too
its an odd lil bug too isnt it cause it doesnt just start at tye tiop, but after the 1st letter
James Higginson replied to Tim's discussion 'Ning Slow Today?'
AnGella replied to PeruCool's discussion 'Alternatives to Ning social network'
Alexander replied to Alexander's discussion 'Move header image to top!'
Riccardo Rossini replied to Riccardo Rossini's discussion 'problem in redirecting NING 3.0'
Riccardo Rossini replied to Riccardo Rossini's discussion 'problem in redirecting NING 3.0'© 2013 Created by Ning.
