On 11/1/05, Anil Gangolli <[EMAIL PROTECTED]> wrote: > Henri Yandell wrote: > > >On 10/31/05, Anil Gangolli <[EMAIL PROTECTED]> wrote: > > > > > >>Henri Yandell wrote: > >> > >> > > > > > > > >>>Planning to take a look at them myself. Do a full Postgres install and > >>>make sure it starts up okay etc. > >>> > >>> > >>> > >>> > >>That, we should all do. > >> > >> > > > >Things went pretty well. Install easy as usual, it's a habit now so > >I'm a bad tester of that nowadays :) > > > >I hit an error when I tried to run an update on the Website->Settings > >page. I changed the editor, hit save and got a Hibernate error of: > > > >========================================================= > >net.sf.hibernate.JDBCException: Could not execute JDBC batch update > >Caused by: Batch entry 0 update website set name='Mr Testy\'s Weblog', > >description='Mr Testy\'s Weblog', > >userid='ff808081074a49d901074a4ac8770006', defaultpageid=null, > >weblogdayid='dummy', enablebloggerapi='t', > >bloggercatid='ff808081074a49d901074a4ac8840009', > >defaultcatid='ff808081074a49d901074a4ac8840009', > >editorpage='editor-dhtml.jsp', ignorewords='', allowcomments='t', > >emailcomments='f', emailfromaddress='', editortheme='sotto', > >locale='en_US', timezone='US/Eastern', defaultplugins='', > >isenabled='t' where id='ff808081074a49d901074a4ac8830008' was aborted. > > at org.postgresql.jdbc2.Statement.executeBatch(Statement.java:201) > > at > > org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:294) > > at > > net.sf.hibernate.impl.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:54) > >========================================================= > > > >The only odd thing about the data on the page is that the default page > >select box has nothing in it. Thus the null in defaultpageid. This is > >a not-null in the database, so I'm guessing this is the problem. > > > > > > > Not sure how you got to a state where the default page id was empty. In > 1.x, this should always be non-null. It typically points to the > Weblog.vm template. Bad things happen in the theme selector if the > default page is not there. > We make sure that you don't delete the default page in the template > editor either.
I think I've been getting null default page ids with every 1.3 install; I'm pretty sure I've seen this error before. The Theme selector seems to be working though. > >I was able to modify the user settings (Website->User) without > >entering a password. > > > > > Are you sure you didn't have a Remember Me cookie set? I was logged in. :) UI made me assume that I would have to put my password in to make changes to that data. Not a biggy as long as that's not the way it's meant to be. Hen
