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
post-sitemap.xml shows 'Website experiencing difficulties' error #13317
Comments
Hi @microwpgh, I'm unable to reproduce the issue you've described. Installed:
Went to post-sitemap.xml without any errors or issues. Can you provide additional information like the settings in both plugins and errors from your error logs? Have you eliminated the possibility that it could be any other plugin(s)? |
I have tested on another website and it is working fine too with plugins installed. Can this be related to my Thrive Pressive theme?? |
Possibly, you can switch to the default twentynineteen theme to see if that helps. If not: I think it's best to look for the errors in your logs. |
which logs you are referring to? |
Most probable are your PHP error logs. |
I found this error: |
Any advice? |
Doesn't say much, but it might be a server / configuration related issue. Googling |
Here is the error from WP_DEBUG... |
Can you reply to my recent message? |
It seems that you should increase memory_limit in PHP (try 128M or 256M ). More details - https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/ or try to contact your host. |
It looks like your website is using more memory than the server is allowing, though not an optimal solution, it might be good to increate the memory limit or look for ways to optimize your website. Closing this thread due to inactivity. |
Please give us a description of what happened.
I’ve found that Yoast SEO plugin conflicts with the following 2 plugins causing the post-sitemap.xml to show 'Website experiencing difficulties' error!
The plugins are:
– KK Star Ratings
– Ad Intserter
How can we reproduce this behavior?
Technical info
The text was updated successfully, but these errors were encountered: