Imagewize upgrades Joomla! Tags

Imagewize has recently upgraded Joomla Tags to the latest version, v1.3.3. This can be done simply by installing the latest version. This will automatically overwrite the existing version as long as you have version 1.2x. From now on Joomla! Tags will play nice with our SEO SEF extension SH404SEF.

Improve performance of your Joomla! website

I have been experiencing slower and slower loading time over the last several months. Mainly because of an increase in the number of visitors, but as well because I have added several interesting Joomla Extensions such as Tweetme and sh404SEF, two great tools. The former I added for better promotion of our website, the latter for better SEF urls. So, because of these changes the loading time has slowed down and has become more important. People do not like to wait.

Ubiquity does not play nice with CodeCitation Syntax Highlighter component

I recently installed the latest Ubiquity beta Firefox Add on, which worked really well under the latest Firefox (3.6.3), even with Twitter. The fun ended though when I realized it prevented my blog pages from being loaded properly

Today I installed the Joomla! update manager which I found here on de JED site. Amazing I hadn't worked with an auto updater for Joomla! before. After installation I tried to update to Joomla! 1.5.15 , but I kept on getting errors like:

JFolder::create: Infinite loop detected Unable to create destination

In the Apache logs I found:

[Fri Nov 27 12:46:22 2009] [error] [client xx.xx.xxx.xxx] PHP Warning: is_dir()
 
[<a href="/function.is-dir">function.is-dir</a>]: open_basedir 
restriction in effect. File(/) is not within the allowed

path(s):
(/var/www/vhosts/domain.com/httpdocs:/tmp) in 
/var/www/vhosts/domain.com/httpdocs/libraries/joomla/filesystem/folder.php
 
on line 392,
referer

http://domain.com/administrator/index.php?option=com_jupdateman&task=step2&target=patch

I understood there was an open_basedir security issue with the way the component handled the upgrade, but I did not find a solution right away. I searched for it quite a while to figure out what was going on and posted questions on the J! forum.