Tomin Posted January 14, 2014 Share Posted January 14, 2014 (edited) Got some issues with my prestashop After order confirmation I receive blank page. I got this error: Fatal error: Call to undefined method Mail::mimeEncode() in /xxxx/override/classes/Mail.php on line 124 Order has been created, administrator receives email. Customer do no receive confirmation email. After trying cancel these orders in BO, same result - blank page and same error message. Any ideas? Edited January 14, 2014 by Tomin (see edit history) Link to comment Share on other sites More sharing options...
tomerg3 Posted January 14, 2014 Share Posted January 14, 2014 What version of Prestashop are you using? Did you upgrade from an earlier version? Link to comment Share on other sites More sharing options...
Tomin Posted January 14, 2014 Author Share Posted January 14, 2014 (edited) currently I have 1.5.5. Yes, prestashop has been updated from 1.4.x and changed theme to 1.5 compatible. Everything worked fine till now - Now I am changing to new theme and have this issue. Current server configuration: Server informationServer information: Linux #1 SMP Wed Jul 10 05:28:41 EDT 2013 x86_64Server software version: ApachePHP version: 5.4.21Memory limit: 256MMax execution time: 1200 Database information MySQL version: 5.5.34 MySQL engine: InnoDB Tables prefix: ps_ Store informationPrestaShop version: 1.5.5.0 Earlier version of same theme works perfect on PS 1.5.4.1 with this server configuration: Server information Server information: Linux #1 SMP Wed Jul 10 05:28:41 EDT 2013 x86_64 Server software version: nginx/1.5.7 PHP versija: 5.4.21 Memory limit: 256M Max execution time: 1200 Database information MySQL version: 5.5.34 MySQL engine: InnoDB Tables Prefix: ps_ Store informationPrestaShop version: 1.5.4.1 /override/classes/Mail.php file is same on both installations. Theme works fine on different fresh 1.5.x instalations (nginx), so possibly something with apache configuration. Got some smarty related bug today as well, but improvement from github solved it. This bug wasn't before moving to new theme. My hosting says, that it could be some missing Apache library, but they have no idea. Edited January 14, 2014 by Tomin (see edit history) Link to comment Share on other sites More sharing options...
Tomin Posted January 15, 2014 Author Share Posted January 15, 2014 After hours of day time nightmare, possibly i got this working: Existing instalation 1.5.5 upgrade to 1.5.6.1 via 1-click-upgrade (wasn't as smooth as you imagine) Fresh 1.5.6.1 instalation, latest version of theme I need, imported DB via PhpMyAdmin and guess what - HE IS ALIVE. now just image uploading images, translations, setting up theme again etc... Link to comment Share on other sites More sharing options...
Tomin Posted January 15, 2014 Author Share Posted January 15, 2014 (edited) .. Edited January 15, 2014 by Tomin (see edit history) Link to comment Share on other sites More sharing options...
benjamin utterback Posted January 15, 2014 Share Posted January 15, 2014 After hours of day time nightmare, possibly i got this working: Existing instalation 1.5.5 upgrade to 1.5.6.1 via 1-click-upgrade (wasn't as smooth as you imagine) Fresh 1.5.6.1 instalation, latest version of theme I need, imported DB via PhpMyAdmin and guess what - HE IS ALIVE. now just image uploading images, translations, setting up theme again etc... The upgrade didn't work well for you? What was the problem with it that caused you to do a fresh install with DB import? Link to comment Share on other sites More sharing options...
Tomin Posted January 15, 2014 Author Share Posted January 15, 2014 (edited) Upgrade was sucessful.. kinda..but after 1.5.5 upgrade to 1.5.6.1 problem posted in first post still appeared. This was fastest solution as these bugs are quite impossible to solve. it's faster this way Edited January 15, 2014 by Tomin (see edit history) Link to comment Share on other sites More sharing options...
benjamin utterback Posted January 16, 2014 Share Posted January 16, 2014 Upgrade was sucessful.. kinda..but after 1.5.5 upgrade to 1.5.6.1 problem posted in first post still appeared. This was fastest solution as these bugs are quite impossible to solve. it's faster this way Got it, thanks for the clarification. I'll mark it as Solved. Link to comment Share on other sites More sharing options...
Recommended Posts