Flux CMS DevBlog

While the new firebug beta looks and actually is great and worth checking out, it somehow breaks the navitree in the Flux CMS. It just doesn't load anything under the home collection. I have to investigate further, but the only solution right now is to disable firebug (or not upgrading right now to the 1.0 beta)

Update: I could fix it on our side. Somehow XMLHttpRequest.readyState stayed at 0, even though it usually directly goes to 1 after calling .send(). I put now a little check in there, so that it simply reloads the navi tree frame and all should be fine now (it works after a simple page refresh, mysteriously...).

I committed it to trunk and the 1.5-dev, but the patch can be applied to older versions, as well.

So, go and get the firebug 1.0 beta, it's really cool (besides that little annoyance :))