Stats

Comments Posted By Andrew

Displaying 61 To 65 Of 65 Comments

Innovative Use Of Private Pages

I use that method in a theme of mine, but it isn’t for WordPress. Nonetheless the concept is a good one.

» Posted By Andrew On January 24, 2009 @ 4:58 AM

WordPress Needs To Revise Post Revisions

@Jeffro – I would also want a checkbox option to delete revisions on publication.

This has got me thinking about UI bloat thought and I think the following could be moved out of UI into wp-config, after all they only need to be set once, and could be part of the setup. After that there is almost never any need to change them unless you are already doing something much more significant.

WordPress Address URL
Blog Address URL
Email Address (the admin one)
Timezone
Date Format
Time Format
Week starts on
Remote Publishing (debatable)
Encoding for pages and feeds
The entire privacy page
The entire permalink settings page
The entire miscellaneous page

If we can all agree that these are not needed in the UI then we can start a campaign to really clean out WordPress.

» Posted By Andrew On January 25, 2009 @ 7:48 AM

@D -I agree that the feature is poorly implemented, I won’t rehash that myself now. However, I seem to recall that the developers did note that it broke PodPress and did actually offer a patch for it, but it was never implemented.

Does anyone else recall that or did I dream it?

» Posted By Andrew On January 24, 2009 @ 4:36 AM

@Ryan McCue -I don’t really want it turned off though. I want it to be properly thought out in the first place so it doesn’t need turning off.

It is also worth noting that it is the people who don’t know that are the ones who really need it to work properly and not clutter up their database. Who is it that gets blaned when their hosting gets $10 more expensive overnight for reasons they can’t understand. They just start bitching about WordPress.

Honestly, I would take an extra option over 600+ extra post entries per year without a second thought.

Andrew’s last blog post..How modular should a theme be?

» Posted By Andrew On January 23, 2009 @ 7:15 PM

OK, so where I do start on this?

1. The entire feature should have been a plugin only. This is not something that most users need, if anything it is something that most users explicitly do not need. All users, answer this, have you ever used it to go back on a post? I haven’t.

2. The whole concept is ill defined. I don’t see any good reason to have revisions for posts. Blog posts, as the blogosphere has communicated over and over again, should not be changed except to add updates. When they are changed they should explain what has changed. Therefore post revisions should all be deleted the moment the publish button is pressed, that is, if it really must be applied to posts at all.

3. The feature is really an attempt to fill the gap with CMS systems. In that respect I don’t think it is a bad idea, when it is applied to pages. If it only applied to pages you really wouldn’t need the setting.

4. If it really must be in the core, and it really must be turned on for posts and pages then these controls really must be in the core, and you must be able to turn it off.

Andrew’s last blog post..How modular should a theme be?

» Posted By Andrew On January 23, 2009 @ 6:50 PM