Trying to install zend module, have followed steps 1 to step 4, step 5 of instructions says
"Visit admin/settings/zend and put in the parent directory to the Zend folder"
the zend option does not appear to be available on the admin settings configuration page; entering the url "admin/settings/zend" directly just gives "admin/settings/" page.
I am getting this message in the log:
warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/usr/share/pear/Zend) is not within the allowed path(s): (/var/www/..../data:.) in /var/www/..../sites/all/modules/zend/zend.module on line 45.
Comments
Comment #1
mfer commentedVersion 2.x does not have an admin screen. The variable is a hidden one. It can be manually set but does not have a UI for it.
Currently, the module first looks for the hidden variable. This is followed by checking for and with the libraries module for the Zend Framework. If it was not specified in a variable and it is not being supplied by the libraries module the php include path is checked.
In your case it is looking in the PHP include path. But, it looks like safe mode is enabled and is causing problems.
Suggestions welcome on fixing this. I'm thinking we detect the PHP version, it is less than 5.3 we check if safe mode is enabled. If we are in safe mode we need a reaction or message to handle this.
Comment #2
patriiiiiiiiiick commentedWhile I don't have the error reported higher, I am also blocked because of the lack of UI and outdated documentation. Could you please update the installation instructions with what has to be done with the 2.x version?
Thank you in advance!
Patrick
Comment #3
mfer commented@patriiiiiiiiiick This if for the development version and the installation instructions are in the README. Once we are comfortable with this the information on the project page will be updated.
What do you need a UI for? Are you not up for using the libraries module or including it in the PHP include path?
Comment #4
patriiiiiiiiiick commentedNothing says in the installation instructions that they are specific to 1.x. And both versions are marked as dev. Something should be written to warn that those instructions are not valid with 2.x.