Skip to content

open_basedir issues #4

@damanic

Description

@damanic

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;

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions