Version 1.1 adds a few usability improvements:
- a spinner is displayed while loading and saving data
- pressing escape while editing will remove the form
- pressing enter while editing a text input will submit the form
Also, it allows you to edit custom taxonomies, just like you would edit post tags. I recommend the Simple Taxonomies plugin for creating custom taxonomies.
Here is a code example:
<?php the_terms($post->ID, 'mytax'); ?>
To make it work in WP 2.8 *, you have to open wp-includes/category-template.php and find the_terms() function. Then, you have to make it look like this:
function the_terms( $id, $taxonomy, $before = '', $sep = ', ', $after = '' ) { $term_list = get_the_term_list( $id, $taxonomy, $before, $sep, $after ); if ( is_wp_error( $term_list ) ) return false; echo apply_filters('the_terms', $term_list, $taxonomy, $before, $sep, $after); }
____
* You don’t have to do this if you’re using WordPress 2.9 or newer (see #10600).

Totally amazing! This is incredible. Keep up the good work!
Hi Scribu,
I seem to have a weird, but nasty problem with the latest version of Front-End Editor (v1.1.3). When installed and activated, any person with the contributor or editor role (any role with edit_posts and/or edit_published_posts) gets the white screen of death after logging in to the admin area. I can reproduce this consequently and was wondering if you changed anything which might cause this (although I can’t seem to find this in your changelog). This didn’t happen with all earlier versions and doesn’t happen with Front-End Editor deactivated.
I’d love to activate Front-End Editor again, as we use it all the time, but for the moment I just can’t seem to use it on our multi-author blog. Thanks for investigating this!
Please add these two lines to wp-config.php
and then activate the plugin.
I’m seeing all kinds of errors (which I didn’t know of), but not one which points to Front-end Editor. These errors show with or without the plugin activated:
1. Activated Front-end Editor
2. Logged on with my Author role user
3. White screen (except for the errors below)
4. Deactivated Front-end Editor
5. WordPress Admin displays
Obvious note: Yes, I’m running PHP5 (5.2.9)
Notice: Use of undefined constant BM_KEYWORDLINK_OPTION - assumed 'BM_KEYWORDLINK_OPTION' in /***/wp-content/plugins/blog-mechanics-keyword-link-plugin/bm_keywordlink.php on line 21
Notice: Trying to get property of non-object in /***/wp-includes/general-template.php on line 366
Notice: Undefined index: trackregistration in /***/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 613
Notice: Use of undefined constant PRLI_PLUGIN_NAME - assumed 'PRLI_PLUGIN_NAME' in /***/wp-content/plugins/pretty-link/prli-config.php on line 2
Notice: Use of undefined constant PRLI_PATH - assumed 'PRLI_PATH' in /***/wp-content/plugins/pretty-link/prli-config.php on line 3
Notice: Use of undefined constant PRLI_MODELS_PATH - assumed 'PRLI_MODELS_PATH' in /***/wp-content/plugins/pretty-link/prli-config.php on line 4
Notice: Use of undefined constant PRLI_VIEWS_PATH - assumed 'PRLI_VIEWS_PATH' in /***/wp-content/plugins/pretty-link/prli-config.php on line 5
Notice: Use of undefined constant PRLI_URL - assumed 'PRLI_URL' in /***/plugins/pretty-link/prli-config.php on line 6
Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in /***/wp-includes/functions.php on line 2918
Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in /***/wp-includes/functions.php on line 2918
Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in /***/wp-includes/functions.php on line 2918
Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in /***/wp-includes/functions.php on line 2918
Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in /***/wp-includes/functions.php on line 2918
That’s odd, especially since version 1.1 dealt mainly with JavaScript, not PHP.
In the mean time, you can roll back to an older version.
Do you still have 1.1 available? (not the new subrelease, but the one where you first introduced the spinner). That one had been working flawlessly, but I don’t see that version on the older plugin page.
P.S. Good suggestion, forgot about that, but also wanted to inform you first.
It is available now.
Should be fixed in 1.1.4.
Yes, confirmed. Thanks!
What a great plugin! Two things though:
1) I have the wysiwyg disabled and when i double click on the page, it only shows me part of the code. Seems height is incorrect and there is no way for me to scroll down to see the rest of the content to edit.
2) Could the plugin be corrected so that it doesnt invalidate my xhtml markup?
1) See that you don’t have the paragraph option set. As for the height, what browser are you using?
2) I guess it could be made to use div-s instead of span-s.
Of course I have styling set to my paragraph tags, but obviously to height is not set for paragraphs. I tried playing around with the css to no avail though. I am using FF 3.5.1 on Windows 7
Both issues you mentioned should be fixed in version 1.2.
I wrote my own theme and have been trying to get FEE to work in it. It installed fine, I’m running PHP5… but double clicking doesn’t do anything. I see FEE code inserted in my html (stylesheets, front-ed classes, a frontEditorData object, etc) but nothing is happening – not even an error…
What am I missing?
First, add this to wp-config.php:
ini_set(‘display_errors’, true);
Next, use Firebug to see what’s happening with the AJAX.
Oddly, I don’t get any errors with firebug at all. I inserted the ini_set in wp-config – reloaded the page with firebug open to console (also tried net to see if I got a 404 or something), and I get no errors at all. Nadda. Yes I’m logged in.
When doubleclicking on a field, you should see an ajax request being made.
Oh, you should also add this line:
define(‘WP_DEBUG’, true);