-
Notifications
You must be signed in to change notification settings - Fork 264
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
Wwww #906
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before creating an issue / filing a support request
Determining if it's an issue with Theme, Plugin, Environment or a bug in WP2Static
Work down this list until you've identified what kind of issue this is
If the issue is gone - mark this as a Theme related issue
If the issue is gone:
continue to turn back on each plugin, 1 by 1, until you've isolated the offending plugin, mark this as a Plugin related issue
try cloning your site to another environment, such as Lokl (optimised for WP2Static) or use a quick Vultr or Digital Ocean VPS for a few hrs (less than $1 cost)
If the issue is gone, mark this as an Environmental issue
If issue persists after all this, it may still be related to specific content you have or is an issue with the WP2Static plugin, itself. Send a complete set of information with your issue.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Log files (please complete the following information):
Please ensure no sensitive information in your log files, then attach to your issue.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: