WP Super Edit 2.3

I am ashamed to officially announce the immediate availability of the WP Super Edit 2.3 WordPress plugin! It’s about as ugly as it’s ever been with less mole-hairs!

I’ve been so busy that I’ve only been able to take occasional stabs at fixing problems and adding support for WordPress 3.x. As a visitor and user, I beg you to remember that I work for a terribly underfunded university in swamp people country. When I’m not doing that, I’m taking on small projects I can handle to pay those bills. I should also mention the lovely year we’ve had with pets dying, automobile accidents, surgeries, and other random calamities (I won’t say the H-word, but that damn Gustav passed over my house while Jim Cantore was staying two blocks away in 2008). It’s not all bad, just busy. The Saints did go to the Superbowl.

So, What’s the Good News?

A lot of part-time half-a$$ work brings WP Super Edit to version 2.3.

  • Fixed stupid install issues, so the plugin should work on those systems with problems.
  • Removed callback system and moved some external TinyMCE plugins into separate WordPress plugins. This might increase some performance.
  • Multi-site (beta©) support. If you complained about WP Super Edit creating tables in your database, well you can keep on whining for now because WordPress doesn’t yet have a robust method for storing complex Mult-site data yet.  Hey at least it isn’t gonna make three new tables for each sub-site, so smile!

And the Bad News?

So far I haven’t hit a major issue on the websites that are using this new version. If you find a fixable problem or feature and have a solution do not hesitate to contact me. Their may be some problems that could force some users to uninstall and reinstall the database tables. I also haven’t fixed the issues caused when a website is moved, that also requires reinstall of WP Super Edit database tables.

If you have problems you can always press that “Uninstall WP Super Edit Database Tables” button under the WP Super Edit Options tab. It will destroy any custom settings you’ve made, but it will clear out any issues that might have crept into the database over time. Performing the reinstall may be required for WordPress sites that have gone through a couple of versions of WP Super Edit.

Lagniappe!

If you’re brave or close to my level of stupidity, take a gander at the WP Super Emotions plugin and the tinymce_plugins/superemotions TinyMCE plugin. I’ve been using that as I learn more about WordPress and TinyMCE. It uses WordPress shortcodes and flips between the emoticon images and shortcodes in the editor. It also uses the currently messy activation and deactivation functions for adding buttons and plugins to WP Super Edit. That means that you should be able to build external WordPress TinyMCE plugins or buttons and add them to WP Super Edit. In the future I’d like to build an interface to edit the WP Super Edit database tables directly, but for now this is all I’ve got.

As always, leave a comment here (or on WordPress.org for issues with this version and have fun!

8 thoughts on “WP Super Edit 2.3

  1. 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!

  2. 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.

    1. Not surprised. I haven’t done much Chrome testing yet. Chrome is about to be a browser supported where I work at http://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.

  3. 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?

  4. *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;”

  5. 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?

  6. 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.)

Leave a Reply

Your email address will not be published. Required fields are marked *