-
Notifications
You must be signed in to change notification settings - Fork 256
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
500 error returned - when generating static site with RankMath plugin activated #824
Labels
Comments
john-shaffer
added a commit
that referenced
this issue
Oct 9, 2021
When creating a Psr7 request with a base_uri set in the Client and a path that starts with // (like '//wp-sitemap.xml'), the path is interpreted as an absolute URL and we get a ClientException for 'unknown host: wp-sitemap.xml'. This is fixed by removing base_uri from the client and always making Requests with the full url. This was discovered while debugging #824 and may address that issue.
Thanks for the detailed report! I was not able to reproduce this issue exactly, but I did find a similar problem that may be related. Can you test with bbc8abb and see if that changes anything for you? |
I encountered this issue with v7.1.7, and I do not have RankMath plugin installed.
Option |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Plugin - Caused unhandled exception
Describe the bug
On a fresh install of WP with WP2Static and RankMath (free) activated, (using the SiteMap options in RankMath), the Generate static site will fail (browser reports a 500 error) and the log file will report an unhandled ClientException.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
WP2Static should not have an unhandled exception that causes the generate to fail.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Linux 0c15ac11f18a 5.10.25-linuxkit #1 SMP Tue Mar 23 09:27:39 UTC 2021 x86_64 GNU/Linux
Log files (please complete the following information):
Please ensure no sensitive information in your log files, then attach to your issue.
The text was updated successfully, but these errors were encountered: