WordPress are finally getting around to updating the Admin theme.
This is a great idea. From the beginning WordPress has generally looked great when going out with visitors but she dresses awfully sloppily around the house.
The front end just keeps getting better as the backend stagnates.
Unfortunately, current previews of the updated WordPress 2.4 Admin interface show a getup which looks worse if anything, than what’s there now.
I’m having visions of Mambo circa 2004. What’s with the dreadful new brown and orange? The blue on blue colour scheme is about all the WordPress Admin Panel has going for it aesthetically.
The only good looking Admin interface for WordPress has been Steve Smith’s WordPress Tiger Administration, which first saw the light of day in June 2005.
One of the beta testers for Foliopress WYSIWYG has just complained that Foliopress WYSIWYG is not compatible with PHP4. Apparently PHP5 is still only 6% of the installed PHP base across all webhosts.
That figure should be enough to strike terror into any developer. But that number will change very soon as PHP4 has hit the end of the line.
PHP4 incompatibility started off not as a deliberate decision. Generally I like wider compatibility.
But on serious consideration, I’m not worried about Foliopress WYSIWYG being PHP5 only.
Just when you think you’ve got technology under control, some small gnat comes along to bit you. I had just added and styled the nice registration form for people interested in Foliopress WYSIWYG and SEO Images to the previous post :
and then I began seeing double. That is to say two me:
dd add signature plugin error
That nice headshot with the articles is created by Alastair Dagon Design’s Add Signature Plugin. What’s seems to be causing the doublevision is the inclusion of a form inside a post. I tried moving the form into a Sniplet (where it should have been in the first place, quite frankly and reuseable). I’ve cured a few WordPress malfunctions by pulling code outside a post and into a Sniplet – but that was pre-Foliopress WYSIWYG. Most of the WordPress Editors damage or modify code so a Sniplet can stop them from getting a chance to break code. But this time the Sniplet trick didn’t work.
I couldn’t find the issue in the plugin itself:
Nor does the issue seem to be in our template index.php file, although there seems to be room for such an issue there.
Spent most of the day working on Foliopress WYSIWYG together with Peter Baran.
Our solution for the WordPress WYSIWYG and image handling nightmare is coming along quite brilliantly well. This is what the basic toolbar looks like.
Foliopress WYSIWYG offers true What You See is What You Get Editing for WordPress.
- It is backwards compatible with legacy code (hello Xstandard/TinyMCE)
- It doesn’t break complex forms (hello TinyMCE/Xstandard)
- It doesn’t discard whole posts (hello Xstandard)
- It doesn’t go haywire and create more and more nested P tags (hello WYSIWYG Pro)
- It doesn’t look like hell in the WordPress interface (hello normal FCK)
- It doesn’t make uploading images a never ending and hopeless struggle (hello WordPress uploader)
- It doesn’t make your clients hopping mad and lead them to breaking everything (Plaintext/RAW html)
- Your drafts look like exactly like your posts will, without having to waste time with a preview function (hello Xstandard)
- You have unlimited standard undo from the keyboard (hello Xstandard)
- Very easy to configure (including site WYSIWYG) (hello Xstandard, TinyMCE, FCK)
In short, Foliopress WYSIWYG is what you always wished the WordPress Editor would do. I’m using it now and can’t believe no one created and editor like this earlier.