whoey

Yes, I prematurely celebrated it working with a cloned setup of our live site on the same host. The live site still had the error after upgrade. Had to manually roll back to our last working setup (1.7.0.6) by extracting the site backup and manually restoring the DB using phpmyadmin since the 1-click disaster failed to restore.

worked on cloned site, but not live site.

For us our php was configured with Max execution time: 30, changed to 90 and the problem is gone.

Unbelievably, it's a simple solution. Our php was configured with Max execution time: 30, changed to 90 and the problem is gone. Hope this helps someone...

This looks like an error that happened with an older version of the 1-click upgrader. There are plenty of examples on the forums. Try updating the 1-click module first?

It's comforting to know that we're not alone with the issue. Sad that it does not seem it will be addressed by PS folks especially since there has been 4 releases (v1.7.1.0, v1.7.1.1, v1.7.1.2, v1.7.2.0) and it still persists. I think v1.7.1.0 is the only one I didn't try on a test setup... I might do that now and see if I can make any progress. Also there was some issues with the 1-click upgrader versions in between which may have been partially responsible for this issue. Too bad the devs don't seem to pay any attention to the forums. I was looking at setting up another shop using 1.7.x but it seems that many of the affiliated modules haven't all caught up yet, and that whole deal has been a huge fiasco with 1.7.x imho starting with the time it took for paypal to be implemented without a paid 3rd party module. In retrospect I wish we had gone with 1.6.x when we setup the new shop, but at the time we tested both and the client felt more comfortable in 1.7. After some time running it and seeing so many bugs and issues it feels very alpha rather than stable, I really don't think they should be pushing 1.7 yet on new users especially if upgrading is so hit and miss.

What about php versions? we're running php5.6 which well surpasses the minimal requirement of 5.4 from the documentation: http://doc.prestashop.com/display/PS17/What+you+need+to+get+started#Whatyouneedtogetstarted-Technicalrequirements And yet we still get the same 500 error when adding or editing products if we upgrade prestashop past 1.7.0.6

We also get this error after any upgrades past 1.7.0.6 (but not with 1.7.0.6), only when trying to add or edit a product. Does not happen in debug mode. PHP version: 5.6.30

and finally the error from the logs related: PHP Fatal error: Class 'PrestaShopBundle\\Entity\\AttributeRepository' not found in /var/www/domain.com/htdocs/prestashop/vendor/doctrine/orm/lib/Doctrine/ORM/Repository/DefaultRepositoryFactory.php on line 68, referer: https://domain.com/prestashop/index.php/product/catalog?_token=

Some time to play around with this, so I tried again by removing the 1-click upgrade module in prestashop 1.7.0.6, reinstalling via the module addons marketplace (which installs 1-click upgrade 2.1.0) and upgrading to prestashop 1.7.2.0. After upgrade the 1-click upgrade module can be updated to 3.0.2 (all of this was done on a clone of our live install to not have any downtime) No errors on upgrade. 1.7.2.0 works fine with the exception if I try to edit or add a new product I get the 500 error. Enabling debug mode allows products to be added or edited without error. PHP version: 5.6.30 Memory limit: 400M MySQL version: 5.6.35

We are running 1.7.0.6 and get 500 errors when adding/editing products after trying to upgrade to newer versions. if you enable debug mode can you then add/edit products?

I have just done a test with 1.7.2.0 (from 1.7.0.6) and this still persists. Rather annoying since 1.7.0.6 has a display bug with product variant that is causing us a bunch of headaches, and obviously running the site in debug mode to add or edit products is also not a solution.

ese archivo no es parte de prestashop... seria algo de tu alojamiento?

1.7.0.6 > 1.7.1.2 on test duplicate setup (sub directory/copy of live site/database) worked fine, upgrade live site and same problem adding new products get a 500 error, unless debug mode is enabled.

I'm not sure if this is the case for you, but on our 1.7.0.6 if we install the 1-click upgrade module via the backend module shop we end up with v2.1.0, and if we download the one off the addons website it changes to v3.0.0 (although on the modules page it still says 2.1 but if you go into configure it shows as v3.0.0 in the checkup ) This solved an issue we had upgrading previously, but there are others we've encountered that prevent us from migrating our live setup.