The error messages are

* warning: array_splice() [function.array-splice]: The first argument should be an array in /var/www/html/sites/all/modules/xmlsitemap/xmlsitemap.inc on line 290.
* warning: Invalid argument supplied for foreach() in /var/www/html/sites/all/modules/xmlsitemap/xmlsitemap.inc on line 293.

They occur when using the rebuild function, but only when rebuilding the gallery module's map. xmlsitemap, xmlsitemap_menu and xmlsitemap_node rebuild correctly.

Drupal 6.12

XML Sitemap 6.x-2.x-dev (2009-Jun-12)
Gallery module 6.x-1.0
Gallery Program v2.3
Gallery Program's sitemap plugin 1.0.5

Comments

dave reid’s picture

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

Yeah, we need Gallery to update it's implementation of hook_xmlsitemap_links(). It's no longer compatible.

AFowle’s picture

AFowle
he/him
commented

At the risk of cross posting, I have raised this at http://drupal.org/node/490518. However I think the Gallery module development has paused while the maintainer considers the next version of the external gallery program.

dave reid’s picture

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

We the good news is you can simply avoid this for now by not selecting Gallery from the rebuild list.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: bug » support
Status: Active » Fixed

I am changing the category, as the bug is not a XML sitemap bug, but rather a Gallery bug that is taking the assumption the hook used by XML sitemap is the same used in the Drupal 5 version; the version for Drupal 6 is free to use the same hook in a total different way, and until now there isn't a XML sitemap official release for Drupal 6. In absence of an official release of the module, the assumption taken by the maintainer of the other module that the implementation of the hook would not need to be change in the Drupal 6 version is arbitrary.

Taking as example Drupal, there are some hooks used by Drupal core code that required the modules to implement it in a slightly different way, but nobody opened a bug report against Drupal for that (and nobody could).

The report should be considered fixed because it has already received an answer two days ago.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.