Duplicate entry 'admin/content/taxonomy/%/add/term' for key 1 query: INSERT INTO menu_router (path, load_functions, to_arg_functions, access_callback, access_arguments, page_callback, page_arguments, fit, number_parts, tab_parent, tab_root, title, title_callback, title_arguments, type, block_callback, description, position, weight, file) VALUES ('admin/content/taxonomy/%/add/term', 'a:1:{i:3;s:24:\"taxonomy_vocabulary_load\";}', '', 'user_access', 'a:1:{i:0;s:19:\"administer taxonomy\";}', 'taxonomy_add_term_page', 'a:1:{i:0;i:3;}', 59, 6, 'admin/content/taxonomy/%', 'admin/content/taxonomy/%', 'Add term', 't', '', 128, '', '', '', 0, 'modules/taxonomy/taxonomy.admin.inc') in /home/unitra/htdocs/includes/menu.inc, line 2423.

Someone please tell me why it's happening? I have newest version downloaded today, freshly installed.

BTW Why didn't you carry on with gsitemap module http://drupal.org/project/gsitemap, which was simple and great and made this buggy xmlsitemap pack instead (consisting of 4 modules comparing to 1 in gsitemap)?

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (won't fix)

The error you have received is not caused by xmlsitemap. It does nothing to add entries into {menu_router}, especially relating to the taxonomy paths. A search on drupal.org shows that this is probably Drupal core having problems performing a menu rebuild. See:
#352978: Attempt to insert duplicate entry into menu_router table warnings when editing content types Blog and Forum Post
#246653: Duplicate entry in menu_router: Different symptoms, same issue
http://drupal.org/search/apachesolr_search/Duplicate%20entry%20for%20key...

The reason I understand that the module was transitioned was that the sitemap.org specification was written after the gsitemap module. We're not limited to only dealing with Google anymore. gsitemap didn't have a lot of features that people were requesting, so as far as I understand, the new module was created.
See:
#200309: closing down the gsitemap project
#238427: Port to drupal 6-x

I don't know too much about the specifics of the transition. I've only just started helping to maintain the 6.x-2.x rewrite version since March, which is making good progress to help solve all the bugs and problems of the previous versions. We are all working hard to try and get this out to you. As I pointed out in my 'State of the XML sitemap' blog post, there are several ways for people to help contribute to get this new version out.

dave reid’s picture

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

And as far as having several different modules, they are there so that people can use the different features without having one giant big module that does everything (and loads a large amount of code). If you don't need taxonomy terms in your sitemap, don't enable the xmlsitemap_taxonomy.module. If you only need node links in your sitemap, just enable xmlsitemap.module and xmlsitemap_node.module. Simple as that.

v8powerage’s picture

v8powerage commented

Specification wasn't changed, and gsitemap is still working very good, it was simply doing it's job without hassle. I updated my website only recently from 4.7 to 6 and didn't expect that there'll be so many problems with the module which supposed to be a simple one.

What's the point submitting sitemaps to other search engines than google? What's the point submitting them on cron run anyway, if you have a http://www.google.com/webmasters/tools/ where is the field in which you just need to paste sitemap path (on other search engines there's similar feature as I believe)…

I'm tempted to update good ole gsitemap module by myself, but I'm a themer not a module dev. :(

dave reid’s picture

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

Shaman, thanks for your constructive criticism. Like you, I reached the point where I was very frustrated with the module because it was always buggy and never worked properly for me. Like lots of developers before me, I went to rewrite it myself but instead of keeping it to myself and not contributing back, I've been added as the maintainer of the 'new' 6.x-2.x branch that will solve the performance, scalability problems, and bugs of recent versions. For you what seems like gsitemap doing its job well without hassle, doesn't mean it was working great for others (people with very large sites, 50,000+ nodes, etc.). We are working to address these concerns as best we can.

Please read #448000: Big, Over-Arching Sitemap Architecture Discussion (tm) and http://blog.davereid.net/content/state-of-drupal-xml-sitemap-2009 for all the discussions that have happened about why the module has not been the greatest, and what we are doing to help make it better.

As per your question about Google, my response would be not everyone uses Google. Some people don't know or want to use Google Webmasters, so cron submission works for them. We're simply following the sitemaps.org specification about updating search engines (http://sitemaps.org/protocol.php#submit_ping) and providing the user with the list of search engines that support the protocol and giving the users the choice for what they want to do.

v8powerage’s picture

v8powerage commented

All right, thanks for this explanation, but still at the end of the day this module simply doesn't work for me, (I tried almost all versions of xmlsitemap and with all of the tried ones I had different issues which prompted me from using them).

dave reid’s picture

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

Can I ask if you've tried the 6.x-2.x version yet and if so what didn't work out for you?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

As he opened the report for version 6.x-2.x-dev, I would think he reported the issue against that version because he tried it (differently, he would be a magician, to report an error message without to even try the module :-)).