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.

If you’re a JavaScript ninja, you can go even further and tweak it’s behaviour using event triggers baked into the new version. See /inc/editor/editor.js.

Slug updating

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.

Other improvements

  • option to disable highlighting
  • compatibility with the postThumbs plugin
  • added Polish translation
  • better XHTML markup

Comments (22)

  • Hi Scribu,

    I’m seeing massive problems with your latest update 1.3 :-(

    1. It looks like there’s a double insertion of wp_head, as my whole (head) section is completely duplicated. Also: the (title)(/title) html tags are completely gone when I view the page’s source code.
    2. The field options won’t stick. I only want the arcticle’s content to be edited, so I deselect all, check the corresponding checkbox and click Save Changes. If I later return to Front End Editors’ plugin options page, all checkboxes are checked again (and all fields are editable on the front side, which I explicitly don’t want)

    I have uninstalled and reinstalled the plugin several times and even deleted the corresponding options from the wp_options table with CleanOptions, but I keep on seeing this behaviour.

    Your help would be much appreciated. I’ve deinstalled the plugin for now :-(

    • scribu says:

      1. Could you provide your header.php file or at least the HTML markup before and after the plugin is activated? My email is scribu@gmail.com

      2. I was able to reproduce this problem. Should have a fix soon. Fixed in 1.3.1.

  • gio says:

    url slug is working now..:)

    but..when i click on the post title its still using the old url which obviously doesnt not exist anymore. that means i still have to refresh the page.

  • Tobias says:

    Hi! I love your plugin & enjoyed using it.

    However, for security reasons, I had to switch on SSL for the Admin-area by adding

    define(‘FORCE_SSL_ADMIN’, true);

    to the wp-config.php file. Since then, the Front-End Editor is unable to load. It just displays the throbber-icon, waiting to load the WYSIWYG-Editor, but it never shows.

    Is this fixable?

  • Marcel says:

    In my opinion the front-end editor plugin is one the best plugins I have seen this year!

    I have two feature requests: I would like to add new posts with the front-end editor and to edit the post categories. Can/will you make this?

    • scribu says:

      You can already add posts from the front-end with the PostHaste plugin.

      As for editing categories, two reasons why it wasn’t added until now:

      - it would be really slow if you have a lot of categories
      - the interface takes up quite alot of screen space

      That being said, I’m not against adding these features in the future.

  • Zool says:

    Greetings!

    I can’t turn on the (1.3 ver) plugin. WP 2.8.4 HU says:

    Fatal error: Class 'scbOptions' not found in /var/www/.../---/domain/wp-content/plugins/front-end-editor/front-end-editor.php on line 46

    Can anyone help me, whats this problem?
    Thanks!

  • Sean Ham says:

    The plugin duplicates the call to wp header, causeing css and js to load twice.

  • Luke Schafli says:

    I have installed and activated the plug-in. When I scroll over portions of my blog that can be edited with this plug-in, the text is highlighted as it should be. However, when I double click to make a change, nothing happens. Help?

  • Tyson Cecka says:

    Nice on the option for turning off highlighting but it’s still displaying the [empty] text when there are no tags / making it hard to test if a post has no tags due to wrapping the empty response.

  • ashaman says:

    Hi there. I have encountered a small problem with this plugin, even with the most recent update.
    I have a simple text and html widget on my sidebar,
    and I cannot force a line break using tags.
    Every time the page refreshes, the tags are deleted automatically.

    Any help?

  • t.w says:

    Front-end Editor works great in general but it does not go well with another plugin called wp-postviews (http://lesterchan.net/portfolio/programming/php/#wp-postviews)

    When I logged in, the widget post list would appear like “Family DVD authoring in three steps ” but when I log out of the blog, the display is normal.

    How to fix this?

  • t.w says:

    I have to use code format:

    How to add favicon for CMS Made Simple