/usr/local/www/v-webs/games.savage.za.org/html/index.php, then it should work under
safe mode too.
Chris Knipe wrote:
{if (file_exists("themes/$ThemeSel/modules/$name/$mod_file.php"))
an$modpath = "themes/$ThemeSel/";If you have using a new php.ini file, perhaps you can compare it with
}
I don't get it?
Warning: Unable to access themes/DeepBlue/modules/News/index.php in
/usr/local/www/v-webs/games.savage.za.org/html/index.php on line 46
Line 46 is the if statement
myold
one and see if there's anything different--might give you a hint.Yeah, and no. It's FreeBSD-Ports, my php.ini is unchanged. FreeBSD
installs the new / updated ini files as ini-dist, so hence, nothing on
it'ssettings has changed. I did also check to verify this, and it is indeedthe
correct ini file, with the correct settings...not
But then again, perhaps the problem is somewhere else... (i.e. file is
Right, I might be typing faster than I am thinking... :)there, permissions, etc.)Yes the file does not exist. But isn't that why file_exists() is there?
Still, just make sure that PHP is using the php.ini file that you think
using. The file that _you_ check didn't change but _php_ might be lookingAs ridiculous as this sounds...
somewhere else... Of course, I could be wrong--haven't used
FreeBSD/Ports--only linux.
Turning of safe mode made the warning go away. Now, I guess the question
is, 1) is this a bug in the file_exists() function, or 2) does the default
warning levels increase when operating under safe mode?
Either way, this never happened to me before, and is only now happening
since upgrading from 4.2.1 to 4.2.2...
Rather peculiar I think...
--
me
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php