Category: MODx

MODX Base HREF

There’s a lot of sites incorrectly showing how to use site_url in both MODx Evolution and MODx Revolution. Primarily, I use site_url with the html base tag. If you don’t already know the base tag goes inside head and specifies the default address.

In MODX Revolution, our code in a template would look like:

<head>
<title>Some Revolution Page</title>
<base href="[[++site_url]]" </>
</head>

In MODX Evolution, our code in a template would look like:

<head>
<title>Some Evolution Page</title>
<base href="[(site_url)]" </>
</head>

Hope this helps.

MODx How To Properly Link To a Page

In MODx, it is always preferable to link to another page using the document id instead of using the friendly alias because sometimes MODx Evolution has a package that is appearantly capable of using the alias instead of the document id to provide a working link to another page.

The reason you shouldn’t use the alias instead of the document id is because it isn’t unheard of to have google or other search engines incorrectly access another page perhaps one that isn’t even available.

Using the document id is done in the following manner for Evolution:

>a href = "[˜77˜]"<Link to document 77>/a<

Using the document id is done in the following manner for Revolution:

>a href = "[[˜77]]"<Link to document 77>/a<

The documentation for MODx Revolution is really geat and should be used to learn additional things.

Hope this helps!

MODx Revolution – Dynamically Generating Google SiteMap XML

Google SiteMap and the other web tools provides a way for the owner or webmaster of a site to easily submit all of the pages to Google and keep track of which ones are crawled and indexed. Wikipedia provides a much more detailed description which goes beyond the scope of this post.

I didn’t want to have to manually try and figure out which links are children of other links for my own site (which again only has 5 pages anyway!) or other things like that, so I was looking for an automatic way to generate the google sitemap and then be able to provide it to google.

MODx Revolution has a plugin called GoogleSiteMap which uses a snippet called GoogleSiteMap I created a page, set the template to empty, and called the snippet directly on the page and then took the xml it created and pasted it into an xml file to submit. The XML it generates even correctly does the last modified date.

Hope this helps!

Wayfinder in MODx Revolution

When I first tried MODx Revolution (which I did try before MODx Evolution) I found the documentation to be pretty good except about snippet syntax. The tag syntax has changed from MODx Evolution to MODx Revolution.


[Wayfinder? &startId=`0`]

has to changed to

[[Wayfinder? &startId=`0`]]

More information can now be found here for all of the tag syntax changes.

MODx – Evolution – 1st Impressions

I haven’t been using MODx for very long, but I have worked with several other content management systems previously and experienced both the good and the bad with them. MODx appears to be a fairly simple MVC style content management system with a bit of a pluggable architecture. I haven’t written any plugins for MODx, but it appears that hooks are used just like WordPress does.

I have found MODx to be very easy for creating fully tableless XHTML compliant sites and creating very search engine friendly websites. Very easily, it is also possible to hide what cms is running the site by using the easily created pretty urls. (There’s just a couple of simple settings and a file renaming.)

I found the templating system to be extremely frustrating because the template is actually stored in the database instead of in the file system like done in most traditional CMS. I really find editing the templates, snippets, and larger chunks extremely frustrating to edit in the manager because of the lack of syntax highlighting, and issues with formatting.

Of course, the manager does offer the advantage of being able to edit content and site structure from pretty much anything that can access the internet and doesn’t mind some fairly heavy javascript use. MODx’s requirements for webhosting aren’t exactly hard to find either although there is a forum of reviews and suggestions.

Overall, MODx doesn’t appear to be too bad for smaller boutique websites which are a large chunk of my current business. I believe I would recommend it to fellow freelancers for smaller websites that don’t have much need for plugins or high amounts of customization.