I'm getting a timeout error with my migration from phpbb. I've tried to lower the cycle count from 200 to 100 and that allowed the processing to continue to about 13% and it stopped.
What's the proper course of action after receiving a timeout?
- Refresh the page until completion?
- Uninstall/reinstall wpforo, lower the cycle count and run the migration?
- Some other steps?
Hi @michael-tcr,
I think you should reduce the 200 value and make it e.g. 80.
So in address bar fond the &itempercycle=200 and change it to &itempercycle=80 then press F5.
Thanks Sofy! I tried using several other values ... 100, 50, 20, 10 and they each resulted in a timeout. I didn't get a page indicating a successful completion with any attempt. The timeout problem looks to be more indicative of the shared server's resources.
As an FYI, to restore the phpbb database to enable the local connection setup I had to generate a database script that contained one record per insert transaction. The typical multiple records per insert statement generated by a php admin database backup was timing out during post transactions which happen to be about 1M per post. This also points to a resource contstraint my my customer's server.
My real concern was with re-running the migration after modifying the record count per cycle. I didn't want duplicate records to be delivered. There is a prompt just before running the migration that indicated something about duplication ... I can't recall the exact words ... but this was the basis of my concern.
After looking through the wpforo tables this morning... my concerns are realized ... the record counts are reflective of multiple inserts and the wpforo data is not usable in this state.
With the this new information, I have answered my own question ... if a timeout occurs, the wpforo plugin must be uninstalled and re-installed to reinitialize the underlying tables. I suppose I'll have to try a value of "1" in view my server's timeout/resource problem.