in Quid Pro Quo, Rails

Upgraded to Typo 4.0

Well, the upgrade to Typo 4.0 didn’t go so well. No data loss though, so everything’s cool.

At least most pages seem to be functional, so this is not so bad. Combined with having custom sidebar plugins that no longer work, the fact that the merge between the new code and my old one did not quite go as planned, it was not a too pleasant (most of it my own fault I guess).

Anyway, it is getting really late and I’ll finish the rest of the migration tomorrow.

If you tried to access the site while this was going on and you were inconvenienced, pleas accept my most sincere apologies!

If you notice anything weird, please send me a mail at psq _at_ nanorails _dot_ com.

Update, about 20h later, some sleep…: It seems that everything is back up, I migrated my custom plugins to typo 4.0 (about removing 1 file, removing half of the code linked to configuration and adding a few lines) and it seems that everything has been working smoothly :)

And the best of all of that: no more trackback spam! Well, not that it went away, it caught about 25 since last night, but they don’t get published anymore. Just for that, it was all worth it. Thank you everyone in the typo team!

Update 2: Well rails 1.1.5 came out, and it was not enough, so rails 1.1.6 came out and seems to be strong enough to fill in the security issues

And in the process, I also upgraded to Typo 4.0.2

That last upgrade went very smoothly!

However, I’ve had a few annoying cases of nanoRAILS hanging and not responding for hours on hand till I killed the processes. I don’t know yet at this point whether it is due to the new version of rails, the new version of typo, or pehaps some settings that changes on dreamhost. In any case, I’ve installed my own version of ruby and the full set of gems, so we’ll see if that helps!


  1. I’ve just went through the same upgrade as yourself a few days ago! My blog is nowhere near as big as yours but I had many of the same problems! I’d ported your Bookmarkit sidebar to Typo 4 myself but just noticed you had ported it yourself already! Do you plan on releasing the code as I’m guessing your code is probably cleaner then mine :)


  2. Yes, I just ported it, plus the recent posts plugin I’m using and I’m planning to release over the weekend along with some instructions on how to migrate sidebar plugins from 2.6 to 4.0.2. I got sidetracked by rails 1.1.5 and 1.1.6.

  3. Hmm, your textlinkads sidebar does not work for me on typo 4.0.2.
    I installed it but it doesn’t show up in de sidebar tab in de admin panel :-(

  4. Strange. It works on my install. Anything in the log?
    Where you using the older version before? There are less files (remove configuration.html in textlinkads).

  5. Ok, I was very very stupid.
    I placed it in components/sidebars/ instead of the plugin directory.
    It seems to work now.

    Thanks for your time Pascal

  6. Oh, very nice. Typo plugin system is going to be simplified for 4.1 and should help in such case.
    Let me know if you have any suggestions to the code.

Comments are closed.