David, thanks.
I finally found what needed to be tweaked based on my last reply to you regarding the timeout error I found in Chrome’s developer console.
After about a minute the Plugins count the activity timed out and threw the error. I use Plesk instead of CPanel to manage my server and in the PHP Settings was FastCGI settings. I incrementally bumped up the activityTimeout to 120, 180, 240, 300 seconds. When I reached 240 seconds your plugin worked. I added another 60 secs as a buffer.
I had previously bumped up the Performance and security settings max_execution_time to 120 seconds and left it alone.
So now it is consistently working.
FastCGI settings
activityTimeout = 300 secs (70 default)
Performance and security settings
max_execution_time = 120 secs (60 default)
****************************************
max_execution_time int
This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The default setting is 30. When running PHP from the command line the default setting is 0.
On non Windows systems, the maximum execution time is not affected by system calls, stream operations etc. Please see the set_time_limit() function for more details.
Your web server can have other timeout configurations that may also interrupt PHP execution. Apache has a Timeout directive and IIS has a CGI timeout function. Both default to 300 seconds. See your web server documentation for specific details.
****************************************
That last paragraph under help for max_execution_time mentioned the Windows IIS CGI timeout. The default for the activityTimeout said and was set for 60 secs. Even though my incremental bumps up to 240 seconds worked, as I previously said I bumped it up to 300 secs as a buffer, ironically it says the default is 300 secs.
~Richard
