I am using the latest snapshot - download about an hour ago.
I have only enabled nodes. And I went to admin/settings/xmlsitemap/tools and clicked on "continue" and it seemed to have done something (got a processing page 2 items...)

And I also ran cron.php

But I still get no nodes in the ?q=sitemap.xml page - just one entry that shows the root URL.

Is there something else I need to do to get all nodes listed in the sitemap?

Comments

bwooster47’s picture

The empty nodes don't display any error in the logs.

Then I enabled terms, ran update.php, and checked that under tools there is no terms database needed to update.

When I go to load the sitemap page, I now get this error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'GROUP BY t.tid, t.vid, v.module, xt.last_changed, xt.previously_changed, xt.prio' at line 8 query: xmlsitemap_term_xmlsitemap_links /* admin : xmlsitemap_term_xmlsitemap_links */ SELECT t.tid, t.vid, v.module, xt.last_changed, xt.previously_changed, xt.priority_override FROM term_data t LEFT JOIN vocabulary v ON t.vid = v.vid LEFT JOIN xmlsitemap_term xt ON t.tid = xt.tid WHERE (t.vid NOT IN (0) AND xt.priority_override <> -1 AND t.tid <> 0 GROUP BY t.tid, t.vid, v.module, xt.last_changed, xt.previously_changed, xt.priority_override in /.../public_html/cms/sites/all/modules/xmlsitemap/xmlsitemap_term/xmlsitemap_term.module on line 220.

I am using MySQL 5.0.67.

apaderno’s picture

Status: Active » Closed (duplicate)

Actually, xmlsitemap_term.module is a module to which I didn't add the code to update its database table from /admin/xmlsitemap/tools/update because its database table will be changed to just contain the priority of the taxonomy term.

The page to update the database tables of the modules depending from xmlsitemap.module doesn't actually list the modules that need to update their own database tables, but the ones which have support for updating them from /admin/xmlsitemap/tools/update.

I am setting the report like duplicate, because both the issues described have been already reported. Remember to not describe more than one issue per report.

bwooster47’s picture

I am still a bit confused - are the issues reported, but not fixed, or reported and fixed?

It is certainly not working for me - and I used the "Last updated: January 2, 2009 - 00:18" snapshot from 6.x

But the similar issue I found here http://drupal.org/node/351570 is marked fixed.

So I don't know if this is a config problem at my site, or a new issue at this time.

apaderno’s picture

If you are still having the issue, and that report is set like fixed, feel free to change the status of that report to active.