Just a couple of days ago, a customer contacted me about a strange issue - certain categories not being displayed in the blog navigation links.
I was able to determine that this only occurred for categories that also had a tag which was exactly the same. In other words, if there was a category called "announcements" and also a tag called "announcements", then the category version wouldn't be displayed.
The problem came down to how the categories and tags were being retrieved from the database, and so I've released a fix to address this, as well and tweak a couple of minor issues.
It's always a good idea to keep up to date, but this particular release isn't a mission critical change if you don't have categories and tags that are exactly the same.
Let us know if you have any questions!
UPDATE: Somehow, it totally slipped my mind that this update to Armadillo now requires PHP 5.3 - which is pretty much universally available on all major hosting companies that we know of. If need be, make sure to change the PHP version on your hosting account to 5.3 or greater.
I've just released v2.7.1 which includes a couple of seemingly minor but important bug fixes:
- Armadillo now removes the STRICT _TRANS_TABLE setting from the MySQL configuration, and does so in such a way that other configuration settings remain intact. You should now (knock on wood) never run into a error message similar to "no value specified for column default_content". Woohoo!
- That pesky bug that would prevent content from appearing and displayed an error message when the main Armadillo stack was used on the same page as other Armadillo stacks is now fixed.
There are also some other minor improvements:
- Tweaks to the German localization
- Armadillo is now grouped by the CMS, Online Editing and Blog tags in Stacks 3, so it won't appear as "ungrouped" anymore. I know, a long time coming, but it's here now!
Hope you enjoy the update!
And took much longer than I was expecting, mainly because I underestimated how difficult it is to manage multiple independent blogs in a single database.
That being said, v2.5 is a massive update to Armadillo and really extends its capabilities.
Here's a video about what's new!
I've realized over the past week or two, that there was more we could be doing to make Armadillo easier to use, and more intuitive. To remove some unneeded steps when you're trying to create and edit content.
To that end, we've just released v2.1.0 and the Armadillo Solo Content stack now has a new checkbox setting called "Auto Create?". When selected, Armadillo will automatically create a new piece of Solo Content with the specified Content ID, if it doesn't exist in the database.
This automatic creation occurs when you visit that page in a web browser, and will happen even if you're not logged in to the dashboard!
We also managed to squash a few more bugs related to the lightbox, and when using Solo Content stacks together on the same page as the main Armadillo stack.
Numbers-wise, this doesn't look to be that big of an update, but quite a few smaller issues have been addressed.
If you're using a European hosting provider with rather strict file permissions, and were having some difficulty getting Armadillo setup initially, you'll (hopefully) be very happy with the changes we've made. Armadillo now uses an entirely different approach to creating the media folder where all your uploaded images and other files are stored, which should be compatible with more hosting configurations and make things a lot smother.
On the Responsive front, mobile users with smaller devices like the iPhone 5S should enjoy the interface changes which reduce clutter and prevent overflowing text.
Several localization adjustments have been made for the Dutch, German, Polish and Swedish versions. Swedish users should also see their blog date in their native language.
Of course, this is a free update for all Armadillo 2 users, and it should appear for you when you next start Stacks. Enjoy!