First, apologies to all who’ve pmailed me frantically that their mojo’s broken after updating to yesterday’s release of 0.16upgrade. At this point it is suggested to all mojoblog 0.15 folk who are using mojo in a “live” environment to not install 0.16 upgrade. Reports of sporadic upgrade issues from a few of our early testers has resulted in again, temporarily removing 0.16 from our files sections.

Bad, bad, man..

I’ll be the first one to admit when I foul something up and in this case, I’ve now done it a couple of times.

The majority of issues reported so far stem from the uninstall process currently in mojoBlog0.15 which can does cause database errors. We’re working on a patch for mojoBlog 0.15 that will eliminate these issues and allow users to upgrade to 0.16 without errors.

mojoBlog0.16 Full Release

We will release mojoBlog0.16 as a full install but are pushing the release date back another day or two until retesting is completed. New mojoBloggers are encouraged to download and install this latest version, of the 20 some odd installs we’ve tested and another 30 or so brave folk who’ve installed mojo out in the wild, there’s only been 1 small error reported.

more zing,more bling

0.16 is really more than an incremental release, it’s a significant change in MVC methods which affects the infrastructure of the blog code itself. It’s also the first release that further separates com_mojo from it’s ancestral roots, Marko’s com_jd-wp. In addition to these core changes we’re implementing almost 20 new functions and features that form the beginnings of a new abstract layer which will allow mojo deeper integration within the joomla ACL (reducing/eleminating permission errors) and new presentation abilities to load and display modules inside the mojo component layer and interact with joomla `bots and plugins.

Once we get all mojofolk stabilized with 0.16 we’ll be able to really focus on whittling down the short list including pretty urls and post titles.

Thanks for your patience and support,
kevin “mojo” murray