Graffiti CMS 1.2 Released

Blogging software Graffiti CMS has just been updated to version 1.2. This is predominately a bug fix release in advance of version 2 being released in May 2009.

If you use Graffiti to run a blog on your home server, you’ll want to check out these fixes:

Corrected Gravatar markup

· Dictionary references (%{}) in macros now work correctly

· PostsByTagAndCategory no longer returns an exception if no posts are found or an invalid tag or category is passed

· Now trapping invalidly formatted email addresses on the Contact form

· Time settings in error log now reflect the time zone offset

· Deleting navigation links containing special characters now works correctly

· Control Panel post category filtering is now maintained when “older posts” and then “newer posts” are clicked

· Updated VistaDB database engine to current version

· EveryoneRole no longer counts as a content publisher when it doesn’t have edit/publish rights.

· Search results now respect permissions

· Categories tree sidebar item in Control Panel now reflects posts correctly with same-named sub categories.

· Revision dropdown in Control Panel now shows the correct time/date stamp for each revision

· Corrected Comments paging in the Control Panel

· Corrected the XSS issue

More Info: Graffiti CMS 1.2 | Download


Enjoyed this post? Share it.

If you enjoyed reading this post, then why not share it with your friends and followers?

About Terry Walsh

Terry Walsh is the founding editor and owner of We Got Served. Since February 2007, the site has provided detailed coverage and analysis of the emerging home server category, and has subsequently grown into a trusted outlet for digital home news and reviews.

Sign Up for WGS Daily News

If you don't want to miss out on the latest news from We Got Served, why not subscribe to our daily digest? You'll get the day's headlines and a short summary of each news item delivered straight to your inbox each morning.

, , , , , , , , , , , , , , , , , , ,

  • Brent

    Thanks for the post Terry. It is nice to know there was an XSS “issue.”