apache apachecon app apple asf atom atomprotocol atompub barcamprdu blogapps blogging businessblogging conferences family feeds foss general glassfish google humor ibm java javaone links linux mac microsoft movies music netbeans opensocial opensource photos politics rest roller rome rss socialnetworking socialsite socialsoftware sun triangle trianglebloggers vacation webdev webservices wiki


Main | Next day (May 30, 2004) »

Saturday May 29, 2004

JRoller: Roller 0.9.9 upgrade complete

Comments[12] by Dave in Roller

I have successfully upgraded JRoller.com to Roller 0.9.9. If you encounter any problems please report a issue on Roller's JIRA issue tracker located here: http://opensource.atlassian.com/projects/roller.

  • For all users: Roller now supports locale and timezone settings for each user. You can set your locale and timezone on the Website->User page of the Editor UI.

  • For users (excluding Hani) who have customized page templates: if you added a call to $pageModel.getRecentWeblogEntries() in your weblog templates, you will need to add a second argument to the call. In Roller 0.9.8 the method took only one argument, an integer being the number of entries to return. In Roller 0.9.9, the method takes a second parameter, a string being the category of posts to be displayed. Pass in "/" to include all categories. For example: $pageModel.getRecentWeblogEntries(15,"/") would get up to 15 recent entries in all categories.

JRoller upgrade on for today.

Comments[0] by Dave in Roller

I worked out the problems with the database upgrade scripts and code. I'll be upgrading JRoller in the next hour or two.

UPDATE: upgrade is underway.

MySQL update kills timestamp fields?

Comments[4] by Dave in General

I've got a table that looks like this:

create table comment (
    id         varchar(48) not null primary key,
    entryid    varchar(48) not null,
    name       varchar(255) null,
    email      varchar(255) null,
    url        varchar(255) null,
    content    text null,
    posttime   timestamp not null,
    spam       bit default 0 not null,
    remotehost varchar(128) null
);
And I want to set the spam field in all rows to false like so: 
update comment set spam=false;
But that command also resets all of the posttime fields in the table to the current time. If I use the following command, my posttime fields are preserved. 
update comment set spam=false, posttime=posttime;
What's up with that? Why does an update of one field affect other fields?

This work is licensed under a Creative Commons License.
Copyright 2002-2007, David M Johnson (dave.johnson at rollerweblogger.org)

This is a personal weblog, I do not speak for my employer.