Hi there @mikesouth –
I looked through the support tickets and didn’t see where you had put a support request in, so I can only go by what you’ve included in your review above.
We have many users who successfully use our plugin to backup sites 12 GB and even larger. The limitations on some hosts make this difficult, but if a user has server access and is able to edit their own php.ini settings and sometimes additional settings, many times we can get the backups running successfully. Unfortunately some shared hosting environments will be limited, either via CPU or I/o usage or with hard limits on their memory_limit or max_execution_time variables.
Large site can successfully use our plugin, as can professional WordPress users and those with larger publications and eCommerce sites. It’s even been used successfully on Enterprise-level installations with tweaks to the settings mentioned above.
If you’ve had trouble and would like to troubleshoot further, I’m happy to do so with you. If your hosting environment is limited and you’ve exhausted the changes you can make to the server, I understand and I’m sorry you didn’t find the plugin could meet your needs.
I definitely wish that the plugin (every plugin, actually!) could work under any circumstances, but unfortunately with so many hosts, hosting plans, and different server environments, it’s very difficult to meet the needs of every single site.
Again, I’m sorry the plugin didn’t meet your needs.
Kat
you have a bug that hardcodes an error after 300 seconds no matter what the settingss are I confirmed this with my hosting company after they raised the limit to 2600 seconds….
a different plugin worked fine.
Again, I’m sorry you experienced issues with the plugin.
We don’t hardcode any kind of error after any number of seconds; we only report errors experienced when we either run into server limits, or when a function/command isn’t installed or installed incorrectly. So if you ran into an error after 300 seconds it wasn’t due to our plugin. When your hosting company raised the limit (which limit?) to 2600 seconds, they would be changing one of the php.ini settings which are set at the server level.
If you have further information on why you think this might be due to our plugin, please let us know as that isn’t intended as part of our code.
Again, I’m sorry our plugin didn’t fit your needs. I’m glad you found a solution that did meet your server needs and wish you the best moving forward.
Kat
Argue with me all you like but you have a problem, after raising the hph time limit server wide you still reported the 300 second error my hosting company suggested I try a different plugin, I did and it worked fine, just to be sure we lowered the limit and tried the plugin again, it timed out with the lower limit. Yours didnt work either way timing out regardless.
When so many people have the exact same problem the answer usually isn’t y’all are doing it wrong, it’s usually sorry we f’ed up.
sorry you f’ed up
deal with it
