mainfile.php warnings

Posted: Fri Oct 23, 2009 5:10 pm

I just upgraded my development site (locally behind my firewall).
It has display_errors = true, and I'm getting the following messages at the top of my pages:

Code:

Warning: opendir(./includes/addons) [function.opendir]: failed to open dir: No such file or directory in /home/gracious/public_html/mainfile.php on line 1960





Warning: readdir(): supplied argument is not a valid Directory resource in /home/gracious/public_html/mainfile.php on line 1961





Warning: closedir(): supplied argument is not a valid Directory resource in /home/gracious/public_html/mainfile.php on line 1966





Warning: opendir(./includes/addons) [function.opendir]: failed to open dir: No such file or directory in /home/gracious/public_html/mainfile.php on line 1960





Warning: readdir(): supplied argument is not a valid Directory resource in /home/gracious/public_html/mainfile.php on line 1961





Warning: closedir(): supplied argument is not a valid Directory resource in /home/gracious/public_html/mainfile.php on line 1966

All the warnings come out of the last function in the mainfile.php - readDIRtoArray. There is no ./includes/addons directory.
This seems to be triggered by code in header.php

When I created an addons directory - the warnings went away.
This will at least document the issue for others, but perhaps you want to put an empty directory in the package or a line in the instructions telling folks to create the directory.

Posted: Sat Oct 24, 2009 5:51 am

There is an empty directory in the package so you should not be getting these errors.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

webservant,

Please verify from your RNv2.4 download, that the empty folder is present. Some FTP clients will not transfer empty folders by default. You have to explicitly tell them to.

Posted: Sat Oct 24, 2009 10:13 am

I had a larger problem. My download was RC1 which did not have the addons folder. I've downloaded the current package (which does have the addons folder), and applied the changes including restoring the DB and re-upgrading. Much is better now, but not perfect.

Posted: Sat Oct 24, 2009 4:51 pm

The rest of my warnings were related to a previous install of NSN Project. Once I removed it, it works! Thanks.