New Roller version
Well, I finally updated to 4.0... it took a while, as I remembered the update to 3.1 from 3.0 was painful. (I don't know why I bothered, since I don't really use this thing. Maybe I should change the name to "Stuff Nobody Cares About... Not Even Me"...)
First problem: The roller update code detected the wrong running version. So it ran the wrong database migration script and blew up all over the place. Turns out there's a database table, called "roller_properties", that stores the version of the database, and I'm guessing my 3.1 upgrade never updated it. So, I logged into the database via the SQL client and executed a "update roller_properties set value = '310' where name = 'roller.database.version';" and that fixed that problem.
Other problems were just the normal struggles with Glassfish... which I should really upgrade as well. Originally I was using JNDI for specifying Roller's database, but this time I just used the roller-custom.properties file. I also had to tweak the file upload location.
The new Roller uses encrypted passwords by default. This is a problem, as it doesn't check to see if the user's (and admin's!) passwords are NOT encrypted and update them. There's a utility to "upgrade" the passwords, but that's rough to use if the application server and database are NOT on the same machine where you package the war file, as the utility is command-line.
Also, if you have a custom theme from the older Roller, it'll give you a 404 error when you upgrade. Again, problem. I ended up connecting to the database again and updating the "editortheme" column of the "website" table to change references to the dead theme to one of the new ones.
Other than that... it seems to be working okay. I even sort of like the new Sotto theme. I wish I had the web design skills to come up with something of my own, though.
Posted at
09:11AM May 01, 2008
by Brandon Hume in Java |