-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new error exporting to github in 6.3 #174
Comments
tried again with a .5 sec delay but same error. |
Thanks @dmeagor. Working on a "Debugging mode" when exporting for easier debugging, but could you please try the following in Advanced Tab:
If that alone doesn't allow the export to complete, please try:
Increase the delay if still not completing. I'm not yet convinced with the change I've done from the old GitHub deploy method (single-commit) to this one, in order to allow for incremental deploys. The advantage of this one is that if you can complete an export, subsequent ones will be much faster. |
Deployment batch size is already set to 1 and api request delay is 0.5 |
Hi @dmeagor, sorry, I read it properly now and see the:
That may be unrelated to the API issue, but is worth looking into. What it means is that the plugin has failed to rewrite a local link on the original site properly. It uses this When I implement the Debugging Mode option, we'll be able to see each action/request logged in order, so in this case, we're failing on a particular file, we'll know exactly which one it failed on. I'm groping in the dark a bit until then, but this hints that it may be trying to send an empty file to the GitHub API: https://stackoverflow.com/questions/21698009/github-api-502-error I can give you a cpl of lines to paste in and get the exact file that's causing it, one minute... |
Using the attached build, once export is done/failed, check the Export Log in the Logs tab and it should end at the failed file when using a Batch Size of 1 |
|
@dmeagor, I've started the Debug Mode work with this build. If you check "Enable Debug Mode" in Advanced Tab, then check/refresh the Export Log, you should see the API responses from GitHub for the Create/Update requests. |
If you're not seeing any hints from those, the 502 may be coming from the other GH API request, which is hitting the GraphQL endpoint to check if a file exists remotely. Anyway, I'll keep expanding the debugging verbosity across the plugin to help with these kind of issues. |
@dmeagor, one more recent version here worth trying. Please let me know what the Debug Mode outputs. |
Hey @leonstafford , I am encountering the same issue with version 6.5.1 This was the error API response code 200 |
Hi @kencanak, Your issue seems a little different, as you're getting a 422 response code with a particular message from GitHub. What I think is happening, is it's expecting a 'sha' value. The plugin, for this file, seems to be trying to do a CREATE, but an existing file was found in the repo and so it needs an UPDATE. Either the deploy cache from a previous deploy is incorrect or changes have been made to the repo outside of the plugin. Please try these steps to troubleshoot:
failing that:
If you can email me the export log at this point, I may be able to deduce what's happening: leon@wp2static.com Cheers, Leon |
Working on this. Delayed due to a different/unrelated issue with our server. I'll send over the log details as soon as I can. |
no worries, @dmeagor, delay was probably a blessing as a few bugfixes went out in the meantime |
Hey @leonstafford , sent the log to you on Tuesday :) |
With the latest build 6.5.3 I am getting a 500 error when uploading to Github.
|
log sent privately. |
Found a workaround by exporting to a static folder and doing git commit/push from the command line. which has reduced the deployment time from about 90 mins to about 4 and is much more secure. Unfortunately relative urls are broken so I'm again at an impasse (listed as a separate issue.) |
2021-03-27 01:01:53 2021-03-26 07:31:53 So what's the issue here? |
2019-01-23 01:10:14
PHP VERSION 7.2.13
OS VERSION Linux ams203.hawkhost.com 2.6.32-896.16.1.lve1.4.49.el6.x86_64 elementor/wp2static#1 SMP Fri Jan 5 05:15:23 EST 2018 x86_64
WP VERSION 5.0.3
WP URL http://xxxx.xxxx.co.uk
WP SITEURL http://xxxx.xxxx.co.uk
WP HOME http://xxxx.xxxx.co.uk
WP ADDRESS http://xxxx.xxxx.co.uk
PLUGIN VERSION 6.3
VIA WP-CLI?
STATIC EXPORT URL https://xxxx.xxxx2.com/
SAVING URL: FILE IS EMPTY /favicon.ico
BAD RESPONSE STATUS (404): http://PLACEHOLDER.wpsho/
BAD RESPONSE STATUS FROM API (502)
Deployment: error encountered
Exception: BAD RESPONSE STATUS FROM API (502) in /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/library/StaticHtmlOutput/SitePublisher.php:312
Stack trace:
#0 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/powerpack/GitHub.php(290): StaticHtmlOutput_SitePublisher->checkForValidResponses(502, Array)
elementor/wp2static#1 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/powerpack/GitHub.php(91): StaticHtmlOutput_GitHub->updateFileInGitHub()
elementor/wp2static#2 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/powerpack/GitHub.php(31): StaticHtmlOutput_GitHub->upload_files()
elementor/wp2static#3 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/powerpack/GitHub.php(352): StaticHtmlOutput_GitHub->__construct()
elementor/wp2static#4 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/library/StaticHtmlOutput/Dispatcher.php(42): require_once('/home/wpstagep/...')
elementor/wp2static#5 /home/wpstagep/xxxx.xxxx.co.uk/wp-content/plugins/static-html-output-plugin/wp2static.php(17): require_once('/home/wpstagep/...')
elementor/wp2static#6 /home/wpstagep/xxxx.xxxx.co.uk/wp-settings.php(322): include_once('/home/wpstagep/...')
elementor/wp2static#7 /home/wpstagep/xxxx.xxxx.co.uk/wp-config.php(86): require_once('/home/wpstagep/...')
elementor/wp2static#8 /home/wpstagep/xxxx.xxxx.co.uk/wp-load.php(37): require_once('/home/wpstagep/...')
elementor/wp2static#9 /home/wpstagep/xxxx.xxxx.co.uk/wp-admin/admin-ajax.php(22): require_once('/home/wpstagep/...')
elementor/wp2static#10 {main}
The text was updated successfully, but these errors were encountered: