I'm getting the following warning:
Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(/usr/local/php5/lib/pear//home/kitchensisters/kswebsite/archive/plugins/CollectionTree/views/helpers/SearchForm.php) is not within the allowed path(s): (/dh/web/phpmyadmin:/tmp:/usr/local/lib/php:/home/kitchensisters:/home/kitchensisters) in /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Loader.php on line 186
The solution for a similar similar warning was to add set_include_path('.'); to paths.php http://omeka.org/forums/topic/omeka-13-install. There is no paths.php in Omeka 2.0, so where do I go to change this now?
The Omeka 2.0 equivalent of paths.php is bootstrap.php.
Thanks, That got rid of the warning, but it seems to have thrown my whole Omeka ecosystem out of whack. I'm now getting an error that ImageMagick isn't properly configured. And when I try to upload a file to theme_uploads, I get destination directory is not writable. The site seemed to be running ok with the "open_basedir restriction in effect" warning. Maybe I should just let it be?
#0 /home/kitchensisters/kswebsite/archive/application/libraries/Omeka/Storage/Adapter/Filesystem.php(116): Omeka_Storage_Adapter_Filesystem->_rename('/tmp/1bc6fdce1a...', '/home/kitchensi...')
#1 [internal function]: Omeka_Storage_Adapter_Filesystem->store('/tmp/1bc6fdce1a...', 'theme_uploads/1...')
#2 /home/kitchensisters/kswebsite/archive/application/libraries/Omeka/Storage.php(67): call_user_func_array(Array, Array)
#3 /home/kitchensisters/kswebsite/archive/application/controllers/helpers/ThemeConfiguration.php(107): Omeka_Storage->__call('store', Array)
#4 /home/kitchensisters/kswebsite/archive/application/controllers/helpers/ThemeConfiguration.php(107): Omeka_Storage->store('/tmp/1bc6fdce1a...', 'theme_uploads/1...')
#5 /home/kitchensisters/kswebsite/archive/application/controllers/helpers/ThemeConfiguration.php(51): Omeka_Controller_Action_Helper_ThemeConfiguration->_processFileElement(Object(Zend_Form_Element_File))
#6 /home/kitchensisters/kswebsite/archive/application/controllers/ThemesController.php(79): Omeka_Controller_Action_Helper_ThemeConfiguration->processForm(Object(Omeka_Form_ThemeConfiguration), Array, Array)
#7 /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Controller/Action.php(516): ThemesController->configAction()
#8 /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch('configAction')
#9 /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#10 /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Application/Bootstrap/Bootstrap.php(97): Zend_Controller_Front->dispatch()
#11 /home/kitchensisters/kswebsite/archive/application/libraries/Zend/Application.php(366): Zend_Application_Bootstrap_Bootstrap->run()
#12 /home/kitchensisters/kswebsite/archive/application/libraries/Omeka/Application.php(79): Zend_Application->run()
#13 /home/kitchensisters/kswebsite/archive/admin/index.php(28): Omeka_Application->run()
Was it running correctly before?
An open_basedir restriction that doesn't include places like "/tmp" that Omeka sometimes reads from and writes to (like when uploading files, or when trying to run ImageMagick) will often cause problems.
Is it possible that the open_basedir restriction is what's changed?
I'm not sure I follow entirely. It was running correctly when I was getting the open_basedir restriction warning. It stopped running correctly when I added set_include_path('.'); to bootstrap.php. The warning, however, disappeared.
The reason for my previous post is that the include path really doesn't and shouldn't have any effect on what directories are readable. That's why I guessed that maybe the site wasn't working perfectly before.
But, by all means, if taking out that
set_include_path gets things working again, go for it.
You're totally right. After some experimentation it seems that the problem occurred coincidentally with adding set_include_path('.'). Off to hunt for the real issue.
Update: So, I've included set_include_path('.') again. However, I'm still getting an open_basedir warning for ImageMagick. Is there something else I need to include? Is this a contact your host kind of issue?
Warning: realpath() [function.realpath]: open_basedir restriction in effect. File(/usr/bin) is not within the allowed path(s): (/dh/web/phpmyadmin:/tmp:/usr/local/lib/php:/home/kitchensisters:/home/kitchensisters) in /home/kitchensisters/kswebsite/archive/application/libraries/Omeka/File/Derivative/Image/Creator.php on line 250
Contacting your host would be a good move. If this used to work and just started happening, it's likely your host changed a setting.
It's the "/tmp" folder at least that Omeka needs to be able to work with for ImageMagick, and that's not in the set of allowed paths, it seems.
If you can't get the restriction lifted or loosened, you can make some config.ini changes to change where Omeka temporarily stores and works on files.