Comments on: WP Super Edit 1.5

By: Nick

Nick — Fri, 15 Aug 2008 21:59:14 +0000

i’m trying to set up WP again on a new server and therefore trying to install your plugin.
However when I go to organize buttons
1. none of the plugins feature in the “unused buttons” box &
2. there is a whole lot of javascript under the layout box

I’m in WP 2.5 - may update to 2.6.1
server has PHP 5.2
Mysql 5.0.45 (don’t know if this is important.

Could there be clashes with other plugins ?

I’m looking for a solution because I like the damn thing !!

By: Bisnero

Bisnero — Tue, 08 Apr 2008 01:47:04 +0000

Hi, it’s off contextual theme!

What is the name of plugin for donations? Thanks!

By: Jess Planck

Jess Planck — Sat, 15 Mar 2008 16:37:54 +0000

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.

By: starkhay

starkhay — Tue, 11 Mar 2008 07:55:25 +0000

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.

By: Jess Planck

Jess Planck — Sat, 08 Mar 2008 13:26:22 +0000

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.

By: dan

dan — Sat, 08 Mar 2008 09:41:00 +0000

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.

By: Thomas

Thomas — Wed, 05 Mar 2008 09:33:59 +0000

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.

By: Jess Planck

Jess Planck — Sun, 02 Mar 2008 17:25:16 +0000

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.

By: Jonathon

Jonathon — Sun, 02 Mar 2008 06:16:31 +0000

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.

By: Jonathon

Jonathon — Sun, 02 Mar 2008 05:09:45 +0000

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