Hey all, We're going to have a bit of downtime in the A.M (well, morning my time) as we move some of our services to new hosting. It'll actually be a two step process with the 2nd bit happening in a week or two, but we're handling the hard stuff now. The forge, svn, translation center and downloads will be down starting at about 11 am UTC (7am EDT) and be down for 2 to 3 hours. I'm hoping to have the downloads and forge up first (I've already done a test run and it worked fine), and then work from there with TC being last. I'll then have some stuff behind the scenes to do for setting up various automations and backups, but that shouldn't affect any users. If there are problems, schedule changes or whatever, I'll post an update here. Thanks! Ted

Sorry folks. We got word a little bit ago about a security issue, so we pushed out a quick fix to make sure that people can't take advantage of it. Please update as soon as you can. Thanks! Version 1.2.5 "Free Hill" -- May 12, 2008 ----------------- - Fixed a security issue with the java applet functionality in the File Manager

Summer is coming... and so is that time when the geeks behind CMSMS get together and swap war stories. As with last year, we plan on getting together in some unsuspecting city and causing our own brand of havoc for a weekend. We also plan to discuss the project's direction and do some coding too... This year, the unsuspecting city is Philadelphia, PA USA, which also happens to be my hometown. We've selected it because we wanted it on this side of the ocean, it's relatively "central" to the people coming and I have a few connections for getting accommodations and other necessities. The dates are Friday, August 22 through Sunday, August 24, 2008. Actual locations in and around the city are still sketchy at the moment, as is the exact schedule. We are looking to have a public night one evening (probably Saturday) in which we can hopefully get some people to come out and tear up the town with us. If you're in the area or like traveling, then stay tuned for more details on that. We're also going to do a donation drive similar to last year. I'd love to defer the costs for people as much as possible. We'll discuss a goal and post that in a couple of weeks, probably around the same time as a set schedule. I'll keep everyone up to date with the details as I get them.

As you all know by now, CMSMS 2.0 development is now if full swing. Both calguy and myself have been hitting the code pretty hard over the last couple of weeks trying to finish it up and get a beta ready to go. While there is still a lot to do, I'm starting to see the end in sight. A few random folks have asked about helping out with development of 2.0, which I love. However, being the control freak that I am, I'm a bit worried still about giving the world free reign on subversion commit access. A few months ago, I discussed using git for core development. Yes, I still use this model for my 2.0 work and can't imagine switching back to pure subversion. I can be as A.D.D. as usual by having scattered branches of the various things I'm working on, and only commit them back when I feel stuff is ready. Anyhoo, github has gone live. This is pretty much the ultimate geek social network. It allows you to setup your git respoistories to the world. Better yet, it allows anyone else to essentially "fork" that repository, make their changes at will, and easily alert the original person to take a look at your changes. It's terribly brilliant and REALLY useful. I push the CMSMS code up to git every day or so from my personal mirror of the current svn repository. It'll usually be up to date. If I know people are working from it, I'll make sure it's always up to date within a few hours. The main repository is located here. Fork to your hearts content, people. So, do yourself a favor. Learn git. Use git. Love git. And once you wrap your head around it, use github to make those wild and crazy changes to the CMSMS 2.0 code and tell me about them. The proof is in the code, my friends. Get coding! Want to seriously be amazed at the power of git? Read this account. For some good links (even though there is a ruby spin), look here. Enjoy!

We've gathered up a security fix and a few bug fixes for a little maintenance release. I recommend you guys upgrade when you get the chance. Enjoy! Version 1.2.4 "Greenland" -- March 29, 2008 ----------------- - Fixed a potential security issue with the applet upload in File Mananger - Fixed a bug where IE users would have content list issues if there were odd characters in a page name - Fixed a bug where putting quotes in a "oneline" content block would cause issues while editing

Just because the blog has been deserted doesn't mean nothing is happening. About 3 weeks ago, I got myself into a position where I can resume the 2.0 development cycle. Not only that, I'm starting to get to enjoy all the work I did in the beginning of cleaning up and moving code around to make a more consistent API. New features are falling into place pretty quickly and I'm making some rapid progress. Some highlights of the last few weeks include: * Fixed the issues everyone was having with the installer. It's ugly, but it works. * Added the hierarchical permissions editing for content. It still needs to be added in a few more places, but it's a good start. * Start adding a test suite for things that I'm working on. It's by no means complete or even covering a major portion of the code, but it's the direction I'll continue down as I develop. * Removed xajax totally from the codebase and instead made my own version that's entirely written using jQuery. It does just what I need and nothing more. * Added active flags to stylesheets and removed them from templates. * Removed the built-in print functionality. It was ugly. Use print stylesheets. * Added methods to make sure all tables created by the api make proper utf-8 collations * Redid a lot of the Events system. It's now easier to create and use events, and also allows for attaching to events on the fly instead of having to register in the database. * Redid a lot of the module api. Moved the tabs to their own class. Removed methods that weren't really used. Moved the wysiwyg and styler methods to their own subclass. Added a backwards compatibility layer for older modules that still needs some work to be fully functional. * Created an acts_as_list dropin for the ORM system. This basically means that modules (or core items) that want to be ordered can add 2 lines of code and one field to the database and get a ton of functionality for ordering and reordering items. * Changed the parameter sanitization methods in the module api to use the new stuff built directly into php 5.2+. * Rewrote the menu manager to use nested templates. This basically means that menu manager templates will be MUCH easier to understand. It also means you can use different templates (or options) for children if you'd like. * Started a brand new blog module which will be included in the default installation. It will basically have all the main blog features that people ask for and should allow CMSMS to be a viable replacement for those people use Wordpress as a CMS. This also allows me to test that all the changes to the module api are good. * Moved all module templates to be administered in a central location. Not only that, but multiple templates for the same function are now supported by default. Modules no longer have to handle templates themselves, instead they just register the template on install and are good to go. Needless to say, it's moving right along. I still have no solid date for a beta, but I'm shooting for a couple of months from now. As long as I can continue at this pace, it shouldn't be a problem.