Here is a list of known issues and feature requests for upcoming versions of WP Super Edit. If you have an issue, you can always just Contact Me.
- TinyMCE Scan Issues – Some users are having a problem with installation during the scan settings process. The http://(WordPress Install Location)/?scan=wp_super_edit_tinymce_scan should return a blank “Complete” page. The scan process needs to be checked or removed!
- Nasty Bug – I have some sites that are loosing the scanned TinyMCE settings after moving from one server to another. Need some failure checking, and some settings tests.
- If your editor seems to only show the HTML or CODE after you upgrade to WordPress 2.7, then you may need to toggle the visual editor settings for your user profile. I experienced this myself with some users during a recent upgrade. For some reason I had to toggle the option in the user profile that reads “Disable the visual editor when writing.” This only happened for a couple of users. I had to check the box, save the profile, uncheck the box and re-save the user profile and everything was fine.
- Google Chrome has not been tested, but it should be similar to Mac OS Safari.
- Your visual editor might be turned off or need a good toggle. During some WordPress upgrades users may find that they only see the HTML portion of the editor. Those users should make sure the “Disable the visual editor when writing” option is not disabled in their user settings. In some instances after WordPress 2.7 users may need to toggle this option on and off to have their visual editor working properly.
- Only use the “TinyMCE 2.x Compatibility” plugin if you really really need it. I only added this when I was dealing with some old WordPress plugins that added buttons to the editor but hadn’t been updated in quite a while. It is more important to have developers fix things if they don’t work with the current TinyMCE editor. I hope to remove this add-on soon. This will break the editor in WordPress 3.1 or higher.
These are suggestions or issues. Depending on the complexity, they may be added to future releases of WP Super Edit. I can’t guarantee it, but these are worth thinking about.
- Add a manual button arrangement mode so users can type in button names manually. See if it would be useful to add a list of active button names and descriptions so users can reference the names to be typed in.
- See if we can make a custom css classes plugin that will either only use the editor.css file, or remove the custom WordPress classes from the style drop down list. (See Comment)
- Add user and role based option to remove HTML tab from editor.
- Add user and role based options for tinymce allowed tags.
- Of course it needs some WPMU compatiblity work.
WP Super Edit version 2.2
- WordPress 2.8 compatibility fixes.
- Big cleanup to move some of the interface class functions to normal php functions.
- A bug fix from vituko that should work better with some server setups.
- Removed backwards compatibility checks because several changes to TinyMCE and WordPress make backwards compatibility prohibitive to maintain.
- It is now using jQuery UI scripts that ship with WordPress. No more stupid big JS downloads for button settings.
- Updates to most of the packaged TinyMCE plugins for TinyMCE 188.8.131.52 (that’s a bunch of dots)
WP Super Edit version 2.1
- A bonus backport added as suggested by vituko that should make things work on more serve setups.
- Add font tag styling options for font face, size, etc as requested in wordpress.org forums.
- Switch to template_redirect method for settings scanning using a pseudo tinymce init.
- Clean up CSS for WordPress 2.7
WP Super Edit 2.0.x and Earlier
- Sorry didn’t keep good notes for these changes. WP Super Edit 2.0 was a major rewrite to make this plugin compatible with WordPress 2.5 to 2.6.