Carpal \'Tunnel Location: "In your ear" Member Since: 9th Jun 2003 Total posts: 6207
Posted:where about is your php.ini held, if its not at top level dir, you would need to have a php.ini file in each of teh dirs that are dishing out php
if you have a look in joomla at the system setting page (in one of the menus across the top, you will be able to see where you php.ini file is being run from, and i would suggest that as you are on a shared server, that its not accessible to you, but only to the admin of the server, and to te apatche host.
veteran Location: Oxfordshire Member Since: 31st May 2006 Total posts: 1237
Posted:I've been looking at it it's a pig, it's ignoring the php.ini the host provided in the hosting directory root (have also tried site root to be sure). if that was a user loaded file I wouldn't be surprised, but they put it there.
tried disabling and re-enabling php to kickstart it, no joy, it might kick in with an IIS restart, but normally php would check it as the processor is called, so as you load a page.
and it's IIS without the htaccess compatibility mods, so they don't help. could add it to the global includes for joomla but it's not really a secure fix and he'd have to check it any time they patch joomla.