I’m upgrading an old 3.0.6 install to 3.4.2, there are over 400K user records, and millions of link track records. I’ve manually pruned all click tracking data older than 3 months, and all sent messages (and related data) older than 1 year, but even that still leaves a couple million records.
I’ve removed all relevant server timeouts (php script, sessions, DB connection timeouts, etc). No matter what i try, I cant not get the upgrade to complete. I click to start the upgrade (while watching mysql in another window). When I click to upgrade, I get a blank while page with the browser showing it’s waiting for a response, while at the same time I’m Watching the server and DB logs, I can see the upgrade is starting up fine, and starts stepping through the various queries, and no errors are being logged in the server/db/php/etc (after I removed the relevant timeouts).
From what I can tell, the issue appears to be the web browser itself is killing the process because the queries take so long to run, that by the time a query finally completes the browser already killed the process on the client side because it took so long for the server to respond.
Is there a way to upgrade phplist from CLI to avoid the browser timeout error?
Or is there a way to manually run the upgrade queries from CLI, and if so where can I find the queries that need to be run to go from 3.06 to 3.4.2?
Or, maybe…someone has an idea of something I can do to keep the browser from closing the connection on the client side while the queries complete?