NemoPS Posted July 16, 2012 Share Posted July 16, 2012 (edited) Hey there, I'm trying to make my modules compatible with 1.5 rc, the be ready for the full version, but i'm encountering a major problem. For some reason, i get error 500 on most of them when clicking on "configure". I've noticed this seems to be related with the use of protected and private functions with uncommon-given names, like "private $errors" instead of "private $_errors". It prestashop becoming strict on semantics, or is there something else i didn't spot? Fabio Edited July 16, 2012 by Nemo1 (see edit history) Link to comment Share on other sites More sharing options...
Dh42 Posted July 16, 2012 Share Posted July 16, 2012 Do you modules have overrides? Link to comment Share on other sites More sharing options...
NemoPS Posted July 16, 2012 Author Share Posted July 16, 2012 Yes, but i renamed the folder for test purposes, cause it gave me erros (from override to overrides) Link to comment Share on other sites More sharing options...
NemoPS Posted September 14, 2012 Author Share Posted September 14, 2012 Sorry to resummon the topic, but I've noticed the issue seems to be present in the final version, too. There is no error spawn (errors and sql errors are turned on). It just gives error 500! I also tried a module which is not using overrides, and that still doesn't work. Error 500, only that. CRYPTIC! Link to comment Share on other sites More sharing options...
NemoPS Posted September 14, 2012 Author Share Posted September 14, 2012 For some reason, i just noticed that happens if i have debug_sql turned on, and perform some kind of query. at least the sql debugger used to work! This is a BIG step back Prestashop Link to comment Share on other sites More sharing options...
NemoPS Posted September 14, 2012 Author Share Posted September 14, 2012 (edited) Investigating more, i've discovered that what's causing the problems is this piece of code here: if ($sql) throw new PrestaShopDatabaseException($this->getMsgError().'<br /><br /><pre>'.$sql.'</pre>'); throw new PrestaShopDatabaseException($this->getMsgError()); That's triggered in the displayerror method of the Db Class. I'll check that class and let you know at which point it breaks (is anybody has the same issue) p.s. Manually dumping the errors without calling the class works fine THANKS GOODNESS! So, i just discovered i had to turn MODE_DEV in defines.inc.php on to dump errors! Okay, my fault, sorry for that! Great function, thank you! Edited September 14, 2012 by Nemo1 (see edit history) Link to comment Share on other sites More sharing options...
NemoPS Posted September 20, 2012 Author Share Posted September 20, 2012 If anybody is interested, i also recorded a short tutorial about this: http://nemops.com/debug-prestashop-error-500/ I Hope it's useful to someone! Link to comment Share on other sites More sharing options...
Recommended Posts