flowers_ph Posted December 4, 2020 Share Posted December 4, 2020 (edited) My hosting is going to turn off PHP 5.6 which worried me as my 1.6.1.3 might not work? So i changed it to 7.0... Please an anyone help me find out what this error means and if possible direct me on how to sort out the problem? Thanks in advance Error: PHP Fatal error: Call to protected method LinkCore::getBaseLink() from context '' in Edited December 6, 2020 by bnadauld (see edit history) Link to comment Share on other sites More sharing options...
ClassyDevs Posted December 4, 2020 Share Posted December 4, 2020 Hello, bnadauld You can view this thread many people in the past face this issue . it may help you. Thank you 1 1 Link to comment Share on other sites More sharing options...
flowers_ph Posted December 4, 2020 Author Share Posted December 4, 2020 (edited) Thanks for the help - after a read ...it didnt solve the error but thanks anyway! Edited December 4, 2020 by bnadauld (see edit history) Link to comment Share on other sites More sharing options...
ClassyDevs Posted December 4, 2020 Share Posted December 4, 2020 What PrestaShop version you are using Thank you Link to comment Share on other sites More sharing options...
flowers_ph Posted December 4, 2020 Author Share Posted December 4, 2020 (edited) 1.6.1.3 After rolling back the php version i still get the error (on php 5.6) If i go to the place detailed in the error in the server log file: smarty_internal_templatebase.php(188): I get: $_template->properties['unifunc']($_template); Ive no idea what this is, if it is causing the error that only seems to happen when i navigate around the back office. Edited December 4, 2020 by bnadauld (see edit history) Link to comment Share on other sites More sharing options...
musicmaster Posted December 6, 2020 Share Posted December 6, 2020 DId you also empty the cache after changing the PHP version? Link to comment Share on other sites More sharing options...
flowers_ph Posted December 6, 2020 Author Share Posted December 6, 2020 (edited) Yes - ive cleared the cache. the error is generated every time i move around in the backoffice. If that helps at all? Edited December 6, 2020 by bnadauld (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now