Change Details

I've run into this a few times and it happened again today when reviewing a patch for Eileen. When pulling the latest down for CiviCRM and then being told by the dashboard alert model that my database was out of date, I went through the web upgrader process, which looked like it was working fine until I hit the //Max executions Timeout 30 seconds// error. I then clicked what looked like the fast forward / next icon, and it picked up where it left off and seemed to complete successfully. Let's find this stray annoying max execution time setting, which is setting it to 30 seconds locally, and set it to zero so that we don't have to worry about partial upgrades or broken db states when working locally.

I've run into this a few times and it happened again today when reviewing a patch for Eileen. When pulling the latest down for CiviCRM and then being told by the dashboard alert modal that my database was out of date, I went through the web upgrader process, which looked like it was working fine until I hit the //Max executions Timeout 30 seconds// error. I then clicked what looked like the fast forward / next icon, and it picked up where it left off and seemed to complete successfully. Let's find this stray annoying max execution time setting, which is setting it to 30 seconds locally, and set it to zero so that we don't have to worry about partial upgrades or broken db states when working locally.

I've run into this a few times and it happened again today when reviewing a patch for Eileen. When pulling the latest down for CiviCRM and then being told by the dashboard alert modelmodal that my database was out of date, I went through the web upgrader process, which looked like it was working fine until I hit the //Max executions Timeout 30 seconds// error. I then clicked what looked like the fast forward / next icon, and it picked up where it left off and seemed to complete successfully. Let's find this stray annoying max execution time setting, which is setting it to 30 seconds locally, and set it to zero so that we don't have to worry about partial upgrades or broken db states when working locally.