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:

<?php editable_post_meta($post->ID, 'my_key', 'textarea'); ?>

The first argument is the current post id, the second is the custom field key and the third is the type of field you want (input, textarea or rich).

Comments (71)

  • Steffen says:

    Thanks for adding support for meta fields. Love your plugin.

  • kzh says:

    Thanks for Great plugin! I like it.
    I Make Japanese translation file.
    Please use this.
    http://dl.getdropbox.com/u/211844/front-end-editor-ja.zip

  • Dominique says:

    Hello, just installed the plugin, it’s fantastic :)

    Only a little problem, I use accents in my text (french).. and the accented caracters show up weird, maybe some charset or utf8 problem.. don’t know exactly.. I tried with firefox and IE, same thing.
    Here is a screenshot :
    http://www.domsweb.org/test-front-end.gif

  • Dominique says:

    I’ve tried with the wysiwyg editor deactivated, same problem.. and then I tried to edit a title and write “testé” but it gives out “testé”… :(

    • scribu says:

      I’ve sent you an email with a potential fix.

    • Mael says:

      french info :
      si tu le peux, modifie l’encodage des fichiers de ton thème en utf8 sans BOM, et change la déclaration dans le header si il y en a une (du type iso western latin ou autre, remplace par utf8).

  • Gerrit Jahn says:

    I see the latest bugfix took care of an issue with the Blackcurrent theme, but not completely:
    When editing a post, the post content (in WYSIWYG) goes below the bottom of the sidebar.
    This used to be the case also with editing the post subject, but the latest version 0.9.2 did seem to fix that for some reason. Email me if you want a screenshot to demonstrate what I am referring to. I tried to find this bug but I am not sure where the HTML stuff is hidden ;-)

  • Gerrit Jahn says:

    That is what I thought, it was a CSS issue. I added that bit you gave me to layout.css of the theme and that fixed it :-)

  • Esteban says:

    since version 0.9 it’s not working for me with or without visual editor, I’m double click in posts or titles and nothing happens… and I not found the 0.8.4 version :(

    • scribu says:

      It doesn’t work in any browser? Any errors?

      In Firefox, press Ctrl + Shift + J

      PS: You can download version 0.8.4 from here.

      • Esteban says:

        Sorry, I have many plugins installed… may be a conflict with another plugin. :-$
        I test this in another blog with similar theme and work fine.
        seeking plugin in conflict…

      • Esteban says:

        the conflict is the Multi-level Navigation Plugin

        is rare because they worked well together, but now multilevel has an error…

        I prefer this plugin then I look for another way to make the menu ;)

        • scribu says:

          You could try disabling the Post/page title editable field, since I think that’s what’s causing the problem.

  • Esteban says:

    no no, this plugin it’s all right. :)
    I change the place of the wp_head() call in header.php and now all is working, (may be many calls to jquery.js)

    sorry for “my” english… xD

  • Esteban says:

    If can I request a feature… ;)
    Edit with double click an excerpt and if the post haven’t one, add a new excerpt like excerpt field in the admin’s post edit.
    Does that mean what I say?

    OffTopic: the button “Reply” (here below) it’s an external plug-in?

  • Esteban says:

    awesome!
    thank you very much :D

  • Li-An says:

    The excerpt editing does not work on IE 8 :-) (sorry to give bad news)

    • scribu says:

      Try this: In /inc/editor.css

      replace

      .front-editor-container {display: inline !important}

      with

      .front-editor-container {display: block !important}

      and then refresh the browser cache.

  • Li-An says:

    When desactiving the excerpt plugin, the editor field shows up but no text in it. Maybe you could ask somebody else to make some test to see if it’s not a compatibility problem on my configuration.

  • Esteban says:

    Excellent, very useful. :)
    Some remarks on the edition of excerpts.

    -If empty manual excerpt then load initially default post excerpt.
    -No visual editor, delayed loading and it’s not useful for excerpts ;)

    you’ll see if posible :roll:
    thank you for your work!!

  • lolfang says:

    I’m getting extra breaking spaces after I edit a post.

    What info do you need for debugging this?

    I’m using Fervens A theme. See this post, I left it just like after editing with FEE: http://another.intheuniverse.com.ar/2009/04/n-warp-daisakusen-new-snes-game/

    • scribu says:

      Firstly, what version of WordPress and what browser?

      Were you using the WYSIWYG editor or not?

      Did you copy-paste it from Word or another program?

      Did you edit it from Windows and then from Linux or something like that?

      • lolfang says:

        >> Firstly, what version of WordPress and what browser?
        WordPress 2.7.1, Opera Browser 9.64.

        >> Were you using the WYSIWYG editor or not?
        Yes. Both in the plugin and in WordPress.

        >> Did you copy-paste it from Word or another program?
        Nope, I just edited the post with the double click functionality.

        >> Did you edit it from Windows and then from Linux or something like that?
        I don’t have Linux. Windows XP Pro w/SP3.

        • scribu says:

          Ok, thanks for answering all the questions. It definetly has to do something with WordPress’s wpautop() function.

          Try editing the post again and removing the spaces, as that seemed to fix the issue when I tested it.

  • Esteban says:

    I am very grateful with fe-e :D
    Yesterday donate you a few dollars from the paypal account of my wife.
    I recommend that everyone follow this example ;)

    enjoy

  • Eric says:

    I installed the upgrade today and now the editor gives me an error and says it can’t be activated –

    Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /hermes/web05/b2199/gargiulo/camelclutchblog.com/blog/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 4

    I tried to delete and re-install and it still gave me errors. Could you please help?

    • scribu says:

      You probably updated from version 0.7 or older. The later versions require PHP5. You can download older versions by going to Overview -> Other versions.

  • Georg says:

    I run the Excerpt Editor plugin. It allows me to display, e.g., images in the excerpts. When I add an img src-tag, Front-end Editor 0.9.4 removes it, at least sometimes. Running WP 2.7.1 and FF3.0.8.

    • scribu says:

      When exactly does it remove them:

      - when double-clicking?
      - after editing with FEE?
      - for posts that have manual excerpts?

  • Georg says:

    All my posts have manual excerpt or no excerpts.

    When I tried to repeat it in order to answer your questions, I was unable to repeat it. Excerpt Editor sets WP to display the most recent post in full and all other at the front page with excerpt.

    When I double-click on the excerpt – it makes no difference whether I double-click on the text or the image – FEE opens the editor with the main content or entry. My guess is that EE has intercepted the normal display of post contents and replaced it with the excerpts for all posts except the first. So, to FEE, this looks like a normal post. It therefore display the post content, which is not the excerpt.

    OK, I am just guessing …

    If you want more detailed feedback, I will take at look at it, perhaps not before in the beginning of the next week, I am afraid.

    • scribu says:

      Thanks for the feedback. I will test Excerpt Editor myself and see if I can remedy this behaviour, but no promises.

  • Georg says:

    Hi, it’s me again!

    I activated FEE on my WordPress portal in order to test it and did not deactivate it again. I noticed that Shutter Reloaded is intercepted by FEE. SR loads and loads the picture, but then aborts so that the picture is shown separately on an empty page.

    Just to let you know!

  • lolfang says:

    I don’t want to be a hassle, but this plugins has lots of non-standard tags. This makes any site XHTML invalid after editing.

    Check with w3 validator: http://validator.w3.org/

    • scribu says:

      First of all, the validator doesn’t see any output from this plugin, nor do regular visitors.

      Second, they are all valid: span, button, div, input.

  • Bryan says:

    Can you add the ability to edit text widgets?

  • Mael says:

    Hello,
    Do you still plan to insert an option for making only paragraph editable instead of all the content ?

  • Bryan says:

    This plugin seems to conflict with lightbox. Is there anyway around that?

    • scribu says:

      The latest version should work with Lightbox. Which Lightbox plugin are you using exactly and what version of FEE?

  • Dains says:

    Hi, great plugin! I’d asked someone else about doing this before and the answer was that it would be too difficult. I’m glad you made this happen!

    I’ve one problem with it though. I’m using an AJAX popup on my page/post links in the sidebar to show a preview of the content. FEE disables the AJAX functionality when it adds its code to the links in the sidebar(via titles, I think). If I disable the titles option in the FE control panel, the problem goes away, but of course I can’t edit the title in the content area now :)
    The sidebar is using wp_page_menu, and I downloaded the latest version of FEE today (.9 I think, no version info in the readme.txt). Is there any way to differentiate the title of the content from the title of the links in the sidebar for FEE?

    • scribu says:

      I’m glad you like it. :)

      I know several other people are having trouble with the editable titles.

      I might be able to fix the problem you’re having, but I’m not making any promises. Stay tuned.

      • Dains says:

        Thanks Scrib!

        • scribu says:

          About the sidebar links, why would you need to not make them editable? Are they not displayed correctly?

          • Dains says:

            Well, the span and class that FEE puts in is messing up the AJAX previews on the navigation links. Clicking a link brings you to the content page where it’s intuitive to edit the title anyways.

  • Li-An says:

    I just discover I cannot edit the comments fields with the 0.9.5 version (in IE8 and FF). Am I the only one ?

  • Dains says:

    Another question, is there any way to use another editor, such as the default Wordpress one, with FEE? I was actually looking to upgrade the Wordpress editor, and now that I’m thinking of using FEE site-wide, I’d like to know if it’s possible to use the site editor instead of the FEE one.

    • scribu says:

      I’m afraid that’s not an option because it would take too long to load, especially if there’ll be an option to edit a single paragraph.

      • Dains says:

        Hmm, sorry to hear that. I’d assumed the code was preloaded by Wordpress as the jquery library is in the header. It would be absolutely awesome to have a full editor there so that I don’t have to retain edit links to use the Wordpress one for pretty posts.
        Thanks for your reply!

  • Gerard says:

    Hello. Great plugin! :-)
    But i don’t get the wysiwyg editor to work in the wordpress mandigo theme (1.40.1).
    Normal editing works well but choosing the wys only shows the tags around the text. After activating the normal wordpress theme the wys editor works well.
    I want to use Mandigo because it is very easy to cutomize.
    Can you help?
    Greetings from the netherlands…

  • Syl says:

    I got an error when I’m trying to activate it… Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/journees/public_html/devlpjs/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 4

  • Syl says:

    Forgetten to specify, Wordpress 2.7.1, PHP 4.4.8, MySQL 4.1.22-standard, Appache 1.3.41 (unix)

  • Gerald says:

    Hi,

    Can’t edit titles and I don’t get wysiwig editor – but this plugin is great. Thank you Scribu.

  • Gerald says:

    For the non-editable titles, the problem is probably due to SEO title tags I use on this site…