old entries, switching (non/wysiwyg) Editor mode
Posted: Sat May 25, 2013 7:05 pm
I just discovered a behaviour I did not think of before...
When having an existing blog running in non-wysiwyg-mode, all entry (default) ENTER breaks are stored as \n in the database.
So now it comes, someone wants to switch over to an Editor mode and enables the wysiwyg config option, the new situation won't recognize these old entries to be read as linebreaks, or <p>. Just imagine the one has some hundreds entries or even more...!
Vice versa - after some entries are made with the editor - it is no problem, since the new entries seem not to be touched by nl2br (whyever...).
Is that a Problem of my new Plugin, or my personal configuration, or has that been like this in every EDITOR "Plugin" before? I do not want a new discussion about the use and sense of the nl2br plugin, but this may hit many people out there, not being sure what they want to use (forever), wouldn't it?
Can anybody report some experiences with that?
If is, can we do anything persistent about it, without changing into a big mess?
When having an existing blog running in non-wysiwyg-mode, all entry (default) ENTER breaks are stored as \n in the database.
So now it comes, someone wants to switch over to an Editor mode and enables the wysiwyg config option, the new situation won't recognize these old entries to be read as linebreaks, or <p>. Just imagine the one has some hundreds entries or even more...!
Vice versa - after some entries are made with the editor - it is no problem, since the new entries seem not to be touched by nl2br (whyever...).
Is that a Problem of my new Plugin, or my personal configuration, or has that been like this in every EDITOR "Plugin" before? I do not want a new discussion about the use and sense of the nl2br plugin, but this may hit many people out there, not being sure what they want to use (forever), wouldn't it?
Can anybody report some experiences with that?
If is, can we do anything persistent about it, without changing into a big mess?