I am trying to use og_mailinglist on a shared server along with mailgun.

On my site's status report I see:

The Mail_mimeDecode PEAR extension is missing or not installed correctly. Check that the extension is installed and that your PHP include_path is correct. See the INSTALL.txt file for more information at path/to/drupal/sites/all/modules/og_mailinglist/INSTALL.txt.

PEAR seems to be installed on the shared server, as pear config-show gives this:

Auto-discover new Channels auto_discover
Default Channel default_channel pear.php.net
HTTP Proxy Server Address http_proxy
PEAR server [DEPRECATED] master_server pear.php.net
Default Channel Mirror preferred_mirror pear.php.net
Remote Configuration File remote_config
PEAR executables directory bin_dir /usr/local/bin
PEAR documentation directory doc_dir /usr/local/lib/php/docs
PHP extension directory ext_dir /usr/local/lib/php/extensions/no-debug-non-zts-20060613
PEAR directory php_dir /usr/local/lib/php
PEAR Installer cache directory cache_dir /tmp/pear/cache
PEAR configuration file cfg_dir /usr/local/lib/php/cfg
directory
PEAR data directory data_dir /usr/local/lib/php/data
PEAR Installer download download_dir /tmp/pear/download
directory
PHP CLI/CGI binary php_bin /usr/local/bin/php
php.ini location php_ini
--program-prefix passed to php_prefix
PHP's ./configure
--program-suffix passed to php_suffix
PHP's ./configure
PEAR Installer temp directory temp_dir /tmp/pear/temp
PEAR test directory test_dir /usr/local/lib/php/tests
PEAR www files directory www_dir /usr/local/lib/php/www
Cache TimeToLive cache_ttl 3600
Preferred Package State preferred_state stable
Unix file mask umask 2
Debug Log Level verbose 1
PEAR password (for password
maintainers)
Signature Handling Program sig_bin /usr/bin/gpg
Signature Key Directory sig_keydir /usr/local/etc/pearkeys
Signature Key Id sig_keyid
Package Signature Type sig_type gpg
PEAR username (for username
maintainers)
User Configuration File Filename /home/jonathan/.pearrc
System Configuration File Filename /usr/local/etc/pear.conf

I have also tried adding Mail_mimeDecode to sites/all/libraries while using the libraries module, but that also didn't work.

What do I need to do to get PEAR working properly with og_mailinglist?

Thanks.

Comments

jsibley’s picture

I believe I misread the error message. It looks like it is the Mail_mimeDecode extension that isn't being found.

I have installed the libraries module and have tried placing the file in sites/all/library and have also tried placing it in sites/all/library/Mail_mimeDecode. Neither seems to work. Could someone clarify exactly where I should place it?

Also, the shared server is running PHP 5.2.17 if that matters. Thanks for any help.

kyle_mathews’s picture

Status: Active » Fixed

The INSTALL.txt says to put it in og_mailinglist/mimeDecode - http://drupalcode.org/project/og_mailinglist.git/blob_plain/refs/heads/6... Try that.

jsibley’s picture

Could you please clarify what, specifically is supposed to be inside the Mail_mimeDecode folder?

If I go to http://pear.php.net/package/Mail_mimeDecode/download there is a .tgz file that includes Mail_mimeDecode-1.5.5 and package.xml. Are they both supposed to be inside a folder called mail_mimeDecode? Or, am I supposed to rename Mail_mimeDecode-1.5.5 to Mail_mimeDecode and move that folder under og_mailinglist? Do I need package.xml and, if so, where is it supposed to go?

Sorry, but I haven't been able to find clear instructions. So, any help would be greatly appreciated.

kyle_mathews’s picture

You unpack the .tgz file and rename the resulting directory to mimeDecode. The package.xml file is irrelevant and can be discarded or ignored.

Also perhaps helpful, here's the function which loads the mimeDecode library - http://drupalcode.org/project/og_mailinglist.git/blob/refs/heads/6.x-1.x...

The INSTALL.txt file was a bit vague about what you should do so I've updated that.

jsibley’s picture

Title: Drupal cant find PEAR » Drupal cant find PEAR Mail_mimeDecode

I created a folder called mimeDecode in libraries and put mimeDecode.php in that folder. It appears that Drupal can now find it.

Incoming mail is not working properly, but I will create a new issue for that.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.