-
Notifications
You must be signed in to change notification settings - Fork 4
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
sitemap.xml return 503 when not loggedin #11
Comments
Hey there, I can't reproduce the issue for an anonymous request on any of my test sites. Are you running any other plugins on the site? |
Hi, Here the composer require list :
|
Thanks for the extra info. Could you try uninstalling the plugin and then try to access that url again? Does it still throw the 503? |
Check. Could you try changing your sitemap settings? Maybe try just enabling 1 section (a homepage single or something like that) and see it still crashes? |
Still crash ! |
It's really weird because in SeoFields.php
The $shouldRender condition is met and the rules is add to the listed rules... For an unknown reason, if i'm not connected to CP, the rules do not apply.... |
I reinstalled the plugin on my test install and now I'm having the same issue. Diving in :) |
Not a good news but at least it will be easier for you to find a solution. :) Thank you for the follow up. |
Just published an update that should address this. Could you give it a try and let me know if it works now? |
Thank you so much. Now it work without problems. |
Great! Let me know if you run into anything else, happy to help out :) |
I use the plugin to generate a sitemap for a site.
Everything works correctly when the user is connected to the control panel.
However, if the user is not connected (example a robot), the url returns a 503 - Service unavailable error.
The url used is http://example.com/sitemap.xml
Is there a configuration to put in place to make functional?
Thanks for your help !
Informations:
Craft version : Craft CMS 3.2.9
Plugin version : 1.0.0
The text was updated successfully, but these errors were encountered: