Funroe Factory

13 Comments

1. Dan
   Posted January 21, 2008 at 12:58 pm | Permalink

   Hi,

   This looks like a great plugin, but when I installed it on my test server - once on a WP 2.2 site and once on a 2.3 site - I couldn’t get the toolbar in the editor window. Tried empty all user data, cache, etc, still nothing. Tried it in Firefox 2.0 and Opera 9.4 running a Mac (10.5).

   Hope it’s just me… but either way I can’t use it.

   All the best,
   Dan

2. Thomas
   Posted February 3, 2008 at 10:33 am | Permalink

   Love this plugin.
   I made a couple plugins for it too. NextGen Gallery etc.

   One thing I man missing is: When I deactivate the plugin it flushes the settings.

   So It would be great with at function, that stores all the settings and maybe and uninstall.

   For inspiration see lesters plugins (wp-email etc.)

3. jesse
   Posted February 28, 2008 at 8:28 am | Permalink

   This was an old post that I recycled for the release of WP Super Edit 1.5.

   Dan and Thomas should both try version 1.5. I have fixed the flush settings issue. Among other nasty things.

4. Jonathon
   Posted March 1, 2008 at 4:29 pm | Permalink

   Summary: My Internal Server Errors still exist, but they are not due to Super Edit.

   Thanks for notifying me that you had released Super Edit 1.5.

   I installed Super Edit 1.5 last Thursday, but I still get “500 Internal Server Error” on all the buttons I mentioned in wordpress.org/support/topic/143837, as well as the new HR button.

   I have Monsters Editor for WP Super Edit - deactivated.
   I removed Laurel’s FullScreen plugin since it is now included within Super Edit.

   Still, I get the Internal Server Errors.

   I de-activated WP Super Edit, but I still get the Internal Server Errors.
   I should have tried that before - I think I did not. So, my system’s problem and solution are not to be found within WP Super Edit.

   My analysis of my tiny_mce_config.php page is also in support topic 143837.

   Is there some way I can get the 500 page to provide more details than “Internal Server Error”?

   System info:
   PHP version 5.2.4
   MySQL version 4.1.22-standard
   Apache version 1.3.39 (Unix)
   Operating system Linux
   Architecture i686

   Is there someone else I should contact regarding TinyMCE?

   (Reminder of our conversation history:
   You found the source of my 404 errors for a call to bold/editor_plugin.js (due to a different plugin). (http://wordpress.org/support/topic/148036)
   You clarified how I can use editor.css (143837).)

5. Jonathon
   Posted March 2, 2008 at 12:09 am | Permalink

   Thanks for suggesting I check the Apache error log - that should have been obvious to me, but was outside my mental box, even though my box is complex.

   “Premature end of script headers” is the recurring error message (on html files like wp-includes/js/tinymce/themes/advanced/charmap.htm). I googled that error message but the solutions, even within moxiecode’s forum, seem to not apply here. (Details below.)

   In wp-plugins/superedit/
   all my folders have ‘755′ permissions,
   but all the files (in all the folders) have ‘644′ permissions. Is that okay?
   I don’t want ‘group’ or ‘global’ able to write to the files. I do want group able to do actions which read the files. Do php files need to be executable?

   Solutions suggested for “premature end of script headers” are:

   - check all tinymce files and folders are ‘755′ - confirmed.

   “make sure that your CGI script has the same user/group ownership as your cgi-bin folder.”
   I don’t think that applies to tinyMCE, or is that little bit of code in the html files cgi?

   Check if you have a /var/log/apache/suexec.log file; if so, and if it’s the problem, it’ll explain the reason why it’s denying your script from executing properly. One easy fix to try is adding a “-w” to the end of the first line of your Perl script, i.e. change the first line from “#!/usr/bin/perl” to “#!/usr/bin/perl -w”

   My site has /var/log/ but no /apache/suexec.log. Using PuTTY, I searched: grep -rl “SUexec” ../../* but got permission denied errors. I’ll ask my host.

   “The first line of a CGI script must contain the path to the Perl binary on the server”
   - not applicable, right?

   ‘Premature end of script headers’ is usually a permissions problem.

   ‘Transfer modes’ ascii or binary - not applicable since wp-includes were installed first by Fantastico and now by WP Automatic Upgrade.

   ‘Line Endings’ microsoft vs other - n/a since I didn’t edit these files.

   I have Firebug and Web Developer Toolbar and IE Developer Toolbar, but I can’t see any relevant information in any of those.

   Thanks Jess,
   Jonathon

6. Jonathon
   Posted March 2, 2008 at 1:16 am | Permalink

   SOLVED

   In my htaccess file I had:

   AddType application/x-httpd-php .htm .html

   so the tinyMCE html files were being processes as PHP.

   A year ago, as I was trying to integrate my original static html site into my new dynamic php site, I read that I should insert that line into my htaccess file. The reasoning seemed cloudy to me, but I knew nothing then, and the author sounded confident. Anyway, that was the problem.

   Thanks.

7. Jess Planck
   Posted March 2, 2008 at 12:25 pm | Permalink

   Jonathon, glad to see you found your problem. I’ve done similar things for various reasons then spent months trying to fix it. I always hate it when it’s one dinky line in an obscure file.

8. Thomas
   Posted March 5, 2008 at 4:33 am | Permalink

   Thank you for the update, didn’t see before now. (saw it through the WP-plugin notice).

   I’ve made an superedit plugin for the NextGen Gallery button, if you are interested.

   I really appreciate your work on this.

9. dan
   Posted March 8, 2008 at 4:41 am | Permalink

   I am trying to adapt the RB Internal Links plugin for WP Super Edit.

   What is going on with the two js: editor_plugin.js and editor_plugin_src.js?

   Thanks.

10. Jess Planck
    Posted March 8, 2008 at 8:26 am | Permalink

    editor_plugin.js is the main JS used by TinyMCE for that plugin. The reason for two files is because typically editor_plugin.js is compressed or “minified” making it hard to read. The editor_plugin_src.js should be the readable source code. You would have to digging on the Moxiecode TinyMCE Website to find their javascript compression tools.

    Although compression is nice for end users, I typically copy editor_plugin_src.js to editor_plugin.js for easier testing and development.

11. starkhay
    Posted March 11, 2008 at 2:55 am | Permalink

    I prefer waiting for wp super edit 2.0 since wordpress 2.5 ‘ll be launched very sooner.
    thanks for your work in the adaptation of super edit, a great plugin.

12. Jess Planck
    Posted March 15, 2008 at 11:37 am | Permalink

    Boy dem’ some huuge gravatars! have to play with that later.

    I know I won’t meet the release of WordPress 2.5 with WP Super Edit 2.0. I will post some sort of progress as I get closer to release.

    Currently it’s a major reworking. I’m moving things to separate database tables and classes. The end idea is have better control and hopefully some user and perhaps even role based settings.

    I’m keeping the original ideas (might make things faster and more flexible.) I don’t think it’s going to be feasible to support older WordPress versions though. Big differences in TinyMCE versions would really bloat this plugin further than it already is.

    It’s not functional, but source is always available from the subversion trunk at svn.wp-plugins.org only for the curious. The notes.txt is my scribble pad.

13. Bisnero
    Posted April 7, 2008 at 8:47 pm | Permalink

    Hi, it’s off contextual theme!

    What is the name of plugin for donations? Thanks!