Switched to wordpress
Finally got tired of messing with pebble, and decided to give wordpress a try. Much better! Only problem is that my permalinks have all changed. Hopefully I’ll figure out a way to map the old permalinks into the new layout - one of the wordpress custom formats gets close, but instead of the leaf being the pebble article id, its the article title - which I do prefer. I guess I’ll have to add in custom rewrite rules for all the old ones. Anyone else have a better idea?
May 23rd, 2007 at 10:10 am
If you have any feedback that you think would make Pebble better and help future users, I’d be more than happy to receive it, good or bad. Good luck with the new blog.
May 23rd, 2007 at 10:58 am
Nothing against pebble per se, its just not quite as feature complete as wordpress, and I got tired of wrestling apache/mod_jk/tomcat everytime I upgraded my system
The file based DAO in pebble also isn’t as robust as it could be. If a blog entry is in a directory that doesn’t match the date in the filename/blogid (millis since epoch), NPEs abound. This happened to me when I updated pebble and timezone defaults were added (changed?) to code, so that the filesystem paths were being created against GMT instead of EST, so expected path was 1 day in the future of where the file actually was - this broke everything from trying to view the day those entries in, trying to view unpublished entries, trying to export the blog as rss, etc. I was going to submit a bug report, but couldn’t find the bug tracker on SF - you should probably open that up to general submissions or if you use something else, make it more immediately obvious
If you want to stay self contained, it might be worth having the option to use something like hsqldb, and have import/export between the diffferent DAOs