Fatal error: Call to undefined function _xmlsitemap_update() in /blah/blah/blah/sites/all/modules/xmlsitemap/xmlsitemap.module on line 360

I had a problem after updating from 0.x-dev-[2008-06-09] to 1.x-dev-[2008-11-17] when I tried to call on the sitemap.xml file, so I blew the module away (uninstalled it) and re-installed it then received the above error when trying to call on the actual sitemap.xml file.

Might be buggy but keep up the great work on the module! It is by far one of the most important modules to Drupal SEO!!

Comments

ivrh’s picture

ivrh commented

The same issue

ivrh’s picture

ivrh commented
Priority: Normal » Critical

Changing status

jantoine’s picture

jantoine commented

Subscribe

alliax’s picture

alliax commented

subscribe, why did I update this module to the latest version when everything was working fine?

haggaret’s picture

haggaret commented

Same issue here. Anyone know where I can get a copy of the old dev module? :)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (duplicate)

This is a duplicate of #335696: Undefined function _xmlsitemap_update_cache(), which has been fixed.

The 6.x-1.x-dev development snapshot is not ready for production uses. The code is being ported, and changed whenever needed, from 5.x-2.x-dev.

The 6.x-1.x-dev fixes some issues present in 6.x-0.x-dev.

haggaret’s picture

haggaret commented

Back on 6.x-0.x-dev for now. Unfortunately drupal keeps telling me to upgrade, which is how I got into the problem in the first place. :)

casperl’s picture

casperl commented

Yep, same here - subscribing.

IMHO this is a critical module and needs to be in place! I have delayed upgrading Drupal 5.x sites to 6.x for a long time and have only just started developing the first Drupal 6 site. XML Sitemap is a must-have module for SEO!

avpaderno’s picture

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

The issue described here is already described in another report; if you look at that report, you will see that it is already fixed. It's not even necessary to look at it because it's enough to hover the mouse on the link there is in my previous comment.