Sorry, execution_time = 300s and db is local (127.0.0.1). No idea why an empty course needed this adjustment and a full course, including all student info, logs that's much larger did not require this tweak (like I said, I think they may have tweaked something else to help moodle get over whatever hump it was under). All other courses backed up without issue.
I realize shared hosting is far less than ideal for Moodle... I know it's resource intensive, but it's such a great platform and I've been using it for a decade... A VPS is just not offered at a pricepoint I can justify at the moment.
I realize shared hosting is far less than ideal for Moodle... I know it's resource intensive, but it's such a great platform and I've been using it for a decade... A VPS is just not offered at a pricepoint I can justify at the moment.