With Joomla so popular now that even Paris Hilton uses (and breaks) it [Editor note: It seems early reports of Ms. Hilton using Joomla are not accurate- see the comments in the original post from Joomla core team representatives], it's no surprise that new Joomla User Groups (JUGs) are popping up all over the map.
The latest is in Wisconsin, where the Milwaukee User Group will hold its first meeting in a couple weeks. A few of us Vermonters call the New England User Group home, which has grown to an impressive number and is now helping spin off another new JUG in the seacoast region of New Hampshire (near Portsmouth.)
And then there are Joomla Days like the upcoming one in Las Vegas. Unfortunately we'll never know what happens there, because what happens in Vegas So you'd better find your own local Joomla User Group and/or Joomla Day to attend!
It's been two months since a new version of Joomla 1.5 hit the streets, and not a moment too late. The new release has the longest change log we've seen in a long time, including some high priority security issues and dozens of bug fixes and changes.
The list of changes is long and worth taking a look at.
The Joomla Project is moving along and fixing security and other problems monthly now, and it's important to keep on top of these regular updates.
From their news release, see what's changed in this most recent version:
From the Joomla.org website:
The Joomla! community is pleased to announce the immediate availability of Joomla! 1.5.6 [Vusani]. This is a quick turnaround security release to address a high level security issue and it is recommended all users upgrade immediately.
A flaw in the reset token validation mechanism allows for non-validating tokens to be forged. This will allow an unauthenticated, unauthorized user to reset the password of the first enabled user (lowest id). Typically, this is an administrator user. Note, that changing the first users username may lessen the impact of this exploit (since the person who changed the password does not know the login associated with the new password). However, the only way to completely rectify the issue is to upgrade to 1.5.6 (or patch the /components/com_user/models/reset.php file).
For more information about this exploit, click here to visit the Joomla Security Blog.
The pace of improvements to Joomla 1.5 seems to be quickening this summer, as we're seeing new versions in weeks now.
This release also contains "important SEF URL improvements and fixes for com_content in addition to a number of bug fixes and improvements."
Be sure to upgrade today, especially if you upgraded to version 1.5.4.