Well, today in the WordPress weekly digest 11th February to 24th February 2008, (posted today, the 28th) about three-fourths of the way down, what do I see?
- Update to TinyMCE V3.01 (#5944).
This digest is talking about WordPress 2.5 development which typically runs a little ahead of the MU development (used on the ol’ dot com). 2.5 is scheduled for release on March 10, 2008 and I expect the MU version will be at least a couple weeks later than that. It may make it into dot com a little sooner as they typically use dot com bloggers as unsuspecting lab rats for testing things before release.
And Now For the Customary Paragraph of Caution!!!
Before you Safari fans break out your dancing shoes and champagne, remember that TinyMCE may be compatible with Safari 3, but wordpress surrounds it with a whole lotta their own home-grown code, so there could still be problems. Give the rash of problems seen in the past when upgrades are loosed on the general blogging public, one has to wonder about the thoroughness of WordPress pre-release testing.
So, I’ll end this with cautious optimism since I am writing this on a Mac in Safari 3 which I “hacked” so that it would lie to WordPress and tell it that it was Firefox instead of Safari. I find it soooo interesting that that is all that I had to do to get WordPress/TinyMCE 2.x.x and Safari 3 to play nicely together.
[Edit: This version of TinyMCE is only fully compatible with Safari 3. Those still on Safari 2, will still have the same problems as you always have. Turn off the Visual Rich Text Editor, or use a different browser such as Firefox or Camino – or upgrade to Mac OS X 10.4.11 which comes with Safari 3.]
The Sacred Path
Feb 28, 2008 at 5:19 pm
Oh my! Let’s hope they cure the wordpress end of things before this occurs. Sheesh … 10 days from now.
Feb 28, 2008 at 5:37 pm
I’m not about to install 2.5 on my self-hosted blog till I have at least a couple weeks to see what problems crop up in the wordpress.org forums. Mine is working fairly well right now on 2.3.3 and I’m not going to muck things up unnecessarily by rushing into 2.5. There are still 434 “active tickets” on 2.5 and it’s listed at 52% complete right now. I find it hard to believe they can go through so many tickets in such a short period of time, which means they will have to let some of them go. Are any of the ones already complete at least in part dependent on some of those still open?
Inquiring minds want to know!!!!
Feb 29, 2008 at 4:17 pm
Dunno if it’ll work with 2.5 or TinyMce 3, but Text Control has solved just about all of my WordPress (2.3.3) editor problems, including that lovely bit where they strip out line breaks.
It’d be a lot easier if WordPress would just, you know, stop telling me what I really wanted to do, but that’s not going to happen.
http://ckon.wordpress.com/2006/08/14/updated-version-of-text-control-that-works-with-wp-21/
Feb 29, 2008 at 5:01 pm
@matt
Thanks for the link, I’ll have to check it out. I switched to the fckeditor plugin (on 2.3.3) which is a little slow to load and save, but works without a hitch with all browsers I’ve tried it on.
Mar 1, 2008 at 5:39 am
I’m with you, Richard, about not upgrading to 2.5 immediately. I wouldn’t be surprised if there’s a 2.5.1 within a week.
As for TinyMCE, if the new version enables it to load in under one minute I’ll be joyous.
Mar 1, 2008 at 9:13 am
@ella
I used to like being on the cutting edge – an early adopter – but now I prefer to let others be sliced up on the cutting edge and wait until it is dulled down a little. That comes from experience. I have scars to prove it.
TinyMCE is quite solid in my experience playing around with it, so if there are problems when it shows up in 2.5, then the problems are with WordPress’ implementation, not TinyMCE.
As an interesting aside, I had tried the online 2.x.x demo version of TinyMCE they had on their website with Safari several times in the past, and it never once stripped out my paragraph breaks. That always confused me. Of course, it reinforces my belief that the problem was mostly with WordPress, not TinyMCE.