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

Error while accessing sitemap.xml #60

Open
worldofsmarty opened this Issue Aug 14, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@worldofsmarty

worldofsmarty commented Aug 14, 2018

Hello,

We have the sitemap plugin installed for a few years now in our website. But recently it started behaving weirdly. The error shown in the below screenshot appears very regularly.
sitemap-error

Once we open the sitemap menu/link from the settings section, we will be able to see the sitemap.xml file correctly. But after some 3 to 4 hours of time again it will display the same error as shown in the first screenshot.

After accessing the sitemap page from the settings section. It will revert back to normal.
image

image

@LukeTowers

This comment has been minimized.

Show comment
Hide comment
@LukeTowers

LukeTowers Aug 15, 2018

Member

@worldofsmarty looks like it might have something to do with your plugins/vdomah/blogviews/Plugin.php line 60. Check to see if that's the issue by disabling the plugin first.

Member

LukeTowers commented Aug 15, 2018

@worldofsmarty looks like it might have something to do with your plugins/vdomah/blogviews/Plugin.php line 60. Check to see if that's the issue by disabling the plugin first.

@kevinvermeulenn

This comment has been minimized.

Show comment
Hide comment
@kevinvermeulenn

kevinvermeulenn Sep 17, 2018

Hi! I have the same issue.
Any update regarding this issue?

kevinvermeulenn commented Sep 17, 2018

Hi! I have the same issue.
Any update regarding this issue?

@LukeTowers

This comment has been minimized.

Show comment
Hide comment
@LukeTowers

LukeTowers Sep 17, 2018

Member

@kevinvermeulenn did you read my comment?

Member

LukeTowers commented Sep 17, 2018

@kevinvermeulenn did you read my comment?

@kevinvermeulenn

This comment has been minimized.

Show comment
Hide comment
@kevinvermeulenn

kevinvermeulenn Sep 17, 2018

@LukeTowers, Yes I did. I’ve disabled the plugin. Unfortunately, it does not work.

kevinvermeulenn commented Sep 17, 2018

@LukeTowers, Yes I did. I’ve disabled the plugin. Unfortunately, it does not work.

@LukeTowers

This comment has been minimized.

Show comment
Hide comment
@LukeTowers

LukeTowers Sep 17, 2018

Member

@kevinvermeulenn you're going to have to be more specific than that. Did you try emptying the cache after disabling the plugin? What error appeared on the screen?

Member

LukeTowers commented Sep 17, 2018

@kevinvermeulenn you're going to have to be more specific than that. Did you try emptying the cache after disabling the plugin? What error appeared on the screen?

@kevinvermeulenn

This comment has been minimized.

Show comment
Hide comment
@kevinvermeulenn

kevinvermeulenn Sep 17, 2018

@LukeTowers

Well, right now. I've disabled the plugin Views and deleted my october and browser cache.
If you see the page: https://www.kvntravel.nl/sitemap.xml, it is not working correctly (see attachment as well).

image

Does this help?

kevinvermeulenn commented Sep 17, 2018

@LukeTowers

Well, right now. I've disabled the plugin Views and deleted my october and browser cache.
If you see the page: https://www.kvntravel.nl/sitemap.xml, it is not working correctly (see attachment as well).

image

Does this help?

@LukeTowers

This comment has been minimized.

Show comment
Hide comment
@LukeTowers

LukeTowers Sep 17, 2018

Member

@kevinvermeulenn yes, I suggest you try reading the error messages instead of panicking :)

The error you're getting is that Class name is not registered for the component "views", and it tells you to "Check the component plugin". One of your pages still has the views component on it which previously would have been provided by the plugin in question, you need to remove that plugin's components from the pages so that the pages aren't trying to load a non-existent component.

Member

LukeTowers commented Sep 17, 2018

@kevinvermeulenn yes, I suggest you try reading the error messages instead of panicking :)

The error you're getting is that Class name is not registered for the component "views", and it tells you to "Check the component plugin". One of your pages still has the views component on it which previously would have been provided by the plugin in question, you need to remove that plugin's components from the pages so that the pages aren't trying to load a non-existent component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment