I'm running unstable5 but I've tried the dev version and I get the same result. I rebuilt the map after going to the dev. I do not have menu or internationalise enabled but the other are. The duplicates are on normal pages. I get one entry with modification date etc. and one with just the url and priority.

I removed custom module and un-installed but that made no difference.

I included menu module. With all menus set to exclude that removed duplicates and the views leaving just the menu items that were nodes. I then removed the menu module and rebuilt and then sitemap was the same. Hence I think that xmlsitemap remembers the settings of the menu module even if it is removed. I suspect the last time I removed it they were not all set to exclude. I don't know what the default is with menu not installed but it doesn't seem to honour a default.

My guess would be the from the menu the url is content/page but from the node alias you get /content/page hence no match. On the sitemap they are identical urls but that could be a clean up function.

It seems like I need to install menu and custom and then let custom handle the views items off the menu and set menu to disable all. The other menu items being found as nodes.

BTW I have views pages and they don't have modification date etc. either but I guess they wouldn't. Niether do the taxonomy pages but then I use a view for taxonomy too. It would nice if they did have last update date but that would mean running the view I guess.

BTW it might be good to have the option to filter taxonomy page for zero nodes with that term, if that is possible, views does it.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

See #454442: Disable duplicate links during regeneration

malc_b’s picture

malc_b commented

Is this the same as 454442? The start confused me as I didn't have the the errors come up but on reading down I see you disabled that reporting. But I can't see that:

After some debugging chat with mark_r, we discovered that the referenced nodes had missing records in the node_revisions table, which causes the node_load() function to return FALSE since there is an INNER JOIN on node and node_revisions tables. The only solution was to delete the corrupted data from the node table.

applies in my case. This was a clean rebuild on a fresh database. If anything the node might not have a revision table as there are no revisions. New node, copy, paste, save. But I'm sure I have changed some things. It seems consistent that with menu enabled that produces duplicates without a revision date, where as the node produces entries with dates.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

In the other issue I made changes in the code to stop the errors from occurring and just output all the data, even if there are duplicate paths. So in your case where you say you've got two entires, one with a modification date and one without, that's consistent with a node being in a menu, and both the node and the menu item being included in the sitemap.

malc_b’s picture

malc_b commented

OK. I see, I think. This is the behaviour you expect. I assume this is on the list to be fixed? Or are you saying either use the menu module, or the node module, but not both. Unless of course you have a menu that has no nodes on it.