I have this problem too.
- Memory limit is 1024Mb (exceeds above)
- Upload is 200Mb (under, but I’m not uploading anything, I’m downloading)
- Post max size: 512Mb (meets)
- Execution time: 899 secs (exceeds)
- Input time: 299 secs (CW warns not to go beyond 300 or more)
- Allowed packet: Can’t find this in CW
- InnoDB log: Can’t find this in CW
- Allow URL: Can’t find this in CW
In my previous downloads of .TCO files the largest I’ve managed to make is 2 megabytes, most of them come in at 2k - 99k, hardly a stretch to download.
Why would the Cornerstone export fail to produce a valid file if we’re not getting anywhere near the limits above?
Here’s the console error messages which sound suspicious:
SecurityError: Blocked attempt to use history.replaceState() to change session history URL from about:srcdoc to https://hardy-plant.org.uk/cornerstone/edit/srcdoc. Protocols, domains, ports, usernames, and passwords must match.
And an http error 500 which is a catchall for server errors - back-end code in Cornerstone causing the issue?
This needs more investigation, it was working before and now it’s broken.
Bill.