Thanks, Oli. Could you possibly attach a patched folders.php? for 1.5.9?

That would be lovely. I am on shared hosting, and don't typically apply patches that way, so it's new to me.

Thanks,
Ken

Strangely, I am getting this error after upgrading to 1.5.10! Which all ready includes the patch. When I ran the php wizard, I started having the problems.

Warning: opendir(/tmp/.horde) [function.opendir]: failed to open dir: Permission denied in /home/mysite/public_html/libraries/joomla/filesystem/folder.php on line 423

Warning: readdir(): supplied argument is not a valid Directory resource in /home/mysite/public_html/libraries/joomla/filesystem/folder.php on line 424

Warning: closedir(): supplied argument is not a valid Directory resource in /home/mysite/public_html/libraries/joomla/filesystem/folder.php on line 450

From the same page I am getting:
PHP Checks
register_globals is on.
safe_mode is off.
allow_url_fopen is on.
Functions disabled: show_source, popen, proc_open.
open_basedir not used.

Hi,

are you sure, this has changed after the PHP wizard? The warning sounds more like a file permission problem... Which action causes the problems above?
regards,
Oli

I might had messed it up, following the permission fixes (644/755), but when either I use my home directory or my web apache in the base directory, it only gives an error while accessing the /tmp directory (which exist in both the home and html directories). When I include the /tmp in the base, it goes crazy and gives a series of errors and in the tmp directory content it list 39000 items.

with only the home or html:


when including the /tmp it gives:

Hi,

ok, that makes things clearer. You changed your joomla-tmp directory to the standard apache tmp directory. In that directory other applications created folders which you (or actually joomla) is not allowed to read.
I would propose: Create a special tmp directory for joomla and include that in the open_basedir parameter.
btw.: GuardXT only changes permissions of files/folders below joomla root.
regards,
Oli

Actually I never did change it, it was /tmp

Not sure if it gave me the error under 1.5.9, but apparently 1.5.10 uses absolute paths to the tmp folder. Some how it used to point to the tmp folder in the joomla directory. I changed the tmp_path to show the absolute path, and it seems to be happy now

Thanks

By the way when I click on the link on the notification email, it doesn't allow me to enter comments. I have to go up to the topic listing and then select the topic again

From this experience I reduced the configuration.php privileges to 550, this might be a test you might want to add to guardxt, for it reduces the chances of someone else reading its content.

Edit:
Seems that after upgrading to 1.5.10 several settings of the configuration.php were changed, including the tmp_path. Also guardxt seems to give read rights to group and world, only the user and maybe the group should be able to read this file.