Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

open_basedir issues #4

Open
damanic opened this issue Aug 16, 2013 · 0 comments
Open

open_basedir issues #4

damanic opened this issue Aug 16, 2013 · 0 comments

Comments

@damanic
Copy link

damanic commented Aug 16, 2013

Setting the default config to
$CONFIG['ERROR_REPORTING'] = E_ALL | E_STRICT;

Causes the frontend CMS pages to fail on an install that makes use of open_basedir. (Encountered Win/PHP5.3) . This is the case even though the open_basedir permissions allow for the full install location of PHPR

file_exists() checks in the controller classes will throw an open_basedir warning and throw a front end exception instead of moving onto other file location checks and eventually rendering the page.

So suggest installer goes with
$CONFIG['ERROR_REPORTING'] = E_ERROR | E_STRICT;
or update classes to ignore warnings on any file_exists break;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant