It's probably not a good idea to be up until 3 in the morning fixing wonky code -- particularly when I had to be up at 5 -- but that's just how we roll here. And it's not as if I'm not too obstinate to simply set aside a particularly stubborn problem until the blasted thing is fixed.
The problem was something that I remember having back when I'd first installed and ran Joomla, the infamous JFolder::create: Could not create directory problem. Specifically, Joomla couldn't seem to find the installation package whenever I attempted to use the Extension Manager to install components or templates. I'd found a work-around initially, but it escaped my memory, which in turn forced me to hunt down a real solution.
The general consensus appeared to be that it was a file permissions issue, but a quick check on Filezilla told me that no, the correct permissions were all set on the relevant folders. The second best solution was that the path was wrong, but another check told me otherwise. So I basically spent hours until I found a good combination that finally worked. So here it is.
First, check with Joomla itself to find out if it's reading your folders as writeable by going to the Admin Panel and selecting System Info > Help Section > Directory Permissions. Even though the folders themselves may be set correctly, Joomla might not be reading them that way. In my case, both the tmp and logs folders were listed as unable to be written to.
The next part is a bit of a PitA, but it was the only way to force Joomla to read them correctly: you'll need to edit your configuration.php file. (Make sure you have a backup copy in case something goes wrong) Find the the two lines that look something like this:
var $tmp_path = '/localhost/longassstring/ofcode/yourwebdomain.com/tmp';
var $tmp_path = '/localhost/longassstring/ofcode/yourwebdomain.com/logs';
Change these to:
var $tmp_path = '../tmp';
var $tmp_path = '../logs';
Even if the path is correct, (as it was in my case) Joomla won't necessarily read it due to redundant security. (Which is what makes Joomla so difficult to hack... we like that in a man CMS) This way, even if your host makes weird changes that Joomla doesn't like, it can find its own way.
Lastly, if you can't force your FTP client to overwrite the existing configuration.php file, you'll have to delete the one on the server and re-upload the edited one. If you changed only those two lines, you shouldn't have any problems.
For me, this cleared my problem right up. Now, if only the updated version of Gantry would stick...
Friday, 08 July 2011 11:40