Comments on: WP Super Edit 2.3

By: @Metacowboy

@Metacowboy — Fri, 01 Apr 2011 08:57:37 +0000

Finally a great plugin but still the custom classes don’t work on Safrai everything fine on firefox but on Safari the styles from editor.css dotn show up instead the default wordpress styles. Any work around would be grateful .

( also use in your forum, to hide the 6 default wp classes in function.php.)

By: Mathew

Mathew — Mon, 24 Jan 2011 22:28:36 +0000

I just installed WP Super Edit for the first time and love it! I’m using WP MU and have set up two profiles for Super Edit (Admin & Editor). They seemed to be working great!

I have one question however. How can I get my Super Admin to see the Editor? When I am in a site using my super admin profile, I see no editor options.

Am I doing something wrong?

By: knn

knn — Fri, 24 Dec 2010 21:23:55 +0000

*BUG*

It seems that SuperEdit inserted hardcoded style definitions when I switched to html view:

I had to delete these nonsense definitions manually.

style=”background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #d2dfef; outline-style: solid; outline-width: 1px; outline-color: #447aa4; padding-left: 2px; padding-right: 2px; background-position: initial initial; background-repeat: initial initial;”

By: knn

knn — Thu, 16 Dec 2010 04:27:59 +0000

As a suggestion: I would like to have self-defined styles as a button (and not only in the drop down menu). Would that be possible?

By: jess

jess — Wed, 15 Dec 2010 19:31:18 +0000

Not surprised. I haven't done much Chrome testing yet. Chrome is about to be a browser supported where I work at www.nicholls.edu, so I'll be working with Chrome more this spring. Hopefully those issues will be fixed in WordPress 3.1 since it has an updated TinyMCE editor. WP Super Edit only turns on some things to show that CSS drop-down, it doesn't actually create it. I will be doing some updates for WordPress 3.1 to make sure I'm using stuff compatible with the updated TinyMCE editor.

By: knn

knn — Wed, 15 Dec 2010 09:25:36 +0000

Google Chrome doesn’t like this plugin:

The self-defined styles disappear in the styles dropdown menu after you edit a post and press update.

By: jess

jess — Tue, 14 Dec 2010 22:02:31 +0000

Completely missed that bad define()! WP Super Edit 2.3.4 should fix it. Thanks for letting me know!

By: Jeremy Clarke

Jeremy Clarke — Fri, 10 Dec 2010 19:35:22 +0000

Hey man, thanks for your work and sorry about the hard year you’ve been having, here’s hoping 2011 goes smoother

I’m here with more work for you unfortunately. My request is that, whenever you get back to the plugin, you enable WP_DEBUG on your dev environment and clean up some of the errors that come up when your plugin is running.

WP_DEBUG is not the most popular feature in WP but it is a very useful and important one that many plugin and core developers use when developing because it activates the display of many errors that help you write safer and cleaner PHP.

http://codex.wordpress.org/Editing_wp-config.php#Debug

With super-edit enabled there is one notice that shows on every single pageview, related to this line:

define( WPSE_VERSION, ’2.3.1′ );

All you need to do for that one is add single-quotes around the constant name:

define( ‘WPSE_VERSION’, ’2.3.1′ );

When I’m in wp-admin there are a lot more notices. Usually the fixes are really quick for these problems, and they tend to involve things that you should be doing anyway (declaring variables, not using deprecated functions/arguments etc.).

Thanks for considering it!