Setting the PHP-CLI path in Omeka Classic


#1

Some plugins including CSV Import and Neatline may need to execute code using the command-line version of PHP. If your plugin requires this it can be enabled by editing the file at application/config/config.ini and modifying the background.php.path = “” line to the following:

background.php.path = "/usr/local/bin/php"

Editing files is easy within cPanel by using the File Manager.

Simply navigate to the folder location (application/config within your Omeka directory) and click the file and you’ll have the option for a code editor where you can find the line to edit:


ImageMagick in Omeka Classic
Migrating from Omeka.net to Omeka on Reclaim Hosting
Zotero Plugin to Omeka fails to import items
Zotero Plugin to Omeka fails to import items
Move Omeka files to new installation
#2

Is there a possibility that existing accounts might have been moved to new servers, requiring an update of the path? (I’m trying to track down a glitch in Neatline not pulling in a WMS layer.)


#3

We typically communicate with a user if we’re moving them to a new server. In almost every case the user would know about a server move in advance or as a result if action on a ticket.


#5

When working with Omeka S you’ll need to be aware of the file changes. Omeka S requires that the path be changed within the config/local.config.php file. Change the line ‘phpcli_path’ => null, to ‘phpcli_path’ => ‘/usr/local/bin/php’ (note that if Omeka S is installed via Installatron on Reclaim Hosting this should be set for you already.