Comments on: WordPress 2.0.3 Tuneup Plugin

By: GamesPeru » 1

GamesPeru » 1 — Tue, 27 Jun 2006 16:09:33 +0000

[...] Comments (13) [...]

By: Rev. Bob

Rev. Bob — Sun, 25 Jun 2006 08:05:16 +0000

OMG!! Quicktags is back! I rolled in my changes from last time, and I’m back in business. Evidently moving quicktags.js to a different directory was enough to completely baffle me when I installed WP 2.

In case anybody wants to try my additions, they’re here: http://blog.crispen.org/etc/quicktags.js.gz.

My and ~~tags are much nicer, imho.~~

By: Dougal

Dougal — Fri, 23 Jun 2006 16:04:56 +0000

Bob,

The WYSIWYG editor is one of those things that everybody just has to agree to disagree on. Like you, I find it too limited for my use. Fortunately, you can disable it in your user profile (see the checkbox at the very bottom of the page).

The reasoning for turning it on by default is that we want WP to be user-friendly for non-techie users. But for advanced users like us, we have the option to turn it off. In fact, I have a homebrew plugin that turns off most of the other auto-formatting functions, as well. I just write all of the underlying HTML for my posts by hand.

I *do* use quicktags, though. Mainly just for adding links, or occasionally for unordered lists.

By: Rev. Bob

Rev. Bob — Fri, 23 Jun 2006 13:45:27 +0000

Is it just me, or do people really hate that new editor? I’ve been struggling with it to get it to behave, and to get it to do something useful (e.g., tags, ) I fear I’m gonna have to figure out how to write a plugin for that stupid editor.

The editor change was good if you’re afraid of HTML, worse than useless otherwise. They’d better get a bunch of new adopters with that editor, because I know at least one long-time user who’s really pissed off at them.

By: Jean Andre Vallery

Jean Andre Vallery — Wed, 14 Jun 2006 12:52:45 +0000

Do you have the time and experience to configure and fine tune a wpmu installation encluding using the cpanel to setup permissions as well as htaccesss configuration?

If not do you know of a good, and quick person to do this type of thing?

Jean Andre Vallery
Sarasota Florida
1-941-232-2183

By: Geof F. Morris

Geof F. Morris — Thu, 08 Jun 2006 19:56:39 +0000

Gosh. Once again, the lack of a co-ordinated, comprehensive testing program is biting WP in the ass.

By: Mark Jaquith

Mark Jaquith — Thu, 08 Jun 2006 04:07:22 +0000

I would NOT wait to upgrade. This is a security release. As annoying as these bugs are, they’re fixed by the tuneup plugin, and it’s not worth compromising the security of your data.

By: How to Blog : You might wanna hold off on upgrading WordPress until version 2.0.4…

Thu, 08 Jun 2006 01:14:43 +0000

[...] As has annoyingly been the case with many a WordPress release, turns out that this latest upgrade (WordPress 2.0.3) came with a few unexpected bugs. Dougal Campbell reports that a 2.0.4 version should be out soon. [...]

By: Dougal

Dougal — Wed, 07 Jun 2006 20:21:44 +0000

Marc: Revision 3850 is under the trunk, not the 2.0 branch. The most recent 2.0 branch revision at the time of this writing is 3841. From a quick look, I think that the plugin mentioned above is roughly equivalent to having revision 3828. (view changesets) The best way to keep track of it (for me) is to subscribe to the wp-svn mailing list.

By: Marc

Marc — Wed, 07 Jun 2006 20:00:56 +0000

I’m at Subversion revision 3850. Does that have the fixes?