I'm not sure if that original mail went to the list or not, service has
been so spotty lately :/
Anyways, I would like to have a few minutes to check on that change to
the lastmodified column. It seems a little strange to me that this
issue would crop up now even though we never encountered that issue on
other sites, like BSC, where we certainly would have noticed if there
was an error that prevented weblog page rendering from working on a
stock 3.0 upgrade.
I am wondering if there is something unique about your upgrade path
which may be causing this problem.
-- Allen
Matt Raible wrote:
As far as an RC5, I'm fine with that, or just fixing it in SVN and
letting me try again. ;-)
Also, it'd be nice if andreas08 worked out-of-the-box, since it's a
new theme and all. I'd hate for folks to try it and it not work w/o
modifying properties.
Matt
On 10/24/06, Dave <[EMAIL PROTECTED]> wrote:
On 10/23/06, Dave <[EMAIL PROTECTED]> wrote:
> The problem:
> java.lang.NullPointerException
>
org.apache.roller.ui.rendering.servlets.PageServlet.doGet(PageServlet.java:168)
>
> Looks like a 3.0 bug, your website is has a null lastmodified date.
> You can work around the problem by setting lastmodified date to some
> non null value, perhaps now() would work.
The root problem is that we create the new lastmodified column with
default to null.
alter table website add column lastmodified $TIMESTAMP_SQL_TYPE
default null;
What we ought to do is to set the default to now() like so:
alter table website add column lastmodified $TIMESTAMP_SQL_TYPE
default now();
So we need an RC5. Does anybody else have Roller 3.0 RC4 feedback?
- Dave
