Errors in mails after upgrading to 1.6.1.5

[metalice]

hi

 

attached is a screen shot of contact us page when clicking send (debug enabled):

 

 

any idea how to fix it?

 

thanks

Matan

[selectshop.at]

Which php-version are you using ? Which swift version is installed on server (ask your provider).

 

Please read also here: https://www.prestashop.com/forums/topic/520374-504-error-after-upgrade-to-1615/?do=findComment&comment=2302676

[selectshop.at]

Please disable also all overrides and non native modules and check if mails are working again.

 

Tab: advanced parameters -> performance -> debug mode = set both options there to YES.

[metalice]

thanks for thr quick reply.

 

ok so i tested, indeed when im activating disable all override its works as always.

 

now, how i can know which override/module causing this issue?

 

thanks

Matan

[Prestachamps]

Hi,

it seems that you have 2 classes in the override folder, that are from the old version of your prestashop, and those are incompatible with new version 1.6.1.5 of prestashop.To fix this errors you should disable those 2 overrides by renaming file /override/classes/Media.php to _Media.php, and renaming file /override/classes/Mail.php to _Mail.php .

Then you must delete the file /cache/class_index.php in order for those 2 overrides to not be loaded on the site.

You should get the new version of the module that uses these 2 overrides, and install the new version of the module that it is compatible with version 1.6.1.5 of prestashop.

Regards, Leo

[selectshop.at]

For to check which module is causing this problem, you should activate non native modules again, and also debug modus. Activating debug modus you will see on top the error line when trying to send a mail.

 

How to activate debug mode: https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/

[metalice]

the screen shot i attached is when debug mode is activated.

but i dont see any sign to module name or something like that..

[metalice]

nevermind guys, i figure which module causing this issue.

 

thanks

Matan