It’s now possible to create arbitrary groups of editable elements. This opens the door for a lot of possibilities. For example, you can now edit all fields of a post at once, instead of one at a time. Go to the FEE settings page to enable it.
One feature that was often requested was the ability to create posts from the front-end, not just to edit them. This is now possible by using the fee_inject_dummy_post() template tag.
This release features the most recent version of Aloha Editor available, 0.20.0-RC9. This fixes the jQuery compatibility issues, as well as a bunch of other bugs. Thanks again to Jotschi for lending a hand with this.
Thanks to AppThemes and Jason Buksh for supporting this release financially.
This version integrates Aloha Editor, a rising star on the wysiwyg editor scene. Unlike other established editors like TinyMCE, it makes the content editable inline, rather than using an iframe, which means that all the theme styles are preserved.
Also, unlike the rich-text editors previously integrated into Front-end Editor, Aloha is being developed by a whole bunch of contributors and is also backed by Gentics, the company that originally wrote and subsequently open-sourced it.
Jotschi, one of the Aloha developers, was working on a similar WordPress plugin; it just made sense for the two of us to combine our efforts. This release wouldn’t have happened without his help.
This is just the beginning. We have a lot of ideas related to Aloha Editor that we haven’t implemented yet. So, try it out and let us know what you think.
Thought I’d do another release before year’s end. It is focused on improving the existing features rather than adding new stuff.
The tooltip looks sexier now. It resembles the one on the iPhone:
When you click a link inside the rich editor, a gmail-like tooltip will appear:
Another usability improvement is limiting the maximum height of the wysiwyg editor to the window height, so that the controls are always visible. This way, you don’t have to constantly scroll up and down from the text you’re editing.
For developers: I’ve moved plugin development to github:
Although Front-end Editor tries to be compatible with as many themes as possible, there’s only so much it can do.
No wp_footer() call
<?php wp_footer(); ?>
Using custom versions of jQuery
Some themes, for one reason or another, use their own jQuery file. When a new version of WordPress is launched, the bundled jQuery library is also updated, but the theme is stuck using it’s own, outdated version.
View the HTML source and make sure the path to jQuery looks like this: wp-includes/js/jquery/jquery.js.
Using the_title() in the wrong places
A mistake I see in a lot of themes is code like this:
<a title="Permanent Link to <?php the_title(); ?>" href="<?php the_permalink() ?>"><?php the_title(); ?></a>
This causes all sorts of problems. You should use the_title_attribute() instead:
<a title="Permanent Link to <?php the_title_attribute(); ?>" href="<?php the_permalink() ?>"><?php the_title(); ?></a>
No id & class attributes for dynamic sidebars
If you want to have editable widgets, you’ll have to change code like this:
If you’ve been using the basic text editor, you’ve probably had your share of frustration with the autogrow script. After switching from Autogrow to Growfield without much improvement, I’ve decided to stick to a normal textarea with a scrollbar.
The rich editor is not affected by this.
I’ve added two buttons to the rich editor panel: font-family and font-color. More importantly, you can now select which buttons you want to use. Just paste this code in your theme’s functions.php:
Over the last several weeks, there has been a steady stream of improvements going into Front-end Editor, largely as a result of your feedback. I’m happy to see people are using the plugin in interesting ways.
First of, several users requested a way to allow only certain posts to be editable. This is easily done now, with a few lines of code. See examples here.
Secondly, there are two new editable fields: If you’re on a category archive and your theme uses single_cat_title(), you will be able to edit the category title on the spot. The same goes for tags.
added $echo parameter to editable_post_meta()
don’t load CSS or JS if the current user can’t edit any of the fields
switched from Autogrow to Growfield (fixes IE compatibility)
added Georgian translation (thanks to Levani Melikishvili)
Thanks to those who suggested improvements and did beta testing.
A new release with a lot of small but noticeable improvements:
Two new editable fields
In version 1.3, you can also edit your site’s title and description. You won’t go changing those very often, but it’s nice to know you can. :)
Skinable WYSIWYG editor
The rich text editor now respects image alignment. What’s more, you can make the editor window look however you want. Just add your own CSS into a file named front-end-editor.css and place it in your theme’s directory.
When you edit a post, the post’s slug will also be updated, when appropriate. For example, say you have a post titled “My Greatest Post Ever”.
If the slug is the default one - “my-greatest-post-ever” – and you change the title, the slug will also be updated.
But, if you had previously set the slug to “greatest-post”, it will remain unchanged when you edit the title.
The new feature in this release is the possibility of editing a single paragraph in a post, instead of the whole post. If you want to go back to the old behaviour, you can uncheck the new checkbox from the settings page.
Speaking of which, the settings page is now split into two dashboard-like boxes.
This version adds post meta editable fields. These are a little different from the others. To add a custom field editable meta, you have to add something like this inside The Loop in you WordPress theme:
This version makes it possible to also edit tags inline. However, due to a bug* in WordPress, it won’t work on most themes. If you want this feature you will have to make the following modification to your theme:
Replace the_tags() with echo get_the_tag_list().
Some fixes for the autogrow script have also been added. Props Jean-Paul Horn.
It’s now a lot easier to add new editable fields. I will be writing a post for developers on how to add new editable fields using this plugin.
I’ve submitted a ticket, so the bug will hopefully be fixed in WP 2.8.