Tag Archive for 'wymeditor'

Simple WYMeditor and WordPress 2.6

I love WYMeditor, it is by far the best Javascript text editor I have used.  As I have written before, I use the Simple WYMeditor plugin so I can have WYMeditor in my WordPress installation.

However, when I upgraded to WordPress 2.6 it stopped working for me.  There is no new version of Simple WYMeditor as yet, but this little fix worked for me.

Simply change line 69 from this:

69 if ( strpos($wp_version, '2.5') !== false ) {

to this:

69 if ( $wp_version >= "2.5" ) {

Enjoy!

WordPress and WYMeditor

EDIT 22/04/08:
If you use the latest versions of WordPress, Admin SSL and Simple WYMeditor, then this workaround is no longer necessary.

I currently use WordPress to publish my blog, and I recently discovered that there is a plugin () that lets you use my favourite online text editor - WYMeditor - to write blog posts.

So far so good - but I encountered a problem.  I enabled the plugin in WordPress but nothing happened.  Then I discovered that another plugin I use - Admin-SSL, which unsurprisingly secures the WordPress admin pages - was not securing pages from the /wp-content/ directory, which is where the plugins are.  The page was trying to call the WYMeditor plugin script using an unsecured link, which was causing it to break.

So I added the following code to admin-ssl.php at line 370:

370	$content_url = get_option("siteurl") . "/wp-content";371	$secure_content_url = $secure_url . "/wp-content";372	$replace_this[] = $content_url;373	$with_this[] = $secure_content_url;

This fixed the first problem.

However I noticed that the autosave function was not working either.  Apparently some people find it annoying, but I find it extremely useful while I'm writing blog posts.  After spending ages looking through the code of the WYMeditor plugin, through the WYMeditor documentation, and the autosave() function in WordPress, I found a way to fix it.

There is an HTML textarea element called 'content' which WYMeditor replaces, and which WordPress uses to get what you are writing.  When you click the 'Save' button, WYMeditor updates that textarea element with whatever you've written, and WordPress saves it.

However, the WYMeditor plugin only updates the textarea element when you click the save button, so the autosave() function doesn't work - when it looks at the 'content' textarea element, it's empty.  What we need to do, then, is automatically update the textarea element when the autosave() function is called.  Thankfully, WYMeditor has an inbuilt function to do this, called update().

Two things need to be done.  First, open simple-wymeditor.php, which is the main file for the WYMeditor plugin (it's probably in /wp-content/plugins/simple-wymeditor/).  Comment out lines 143 and 168, to look like this:

143	//jQuery( function() {...168	//});

This allows us to access the WYMeditor functions through jQuery.  Save the file and close it.  Now open the WordPress autosave.js file (in /wp-includes/js/).  At line 98 insert the following:

98	if(wym = jQuery.wymeditors(0)) wym.update();

This updates the 'content' textarea element if it can find a WYMeditor object, so the code won't break if you disable the WYMeditor plugin.

So there you have it - my WordPress now works with the WYMeditor plugin, and I'm very happy, and very tired after a couple of hours reading other people's code!

Addendum

In writing this post I used <pre></pre> tags to display the code.  Due to a bizarre filter, WordPress doesn't let you do things like have <br/> tags inside <pre></pre> tags (and many more such combinations).  So the code above, although one block of it is on four lines, WordPress was displaying it all on one long line, having stripped out the <br/> tags.

Cue much more learning of WordPress and code-reading - I now have two plugins.  The first removes the 'wpautop' filter from the 'the_content' and 'the_excerpt' tags.  This stops WordPress stripping tags that it shouldn't - now I'm using WYMeditor it is unnecessary anyway, because it creates XHTML.

The second plugin replaces all the curly quotation marks that WordPress 'helpfully' adds in with straight ones.  Sigh - at least I'm much more aware of how WordPress works than I was!  It's an absolute beast - functions and classes all over the place.  I'm sure it isn't necessary for it to be so complicated.

Top Web Development Tools (Pt. 2)

Part 1: Applications
Part 2: Code Libraries/Resources

6. Smarty

Separating form from content is a holy grail in web design - it allows you to update the user interface of a website without altering how it works. You can even have different colour schemes or skins. Smarty is a template engine for PHP which forces you to separate form and content. It is easy to use, quick to master, and has good documentation.

7. jQuery (not Prototype)

Writing JavaScript can be frustrating at best. Using a JavaScript framework (there are many available) makes things quicker and easier, and they often include simple to use Ajax funcionality. The most common (thanks to Scriptaculous) is Prototype, but I prefer jQuery. It is much smaller, and has similar effects to Scriptaculous (although, admittedly, not as many). It also (I think) has a more logical structure.

8. WYMeditor

WYSIWYG text editors are the scourge of web developers. They often create hideous code and don't work properly, no matter what they claim, and allow users to define what their text looks like, rather than your template. Cue WYMeditor, an What-You-See-Is-What-You-MEAN editor, which creates perfectly structured XHTML code. It allows the user basic formatting tools (bold, italic etc) but not font, size, colour etc. Instead, the user chooses a style type (heading, paragraph, list etc), which can fit into your template easily.

Added to that, it works extremely well, and uses jQuery. It's brilliant!

9. Behaviour

Adding JavaScript events to HTML is as simple as CSS with the Behaviour framework. It is faster than any full JavaScript framework, and works like a charm. I use it in all my projects, and highly recommend it. The script file is small as well, especially if you pack it.

10. JavaScript Packer

If you include JavaScript files in your websites, you'll want to reduce their size as much as possible. Enter Dean Edwards' JavaScript Packer. It hugely reduces the size of JavaScript files, without losing any functionality. I love it.

That's it for now - there may be a part 3, in which I will add any new tools. I hope that someone at least has found these two useful!