If you just upgraded Prestashop to version 1.5, or are trying to make your modules compatible with this new version, you might have run into the cryptic Internal Server Error (500). Let’s see how to make it more understandable in Prestashop.
Watch the screencast
UPDATE – Fixing Paypal error 500 in Prestashop 1.5
I am just out of a hourly struggle with the Paypal module in 1.5. If you happen to get error 500, and can’t solve it in anyway, it’s mostly due to the url. The paypal module uses the following url to perform the payment (express checkout):
And this is BAD, since Prestashop 1.5 uses the following structure:
So, it’s necessary to change the url that points to the first link, into something Presta 1.5 likes, using the second API reference. So! Here is an example if you use express checkout, like the link above.
Go to modules/paypal/views/templates/front/express_checkout/paypal.tpl and change the action of the form with ID paypal_payment_form from
Again, this is for the one page checkout! If you’re using 5 steps checkout, you will need to edit the links in modules/paypal/views/templates/front/paypal.tpl
Now open up modules/paypal/express_checkout/paypal_express_checkout.php. Go to (approximately) line 223 and change this:
$fields['RETURNURL'] = PayPal::getShopDomainSsl(true, true)._MODULE_DIR_.$this->name.'/express_checkout/submit.php';
$fields['RETURNURL'] = PayPal::getShopDomainSsl(true, true)._PS_DIRECTORY_.'index.php?fc=module&module=paypal&controller=expresscheckoutsubmit';
This way, we ensure Paypal returns to the correct page when coming back to the site and confirming the order.
Text version – How to Debug Prestashop Error 500
Error 500 is a nightmare for every developer, because it doesn’t tell you anything at all about what’s going on. It’s more or less like the scary Blank Page.
If you had this error with Prestashop 1.4, it was probably due to some .htaccess misconfiguration when activating friendly urls, or some folders permissions not set to 0755. However, Prestashop was crystal clear about errors if the display_errors setting in config.inc.php was set to true. But now you already did it, and you also turned on ps_debug_sql! Plus, you are not using any htaccess special configuration, and you are whether set the folders permissions to 0755 or running the store on a local environment. So, what’s the catch?
Prestashop 1.5 comes with some new Exception classes, to help the developer have a better tracking of the errors’ source. Howver, what Prestashop doesn’t tell you, since it does not have a decent user manual, is that you have to enable the development mode to take advantage of the new debugging features.
So, just head to config/ and open up defines.inc.php. Then, set _PS_MODE_DEV_ to TRUE as shown below
define('_PS_MODE_DEV_', true); define('_PS_DEBUG_PROFILING_', false); define('_PS_MODE_DEMO_', false);
It should be at line 28.
Now go back to the error page and refresh, you should see something like this (may vary depending of the exception thrown)
In this case, I can now see that a table I’m referencing doesn’t exist.
So, this is everything on how to debug prestashop error 500. Even if you don’t understand a single line of the error above, you might hopefully be able to fix it with your developer (by the way, if you need one, you can hire me!).