Posted 3 years ago #
Hi All,
Is there a way to disable the WYSIWYG editor in WP 2.0? I'm much more comfortable using markdown syntax, and I personally feel that the HTML the WYSIWYG editor produces can be a little unpredictable.
I've wandered through the options panels and haven't seen anything in there, and also a search here using 'disable wysiwyg' didn't turn up anything relevant.
Much warmth,
planetthoughtful
Posted 3 years ago #
It's carefully concealed in a tickbox at the bottom of your user profile page.
Posted 3 years ago #
In retrospect I guess that makes some sense, but for some reason it seemed to me to be much more like something you'd find under options.
Thank you for the help, and for the (cough) restrained sarcasm.
Much warmth,
planetthoughtful
Posted 3 years ago #
I'm starting to think that for each user a section should appear at the end of Options > General (or maybe we need an Options > Personal ?) that displays it. Certainly a bit more logical (*ahem*) than having to look under ones profile.
Posted 3 years ago #
I tend to think it should be an option on the editing page itself. That's certainly where I would expect to see options relating to switching modes in an editor...
@planetthoughtful: any perceived sarcasm wasn't directed at you. I think the option is in a very silly place, and not at all where I'd reasonably expect people to look.
Posted 3 years ago #
Is there a way to truly disable the HTML from automatically being added in? I've disabled the visual rich editor already, but WP keeps on adding in unwanted tags whenever I use a line break. It's starting to annoy me and I was wondering if there was a way to disable this without having to edit files myself.
Thanks.
P.S. I agree that the option should appear on the actual posting page.
Posted 3 years ago #
chewbacca:
Posted 3 years ago #
Thank you very much, Kafkaesqui. It wasn't exactly what I was hoping for, but I'm happier with a plugin than editing an original file. :)
Posted 3 years ago #
I agree that the post page would be a much more visually and thematically obvious place to put it. It might cause some complications, since I doubt (but honestly don't know) you'd be able to refresh the display via AJAX, which would mean submitting the page and presumably any changes you made to the post to display the editing interface you'd picked. I'm sure you could handle that with a messagebox advisory saying 'Warning: this will submit any changes you've made to your post. Continue?'
I'd also, however, like to see a global setting under options. Something like an 'Allow users to use the visual rich editor when writing', with a second choice enabled to indicate 'Default: On' or 'Default: Off'.
Maybe it's just me - I assume tinymce has its fans, but to me it seems like the blog equivalent of using FrontPage.
Posted 3 years ago #
"I'd also, however, like to see a global setting under options. "
That already exists under Options > Writing. Look for "Users should use the visual rich editor by default"
Posted 3 years ago #
@Kafkaesqui: Sigh. I need more sleep. Thanks for pointing that out.
Posted 3 years ago #
Although, in a pointless attempt to salvage some credibility, it's not quite what I was talking about, since I'd like see an option for the admin to disable tinymce entirely. But, yes, I should have noticed that option before letting my fingers demonstrate that I'm an idiot.
Posted 3 years ago #
"I'd like see an option for the admin to disable tinymce entirely."
Just delete the tinymce directory under wp-includes/js/. That'll do it. :)
Posted 3 years ago #
Ah, shaddup. ;-)
Posted 3 years ago #
No, really it works!
;)
Posted 3 years ago #
Lol, I'm sure it does, and I will give it a try. That was more meant to be an irascible 'thank you'.
Posted 3 years ago #
Aaah, with ticking this box, I have removed the one thing that had always driven me crazy with Wordpress, which otherwise is just awesome. And life can run smoothly again.
Yes, I wouldn't have looked in my user profile either, but I guess this makes sense for enabling/disabling on a per-user basis ?
This topic has been closed to new replies.
