Jump to content

Edit History

w3bsolutions

w3bsolutions


Attach override.

10 minutes ago, Vidar Bjerkeland said:

Thank you for advise, however SiteGround does not allow to open the 1-click upgrade module from the admin section of PrestaShop. It was possible to open 1-click upgrade prior to  module vers.. v4.13.0 - by PrestaShop, but with this version, not possible. Getting a HTTP 500 ERROR at once.

I had this issue also with one shop, where I couldn't open the autoupgrade config page directly, I was already getting the "too many open files" (500 error) directly. I did some debugging and it turns out when you open the page it runs some tests on your installation. Some of these tests just check if directories are writable, and specifically one of the tests checks if each directory in the /img directory is writable... recursively. This shop had several thousand images (more than 4096) and it was breaking there. So I created an override to disable the recursively in this test, and then I could open the autoupgrade configuration page fine. 

Attached is the override. If you want to test it, just place it under /override/classes. Note that in this shop this test was the problematic one, but there are other tests it is running that are also still using recursivity on nested directories, so they could also give problems. You can see which ones exactly in /classes/ConfigurationTest.php. All the tests in there are executed when you open the autoupgrade configuration page. 

P.S. It is giving an error when uploading the PHP override, so I just put it in a zip to overcome this.

ConfigurationTest.php.zip

w3bsolutions

w3bsolutions

1 minute ago, Vidar Bjerkeland said:

Thank you for advise, however SiteGround does not allow to open the 1-click upgrade module from the admin section of PrestaShop. It was possible to open 1-click upgrade prior to  module vers.. v4.13.0 - by PrestaShop, but with this version, not possible. Getting a HTTP 500 ERROR at once.

I had this issue also with one shop, where I couldn't open the autoupgrade config page directly, I was already getting the "too many open files" (500 error) directly. I did some debugging and it turns out when you open the page it runs some tests on your installation. Some of these tests just check if directories are writable, and specifically one of the tests checks if each directory in the /img directory is writable... recursively. This shop had several thousand images (more than 4096) and it was breaking there. So I created an override to disable the recursively in this test, and then I could open the autoupgrade configuration page fine. 

Attached is the override. If you want to test it, just place it under /override/classes. Note that in this shop this test was the problematic one, but there are other tests it is running that are also still using recursivity on nested directories, so they could also give problems. You can see which ones exactly in /classes/ConfigurationTest.php. All the tests in there are executed when you open the autoupgrade configuration page. 

×
×
  • Create New...