3 replies to this topic

[poulR]

If I try to pick "Manage Files" in the manager i get thid error:

Warning: dir() [function.dir]: open_basedir restriction in effect. File(/var/www/web24/html) is not within the allowed path(s): (/var/www/web24/html/:/var/www/web24/phptmp/:/var/www/web24/files/:/var/www/web24/atd/) in /var/www/web24/html/manager/actions/static/files.static.action.php on line 488

Warning: dir(/var/www/web24/html) [function.dir]: failed to open dir: Operation not permitted in /var/www/web24/html/manager/actions/static/files.static.action.php on line 488

Fatal error: Call to a member function read() on a non-object in /var/www/web24/html/manager/actions/static/files.static.action.php on line 491

Anybody knows how to fix this?

[Ralph]

As I recall, that isn't an Etomite error but, rather, a server side security restriction... Sounds like the server has been configured to disallow the dir() function which is then causing a cascading error with read()... This, essentially, renders the Manage Files feature useless...

You should be able to check for disabled functions and classes by going to Etomite Manager > System Info > Server Information > View and look for disable_classes and disable_functions...

Hope this helps...

[poulR]

Ralph, on 11 February 2010 - 12:26 AM, said:

As I recall, that isn't an Etomite error but, rather, a server side security restriction... Sounds like the server has been configured to disallow the dir() function which is then causing a cascading error with read()... This, essentially, renders the Manage Files feature useless...

You should be able to check for disabled functions and classes by going to Etomite Manager > System Info > Server Information > View and look for disable_classes and disable_functions...

Hope this helps...

In the srver setup I can choose: PHP safe_mode yes/no ; PHP open_basedir yes/no
tried to change, but didnt fix the error.

[Ralph]

If you see classes or functions that have been disabled, you won't be able to override the settings to re-enable them yourself... Once disabled at the server level they can only be re-enabled by the hosting companies support staff if they choose to do so...