Jump to content
Rita Ramos

Fatal error: Uncaught Error: Cannot access protected property

Recommended Posts

I updated the PS to version 1.7.7.1, I already had a series of problems but now, I have this one below. Without the debug, I have the error 500. Can someone help me? I´m using PHP 7.3

Fatal error: Uncaught Error: Cannot access protected property Shop::$id_shop in /home/xxxxx/public_html/src/Adapter/EntityMapper.php:101 Stack trace: #0 /home/xxxxx/public_html/classes/ObjectModel.php(264): PrestaShop\PrestaShop\Adapter\EntityMapper->load('1', NULL, Object(Shop), Array, NULL, true) #1 /home/xxxxx/public_html/classes/shop/Shop.php(128): ObjectModelCore->__construct('1', NULL, NULL) #2 /home/xxxxx/public_html/classes/shop/Shop.php(411): ShopCore->__construct('1') #3 /home/xxxxx/public_html/config/config.inc.php(118): ShopCore::initialize() #4 /home/xxxxx/public_html/admin8943a56v4/index.php(40): require('/home/xxxxx/...') #5 {main} thrown in /home/xxxxx/public_html/src/Adapter/EntityMapper.php on line 101

Share this post


Link to post
Share on other sites
3 minutes ago, Daniel Tengler said:

Change php version to 7.2 or 7.1 and  delete  ./var/cache/prod and  ./var/cache/dev folder 

I already did it ... it didn't work.

Share this post


Link to post
Share on other sites
3 minutes ago, Daniel Tengler said:

This looks like a module that is not compatible with Prestashop 1.7.7

If I delete all non-native modules, do I solve the problem?

Share this post


Link to post
Share on other sites
2 minutes ago, Daniel Tengler said:

Just deactivate the modules, you don't have to delete them.

I can't get into the backoffice ... I deleted some modules I didn't use, but the problem continues. Could it be a problem in the new classes of PS 1.7.7.1?

Share this post


Link to post
Share on other sites
1 minute ago, Daniel Tengler said:

I have already experienced that not all files in the Prestashop core are overwritten after the upgrade.

So you know how to solve it?

Share this post


Link to post
Share on other sites

I wrote, not to delete, but to deactivate.
You could have caused an even bigger problem.

There are several possible causes for your problem.
It is not possible to 100% write down what is causing your problem.
I give general advice for the possibility of repair.
Without being able to investigate and fix the problem in person, I can't help but give help.

Share this post


Link to post
Share on other sites
2 minutes ago, Daniel Tengler said:

The programmer or developer needs to look in the error log file.
It can be repaired for a few minutes.

I don't have any knowledge of programming. Until now, I had configured the old version and it worked normally. It was only now that I decided to upgrade that the problem started and I have no idea how to solve it. I need to put the site online because it is undergoing maintenance and I can't even access the back office. Can you help me?

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More