Right, MODx CMS - again
Wednesday, October 28th, 2009
I have spent the best part of a week, on & off, playing with this to see whether it can be offered as a CMS to clients.
Having looked through the online instructions and battled with poor technical writing, I decided to buy the only book on MODx - and it was worth it, saving hours of frustration.
As I have said before, all these CMSs claim to be ‘user friendly’ - ‘get your website up & running in minutes’.
Ha! It’s like ‘Only metres from the beach’. Right.
Having said that, there are only a few concepts that need to be mastered. I decided that for the evaluation, I wouldn’t follow the online docs or the book example so used the template I often use from Dynamic Drive - the CSS fixed 3 column template. Slotted in fine.
Then I added my little radiussed box that is all the rage. Also fine. I used the content from zulu-culture.co.za as a smallish website with a few subsections.
The attraction of MODx as a designer is that it claims that any valid HTML template can be used. There are several ‘template variables’ that need to be added to make it a MODx template. These ‘TVs’ are chunks of code - like Javascript scrollers or meta tags that the user can edit from the backend.
The two other concepts are ‘chunks’, which are basically ‘includes’ and ’snippets’ which are bits of PHP code that do something. Most templates can be reduced to a bunch of includes, a menu area and a content area. The latter uses the TinyMCE editor which works fine although I prefer to get stuck into the code as it’s quicker.
The menu is easy enough but I thought I would use their builtin Wayfinder menu system together with JQuery to set up a CSS accordion menu. It worked too and users can add and delete pages! Other examples of snippets are logins and breadcrumbs. Any piece of valid PHP is fine. I thought I might chance my arm and add FormtoemailPro PHP formmail script as a snippet, all 80kb of it and it was accepted and the form worked fine.
Another exercise was to get database output to the pages. For simple SELECT and WHERE listings, all that is required is 4 lines of code as a snippet. I tried to use code from PHPMaker but as expected, that was kicked out with a flurry of errors.
The login presented a problem. I overreached myself and went for the WebloginPE addon which I couldn’t get to work. The builtin login works fine - but you need the book to work out how to do it. I got it to protect two sets of pages for two sets of users.
I tried a Stu Nicholls CSS image gallery - fine.
The search widget worked and I was able to set up a simple commenting system, either on a blog type page or on any page.
Joomla has 4,000 addons whilst MODx has a few hundred, spread over two versions of MODx. The Newsletter addon worked OK with a subscribe/user management system. The last thing to test - and it’s no big deal if it don’t work - is a forum. I cannot find anything in the plugins.
Summary
I think I’ll use it. The site (search-optimizers.co.za/modx) has all the basics that would be required by the average website. Next step is to use a totally different design (tvae.co.za would be a candidate) to see whether it could be accommodated.
It’s not difficult to set up manager-users and I think that they would be quite happy to edit, publish and delete pages.
