Olafur Posted July 12, 2015 Share Posted July 12, 2015 Can someone help my out here, In my backoffice when I go to module I get this notice shoving up, same notice many times, is that something I have to do to stop this. it come every time I go to module page. Notice på linje 136 i fil /home/styleqaw/public_html/cache/smarty/compile/df/71/f6/df71f64dc24877ab3563b80b21822e7cd561f5dc.file.list.tpl.php[8] Undefined property: stdClass::$price Link to comment Share on other sites More sharing options...
NemoPS Posted July 13, 2015 Share Posted July 13, 2015 Hard to tell where it comes from. First, clear cache multiple times. Then, try to locate that file it mentionscache/smarty/compile/df/71/f6/df71f64dc24877ab3563b80b21822e7cd561f5dc.file.list.tpl.php And look for $price at line 136 (or anywhere else). You have to figure out which module generates it Link to comment Share on other sites More sharing options...
gabdara Posted July 13, 2015 Share Posted July 13, 2015 If you open the file that gives the error (/home/styleqaw/public_html/cache/smarty/compile/df/71/f6/df71f64dc24877ab3563b80b21822e7cd561f5dc.file.list.tpl.php) on the 2 line you'll see the path to the tpl file it was compiled from. Then look into that tpl file to see if you spot something wrong. Link to comment Share on other sites More sharing options...
Daniel - PrestaBR Posted July 13, 2015 Share Posted July 13, 2015 I had this issue in a clean install and this commit helped. https://github.com/PrestaShop/PrestaShop/commit/aaba23728b663b6a6dead34511d25ad65003381d Guess they didn't really solve it, just hidden the module suggestions' prices. The notice disappeared, but I don't have the module prices anymore. 1 Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted July 13, 2015 Share Posted July 13, 2015 nice tip Daniel, my questions to original poster is, if you turn of debug more (recommended unless actively debugging), do you have any issue with features in PS front or back office? i.e. notice does not cause stop of script, so if there is no other issue than the displayed notice, then turn debug off. Link to comment Share on other sites More sharing options...
Olafur Posted July 13, 2015 Author Share Posted July 13, 2015 (edited) Hey, thinks for replay of this issue, this start right after upgrade from 1,6,0 to 1.6.1.0, before everything was fine and it only show up when I go to module in backoffice. Edited July 13, 2015 by Olafur (see edit history) Link to comment Share on other sites More sharing options...
Daniel - PrestaBR Posted July 13, 2015 Share Posted July 13, 2015 I didn't have time to test it extensively (custom modules and functions seems to work right). Just opened a pull request for blockbestsellers.php: https://github.com/PrestaShop/blockbestsellers/pull/5 Of course there are many variables regarding server configuration but, in general, it's working good here. 1 Link to comment Share on other sites More sharing options...
MacRoy Posted July 13, 2015 Share Posted July 13, 2015 Hi! For some reason, PrestaShop has chosen to set debug "ON" by default in PS 1.6.1.0, so just disable it in defines.inc.php and put it in place to define ('_PS_MODE_DEV_', false); Best regards MacRoy Link to comment Share on other sites More sharing options...
Olafur Posted July 18, 2015 Author Share Posted July 18, 2015 Thanks for this, I disable it and now its ok, bud the error or notice is still ther, if I turn debug on again then I get this notice If this is an harmless notice then I just ignore this and turn debug off. Warning på linje 2611 i fil /home/styleqaw/public_html/classes/Tools.php[512] Function <b>getCurrent()</b> is deprecated in <b>/home/styleqaw/public_html/override/classes/controller/AdminController.php</b> on line <b>338</b><br /> Notice på linje 136 i fil /home/styleqaw/public_html/cache/smarty/compile/df/71/f6/df71f64dc24877ab3563b80b21822e7cd561f5dc.file.list.tpl.php[8] Undefined property: stdClass::$price Link to comment Share on other sites More sharing options...
NemoPS Posted July 20, 2015 Share Posted July 20, 2015 That controller is using a deprecated method. It will work for now, but it might not in future versions Link to comment Share on other sites More sharing options...
Recommended Posts