Closed (fixed)
Project:
XML sitemap
Version:
5.x-1.1
Component:
xmlsitemap_node
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2007 at 19:43 UTC
Updated:
27 Nov 2007 at 20:21 UTC
i upgraded to the latest release 5.x-1.1 and still can't get the sitemap to show aliased paths even when raising the weight of the module.
i also am not seeing any entries in the xmlsitemap_node table. the sitemap is produced however. and there are no errors that i can find in any logs.
shouldn't there be entries in the xmlsitemap_node table? how does the map get produced at all without entries in that table?
is there anything else i should look for for clues as to where this is breaking?
i wondered if anyone new when this feature broke - i would perhaps be willing to go back to an old version where this works and wait for it to be fixed.
Comments
Comment #1
darren ohDid you run update.php?
Comment #2
darren ohFixed in CVS commit 87857.
Comment #3
blb commentedi am still experiencing problems. the xmlsitemap_node table now is populated, but not all the pids are there so the sitemap only has the correct URL for those few nodes with pids. this seems like the same problem that was described in the other thread and marked as fixed.
i was unclear as to whether it is required to change the weight of the module still - with the latest version.
i have done a clean install with the following modules:
Drupal 5.3
CustomError 5.x-1.1
Global Redirect 5.x-1.1
Meta tags 5.x-1.5
Pathauto 5.x-2.0
TinyMCE WYSIWYG Editor 5.x-1.9
Token 5.x-1.9
Update status 5.x-2.0
Upload path 5.x-1.x-dev (2007-Jun-15)
XML Sitemap 5.x-1.2
i had originally installed 5.x-1.1 of xmlsitemap; update.php has been run after the update.
btw, i'm impressed by how responsive you are to the postings here, and how rapidly you have been changing the code to keep up. this is an important module and your work is greatly appreciated.
Comment #4
blb commentedOK, i got it to work by:
adding the weight module and setting the weights of sitemap and node to 5 (it still didn't work at that point); removing the modules, uninstalling, and reinstalling.
i don't know if this depends on setting the weight or not. but new nodes are being added correctly to the map WITH path aliases.
perhaps there is a problem with the update process? or it requires setting weights and reinstalling?
Comment #5
darren ohThis could be caused by SQL error in issue 191723. It is fixed, but there has not been a new release yet. To confirm, disable XML Sitemap: Node, then uninstall it, then enable it again. pids should be present for all existing nodes.
Comment #6
darren ohVery good; the problem is a duplicate of issue 191723; I'm changing the status of this issue back to fixed.
Comment #7
blb commentedit definitely depends on weight being set on the modules at the time that the node is created or edited.
it would be great if there wasn't a dependency on manually setting the weights with another module. AND if old nodes were entered with the correct path aliases without having to re-edit them. maybe the pids should get updated when a new sitemap is generated? or if that were part of the upgrade and install processes.
thanks.
Comment #8
darren ohSetting the module weight is already part of the install process. See xmlsitemap_node.install lines 70-73. Updating old nodes would be the same as uninstalling and reinstalling the module.
Comment #9
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.