leonstafford
commented
5 years ago Hi @internationils, sorry for the late follow-up.
When there is an error, but it doesn't appear in the Debug Log, there are several possibilities that come to mind:
- resource limits hit on server
- fatal PHP error not caught by plugin
- client-side error, only in the browser
I've noticed that the CSS parser is one of the heaviest parts in the code and as we're ending around some CSS files, it may be failing on one and not telling us it's crawling it before it dies...
The other 2 things I'm seeing that could be a cause:
- WordFence - or security plugins can incorrectly detect all the quick requests made to the server as an attack.
- PHP version. 5.6 is no longer an officially supported release. I'd strongly encourage upgrading to 7.2 or higher. You should also get significant performance improvements from that, too.
I'm going to try and support even older version of PHP purely because I have some users needing WP2Static to archive old sites without being able to upgrade the servers, but 7.2+ should be a beneficial upgrade.
Regarding WordFence, for a WP2Static source site, it should not be necessary. Protecting the site by http basic authentication will be a very good measure to limits bots/malicious attempts.
Please let me know if any of those help to get your export progressing. With the Crawl Increment setting set to 1, it will be a more robust, but very slow crawling process, so if we can sort out this issue, then start increasing that number as high as the server can handle, you should see much faster exports/deploys.
Cheers,
Leon
internationils
Hello, I an FTP-exporting a site, which fails in the FTP export step at around 50%, but there are no errors in the logfile that I can see. Attached is the log. There are files on the destination site, but I'm not sure if its everything. Having different loglevels might be interesting, i.e. for categories such as crawling, exporting, etc. so that the log can be selectively detailed, else it will be huge for large sites.