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 errors after upgrading to 3.3.x #478

Open
peakpg opened this Issue Feb 13, 2012 · 0 comments

Comments

Projects
None yet
1 participant
@peakpg
Collaborator

peakpg commented Feb 13, 2012

This is caused by left over section nodes that didn't have a matching section object in the sections table. The workaround is to run the following query to join sections and section_nodes.

SELECT * FROM section_nodes left  join sections on section_nodes.node_id = sections.id WHERE section_nodes.node_type = "Section"

Any NULL sections means the section node can be safely deleted. So long as every section node has a matching section, the sitemap should work.

Root Cause

At this point, its not know what caused the section nodes to be orphan'd. It's possible an older version of BrowserCMS didn't correctly delete both rows when deleting a section. However, that doesn't seem to be an issue anymore, so this should probably only occur during this upgrade.

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