[wp-hackers] Replacing TinyMCE with Xinha

[Peter Westwood]

On Thu, November 30, 2006 11:07 am, Andy Beard wrote:
>
> Here is a semi-noob look at this, as I class myself as technically aware
> rather than a programmer.
>
> Most of my installations are running WP2.0.4 now. I didn't upgrade to
> 2.0.5
> because there was a reported bug that slipped through, and whilst Mark
> created a plugin to fix it, as a user I would expect 2.0.5.1 or 2.0.6 to
> be
> released a few days later to clear up the problem.
>

I don't see the need for a quick 2.0.5.1 / 2.0.6 in this case - the issue
is minor and only affects a limited user base - Mark's plugin provides the
fix for you _if_you need it.

Don't forget 2.0.5 contained security updates.

> I haven't received notification of this, so I am still running old code. I
> don't live in Trac, but maybe the 2.0.5 distribution was patched without
> notification.
>

No it wasn't - and that wouldn't be good (/me remembers the support
nightmare the one time long ago the download zip file was updated as bugs
in the release where found - the people providing support in IRC found
there code didn't match what people had just downloaded - it was a
nightmare!)

> I tried using TinyMCE for a while, but after a number of disasters with
> the
> formatting of posts that were only visible after they were published, I
> don't trust it enough to use it on any live blog, and I haven't got a huge
> amount of time for testing it specifically to be able to provide useful
> bug
> reports.
>
> If something works sufficiently well to use it on a day to day basis, and
> I
> can just drop someone an email to report a bug rather than wading through
> trac, I am much more inclined to report bugs.
>

Reporting by email only really works on small projects - trac is where we
as a community collect, triage and fix issues - if you really want to
report by email then wp-testers is the place to go - people on that list
will take you issue suggest a fix (and create the trac ticket for you if
your lucky)

westi
-- 
Peter Westwood <peter.westwood at ftwr.co.uk>
http://blog.ftwr.co.uk