I'm happy to announce the new version of the unrivaled Joomla SEO component, AceSEF. This release includes several critical bug fixes so we highly recommend you to upgrade asap.
I'm happy to announce the new version of the unrivaled Joomla SEO component, AceSEF, and the magnificent Joomla Search component, AceSearch. Both of new versions are maintenance releases which contains mainly bug fixes and/or minor changes.
I'm happy to announce the new version of the unrivaled Joomla SEO component, AceSEF for Joomla 1.7 . In this release we've fixed some issues and improved the multi langual functinality of AceSEF according to Joomla 1.7
After a dead sleep of innovation for AceSEF component, we've pressed the start button again. Here we are with the first one, WordPress style SEF URLs in Joomla with AceSEF for Content, FLEXIcontent, K2 and ZOO components.
Ninjaboard extension 1.5.3 for AceSEF released. We have reduced the generated SEF URLs by using non-SEF variables in this release so that only URLs that may increase your SEO ranking will be generated.
As I said in my last blog post about AceSEF releases, the next releases cycle will be longer and it was (about 1.5 months). Now we have a new version which fixes a couple of bugs and adds some new features that improves the usability of AceSEF.
Yesterday I was providing custom support to one of our honorable customers. He was tired of the huge number of 404 URLs stored by AceSEF. The point that he couldn't get was that he used a crawler to see the 404 URLs on his site and the result was too lowly from the 404 URLs stored by AceSEF.
After a hard work we've finally released the first version of AceSEF 1.6 which is compatible with Joomla 1.6. There is no new features, only compatibility with Joomla 1.6. Due to the different API of Joomla 1.6, it is not backward compatible with Joomla 1.5. For Joomla 1.5, use AceSEF 1.5.
After a short time from the latest release, we have just released another improved version of AceSEF component. The most important change of this version is the low priority security fix. We're calling it as low because the "hacker" have to be logged in back-end so he could apply it.
