Well… it does not work on my blog with IE8 and FF (double click gives nothing) (and it continues to break the Lightbox effect). I will work on a french translation.
Excelent Excelent Excelent Excelent I LIKE IT!!!
initially after update I found a PHP warning
Warning: Option not defined: rich in /wp-content/plugins/front-end-editor/inc/scb/Forms.php on line 172
I check Enable the WYSIWYG editor and save and the warning disappeared, but apparently does not work… when I double click nothing happens
I use firefox and Version 0.7.X work fine
thanks for your work!!
I got this warning :
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /wp-content/plugins/front-end-editor/front-end-editor.php on line 28
I too got PHP errors after the update to 0.8 (in admin dashboard) and white pages for the blog.
Warning: Missing argument 2 for scbOptions::__construct(), called in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 168 and defined in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 8
Warning: Missing argument 3 for scbOptions::__construct(), called in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 168 and defined in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 8
Fatal error: Class 'settingsFEE' not found in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 175
I normally don’t use the Update option in the Plugin screen, but just overwrite newer version from my ftp client. Could you please take this account as well, as it looks like there’s a problem with resetting the options.
I got 0.8.0.1 to work with some DB magic , but still have Save problems in Safari 4/Mac I reported this previously for 0.7. This is without the visual editor (which we will not use anyway, we’re code editor people)
Well, there’s no point in it now, because I’ve included it in the latest version, but it doesn’t seem to work. I’ll try another patch and mail that to you.
BTW, isn’t Safari 4 still in beta? (Have you tried it in Safari 3?)
Yeah, Safari 4 is still in beta, but this happens to be the browser of choice for most of our editors (which is not suprising, since it’s a iPhone/Mac website) and Safari 4 is so much faster for all things Javascript. I haven’t checked in Safari 3, as the upgrade to Safari 4 is irreversible
Was this comment meant for me or for Li-An? If it was addressed to me, I haven’t received the patch and it’s not in my spam folder Otherwise just ignore this reply (or feel free to delete)
The 0.8.0.1 version does not work with IE8 (but works with FF): the edit field seems to be launched but doesn’t show (and no compatibility with Lightbox effect but you must know that
I test the lightbox 2 and lightbox plus plugins based in scriptaculous (or something like that )
and not work with Front-End Editor
but installed the WP Jquery Lightbox Plugin and work fine together with F-EE
This is probably one of the greatest plugins ever made!!! I can’t believe you incorporated the jWYSIWYG editor into the inpage editor… truly groundbreaking!!! I am however seeing the error issues in IE that you’d fixed on the last release. Hopefully the next release will fix this and bring this plugin to the forefront of WP plugins.
Well, when I first installed the plugin (I think it was v6), it worked in FF but not IE… IE gave some random page errors (bottom of browser) which are always ambiguous and never give enough info to diagnose. The symptom was when you double clicked on content, it wouldn’t jump to the front-end editor box like it’s supposed to… you seemed to fix it in v7 but now the same issue is back in v8. If you fix it in the next release, expect a donation from this kid because I’ve been looking for a plugin with that type of functionality for my clients for years!
I’ll also note that in v6, it seemed to mess up the tags in my menu li’s which you seemed to fix in v7 but came back in v8. I wish I could offer a better diagnosis to help you out with it but my php/css knowledge is moderate at best.
I’m running PHP version 5.2.9 and i’m getting this error:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /wp-content/plugins/front-end-editor/front-end-editor.php on line 28
you say the reason is that people are running PHP 4, but in my case I’m not running PHP4 – I’m on 5.2.9.
Are you sure you are running PHP5?
I mean, how can the same code, running on the same version of PHP produce a parser error in some casses and not in others?
Yes, I’m quite positive I’m running PHP5.2.9 – I logged into my host and verified this before commenting. that’s how I know the EXACT version I’m running. Is there a link to version 7 so that I can grab that back (version 7 worked with no issues).
Thank you for correction Lightbox problem… but still IE8 problem (all the content disepeared when double clicking).
French users can find last translation files here http://www.li-an.fr/blog/?page_id=2957
It was without the WYSIWYG editor Same think with titles.
(nothing to do with it but the name of the fields in the option page are not translatable with the po file)
Can you try embedding the tinyMCE http://tinymce.moxiecode.com/ editor used inside the admin? Also if you could hook the actual one used in inside, it would have all the added stuff from other plugins
This plugin is amazing. I adore it! However, I just installed it on a couple of blogs running Contact Form 7, and the contact forms can no longer be submitted. JavaScript conflict, perhaps?
When clicking on the “send message” button, nothing happens. There should be a little Ajax animation “sending your message” then a message “your message has been sent successfully” but they do not show. And the message is not sent
This 0.8.3 version seems to work perfectly Good job !
(if you have some time, there is the little little problem of translation in the option page for the name of the fields but it’s not very important )
the warning disappeared from the plugin admin page but the plugin still not working, double-clicking on any field does not edit it. I guess a plugin conflict!
It kind of works now. The content won’t work after the first click of the Save button, but it will save if I click the Save button again. Previously it wouldn’t even let me save. I’m fine for now, but if you could investigate further I’d be happy to test.
P.S. Most email clients will automagically block file attachments with extension .js. Better zip it up next time (if you haven’t done that, than please ignore)
A conflict with http://www.4mj.it/slimbox-wordpress-plugin/ (the lightbox effect begin to load and stops showing the image without effect).
I’ll look into it.
Well… it does not work on my blog with IE8 and FF (double click gives nothing)
(and it continues to break the Lightbox effect). I will work on a french translation. 
I’ve found the problem and will be releasing an update soon.
As for the Lightbox effect, I wasn’t able to look at it before version 0.8, but I will.
Excelent Excelent Excelent Excelent I LIKE IT!!!
initially after update I found a PHP warning
Warning: Option not defined: rich in /wp-content/plugins/front-end-editor/inc/scb/Forms.php on line 172
I check Enable the WYSIWYG editor and save and the warning disappeared, but apparently does not work… when I double click nothing happens
I use firefox and Version 0.7.X work fine
thanks for your work!!
The PHP warning is a more complicated issue which will hopefully be fixed in 0.8.1.
I’m working in spanish translation
Nice.
I got this warning :
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /wp-content/plugins/front-end-editor/front-end-editor.php on line 28
Your host is running PHP4. Sorry.
I forgot before installing, I’ll do it again…Thanks !
I too got PHP errors after the update to 0.8 (in admin dashboard) and white pages for the blog.
Warning: Missing argument 2 for scbOptions::__construct(), called in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 168 and defined in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 8
Warning: Missing argument 3 for scbOptions::__construct(), called in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 168 and defined in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/inc/scb/Options.php on line 8
Fatal error: Class 'settingsFEE' not found in /var/www/vhosts/**********/httpdocs/wp-content/plugins/front-end-editor/main.php on line 175
I normally don’t use the Update option in the Plugin screen, but just overwrite newer version from my ftp client. Could you please take this account as well, as it looks like there’s a problem with resetting the options.
Yes, I know there’s a problem with resetting the options. As for the other errors, are you running any other plugins of mine?
No to that (sorry
)
Then it means there was some problem with the Automatic Update feature in WP. (It works fine for me).
I got 0.8.0.1 to work with some DB magic
, but still have Save problems in Safari 4/Mac 
I reported this previously for 0.7. This is without the visual editor (which we will not use anyway, we’re code editor people)
A few days ago I sent you an email with a potential fix. Did you get it?
No sorry
I got your ‘Thank you’ note though today. Could you please resend it?
Well, there’s no point in it now, because I’ve included it in the latest version, but it doesn’t seem to work. I’ll try another patch and mail that to you.
BTW, isn’t Safari 4 still in beta? (Have you tried it in Safari 3?)
Yeah, Safari 4 is still in beta, but this happens to be the browser of choice for most of our editors (which is not suprising, since it’s a iPhone/Mac website) and Safari 4 is so much faster for all things Javascript. I haven’t checked in Safari 3, as the upgrade to Safari 4 is irreversible
I’ve sent you an email with a patch.
Was this comment meant for me or for Li-An? If it was addressed to me, I haven’t received the patch and it’s not in my spam folder
Otherwise just ignore this reply (or feel free to delete)
It was for you. Nevermind. Just replace /inc/js/editor.js with this file. (Don’t forget to clear your browser cache).
PS: This also contains a slimbox patch.
I’m installd the fixed files 0.8.0.1 and work well
the visual editor rocks!!
Danish localization as well as some suggestions are sent to you by mail.
Others may get the Danish files here: Ret småfejl m.m. direkte i artikler
The 0.8.0.1 version does not work with IE8 (but works with FF): the edit field seems to be launched but doesn’t show (and no compatibility with Lightbox effect but you must know that
Which field do you mean: rich, textarea, input, all?
Ironically, they all work well in IE6.
spanish lang it’s in your e-mail
I test the lightbox 2 and lightbox plus plugins based in scriptaculous (or something like that
)
and not work with Front-End Editor
but installed the WP Jquery Lightbox Plugin and work fine together with F-EE
Got the translation.
I’ll look into those other plugins as well. Thanks for testing.
This is probably one of the greatest plugins ever made!!! I can’t believe you incorporated the jWYSIWYG editor into the inpage editor… truly groundbreaking!!! I am however seeing the error issues in IE that you’d fixed on the last release. Hopefully the next release will fix this and bring this plugin to the forefront of WP plugins.
Amazing work!!!!
I’m glad you like it.
Which issues exactly? The only one I can remember is with the textarea that had no height.
Well, when I first installed the plugin (I think it was v6), it worked in FF but not IE… IE gave some random page errors (bottom of browser) which are always ambiguous and never give enough info to diagnose. The symptom was when you double clicked on content, it wouldn’t jump to the front-end editor box like it’s supposed to… you seemed to fix it in v7 but now the same issue is back in v8. If you fix it in the next release, expect a donation from this kid because I’ve been looking for a plugin with that type of functionality for my clients for years!
I’ll also note that in v6, it seemed to mess up the tags in my menu li’s which you seemed to fix in v7 but came back in v8. I wish I could offer a better diagnosis to help you out with it but my php/css knowledge is moderate at best.
What version of IE are you using?
Could you enable debugging and post the error message here?
8.2 solved the IE issue. All is beautiful. Excellent work!!
I’m running PHP version 5.2.9 and i’m getting this error:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /wp-content/plugins/front-end-editor/front-end-editor.php on line 28
you say the reason is that people are running PHP 4, but in my case I’m not running PHP4 – I’m on 5.2.9.
So how can this issue be resolved?
Are you sure you are running PHP5?
I mean, how can the same code, running on the same version of PHP produce a parser error in some casses and not in others?
Yes, I’m quite positive I’m running PHP5.2.9 – I logged into my host and verified this before commenting. that’s how I know the EXACT version I’m running. Is there a link to version 7 so that I can grab that back (version 7 worked with no issues).
Yes, see Other versions.
Thank you for correction Lightbox problem… but still IE8 problem (all the content disepeared when double clicking).
French users can find last translation files here http://www.li-an.fr/blog/?page_id=2957
Ok, screenshot? Error message?
http://img269.imagevenue.com/img.php?image=71394_ie8-frontpage_122_492lo.jpg
No message error. You can see here the “before” and “after” clicking (the content of the post just vanishes).
Did you try without the WYSIWYG editor? Does this happen for post titles too?
It was without the WYSIWYG editor
Same think with titles.
(nothing to do with it but the name of the fields in the option page are not translatable with the po file)
Can you try embedding the tinyMCE http://tinymce.moxiecode.com/ editor used inside the admin? Also if you could hook the actual one used in inside, it would have all the added stuff from other plugins
Really cool anyways! Cheers!
This plugin is amazing. I adore it! However, I just installed it on a couple of blogs running Contact Form 7, and the contact forms can no longer be submitted. JavaScript conflict, perhaps?
Same problem with Contact Form 7. It must be very hard to work on such a plugin with so much interactions…
Tell me about it.
(I didn’t attempt to fix this issue yet)
When clicking on the “send message” button, nothing happens. There should be a little Ajax animation “sending your message” then a message “your message has been sent successfully” but they do not show. And the message is not sent
This 0.8.3 version seems to work perfectly
Good job !
)
(if you have some time, there is the little little problem of translation in the option page for the name of the fields but it’s not very important
The new version works beautifully with the contact form. Thank you so much!
You’re welcome.
no more autogrow for me with 0.8.3 version.
Running on FF3, no other plugin activated, on a local windows server.
neither wysiwig. Only a single-line textaera.
Should be fixed in 0.8.4.
plugin is not working, i’m having the waring on the plugin admin page:
Warning: Option not defined: rich in /home2/kitabnl/public_html/wp-content/plugins/front-end-editor/inc/scb/Forms.php on line 172
any idea?
Are you using the latest version of the plugin? (it will dissapear if you check the checkbox and click “save changes”.
many thanks for the quick reply.
the warning disappeared from the plugin admin page but the plugin still not working, double-clicking on any field does not edit it. I guess a plugin conflict!
Well, if you’re using Firefox, click Ctrl + Shift + J and see if you get any JS errors. If not, please tell me what other plugins you’re using.
here is the error from firefox:
Error: $(this).attr(“rel”) is undefined
Source File: http://www.kitab.nl/wp-content/plugins/front-end-editor/inc/js/editor.js?ver=0.8.4
Line: 146
I sent you an email with a potential fix.
It kind of works now. The content won’t work after the first click of the Save button, but it will save if I click the Save button again. Previously it wouldn’t even let me save. I’m fine for now, but if you could investigate further I’d be happy to test.
P.S. Most email clients will automagically block file attachments with extension .js. Better zip it up next time (if you haven’t done that, than please ignore)
Ok, thanks for the feedback and the mail tip.