CiviCRM Community Forums (archive)

Most probably CiviCRM tries to load the Mail_mime class from packages/Mail/mime.php while it’s already loaded by PHP from your platform’s PEAR sources; does this make sense?

You can try skip Mail_mime loading if it’s already loaded by patching packages/Mail/mime.php – you’d need to add

if (!class_exists('Mail_mime')) {

right below the opening <?php and a closing

}

at the end of the file.

Here is the code I modified:

mime.php

---------------

<?php

if (!class_exists('Mail_mime')) {

require_once 'PEAR.php';

require_once 'Mail/mimePart.php';

class Mail_mime
{

    var $_txtbody;

    var $_htmlbody;

    var $_mime;

    var $_multipart;

    var $_html_images = array();

    var $_parts = array();

    var $_build_params = array();

    var $_headers = array();

    var $_eol;


    function Mail_mime($crlf = "\r\n")
    {
        $this->_setEOL($crlf);
        $this->_build_params = array(
                                     'head_encoding' => 'quoted-printable',
                                     'text_encoding' => '7bit',
                                     'html_encoding' => 'quoted-printable',
                                     '7bit_wrap'     => 998,
                                     'html_charset'  => 'ISO-8859-1',
                                     'text_charset'  => 'ISO-8859-1',
                                     'head_charset'  => 'ISO-8859-1'
                                    );
    }

  ............................................. omitted .........................................................

 
    function _setEOL($eol)
    {
        $this->_eol = $eol;
        if (!defined('MAIL_MIME_CRLF')) {
            define('MAIL_MIME_CRLF', $this->_eol, true);
        }
    }

    

} // End of class

} // End of If Clause.


---------------

I hope this was right. Ones I added are in red/bold.

Can you verify?

Thanks.

Thank you.

The patch worked really well.

Blessings!!

(That was a spam post, I deleted the account.)

Hello alfred_nutile

I don't think that was the feature issue, but coding issue.

Depending on the server set up, this can happen. Mine happened because class was already issued, but trying to issue again. This caused the error. So the patch was checking to see if it is already issued, if not it will issue the class. If not, it will ignore. So the patch was working great.