Was the last release of this module packaged wrong?
I was getting an error that the xmlsitemap_flag_sitemap function was not found. I found the function in the xmlsitemap/xmlsitemap/xmlsitemap.module. It seems like the contents of xmlsitemap/xmlsitemap was supposed to go at the root of this module.

I'm not sure about this but when I moved it all I stopped getting this error.

Please let me know.
Thanks!

Comments

Anonymous’s picture

Did you follow the instructions for installation at #379854-128: The site map is not being populated?

There are known issues that have been fixed in CVS that are not in the -dev file yet. Check http://drupal.org/node/190839/release and look for the "Last updated:" data. It will need to be greater than April 29, 2009 - 07:41.

Anonymous’s picture

Status: Active » Postponed (maintainer needs more info)
avpaderno’s picture

Category: bug » support
Status: Postponed (maintainer needs more info) » Active

The content of xmlsitemap/xmlsitemap is not supposed to be moved from where it is.
Moving the content of that directory just causes you problems when updating to a newer release.

I am changing the category, as this is not a bug of the module.

avpaderno’s picture

Status: Active » Postponed (maintainer needs more info)

The usual cross posting issue we should report on the Drupal.org webmasters issue queue. ;-)

Anonymous’s picture

The content of xmlsitemap/xmlsitemap is not supposed to be moved from where it is.
Moving the content of that directory just causes you problems when updating to a newer release.

It may not have been moved. It may have existed there from an older version which is why I came up with #379854-128: The site map is not being populated.

avpaderno’s picture

That is the reason the project page suggests to remove the old files, before to update to the latest version.

Anonymous’s picture

I know it's there but for the case of older version of 6.x-1.x-dev it might not be obvious from the project page that it is needed.

Edited: And for what ever reason my cvs client didn't remove them when I did a cvs update -Pdf either.

avpaderno’s picture

I changed that part in the project page, and I hope it's now clearer.
The project page have a section titled Updating notes, and a sub-section titled Updating to any version, which were present also before; it's not specified that the notes are for who is updating to the same branch.

Anonymous’s picture

The front page looks good we just need to hear from @drfuzetto.

avpaderno’s picture

I guess that we should set as fixed this report.

Anonymous’s picture

Status: Postponed (maintainer needs more info) » Fixed

If there is still an issue please set status to active.

rsvelko’s picture

I've just installed the current stable 6 - beta3 and I received the same error - quite nasty.

rsvelko’s picture

Version: 6.x-1.x-dev » 6.x-1.0-beta3
Component: xmlsitemap.module » Code
Category: support » bug
Priority: Normal » Critical
Status: Fixed » Active

critical cause not installable

Anonymous’s picture

Version: 6.x-1.0-beta3 » 6.x-1.x-dev
Priority: Critical » Normal
Status: Active » Fixed

Try the -dev release. -BETA3 is known buggy. -BETA0 at least works but isn't optimized.

rsvelko’s picture

I apologize - beta3 is ok. There was some kind of problem with a duplicate file/directory ... It was not your fault...

Repeat: beta3 installs ok - I was wrong in #12.

avpaderno’s picture

Category: bug » support

I am changing back the report metadata as they were before.

Status: Fixed » Closed (fixed)

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

GeekElectro’s picture

Version: 6.x-1.x-dev » 6.x-1.0-beta5

Still having the same xmlsitemap_flag_sitemap function missing issue with beta5. Any ideas?

dave reid’s picture

Status: Closed (fixed) » Postponed (maintainer needs more info)

@GeekElectro Can you be more specific about the error? Which file did it come from?

GeekElectro’s picture

I was updating an existing Drupal 6 installation, but there were a few modules installed that were out of date. I wish I knew which file the error came from.

When I kept having errors, I set this issue aside and concentrated on updating other modules. I had an older Theme Settings API in the mix and removed it. It was incompatible with the newer version of Drupal I have installed. That might have been the problem, but I apologize, I just don't know.

Sorry, but I'll have to chalk this one up to a module incompatibility or something.

Thank you for responding anyway.

avpaderno’s picture

Status: Postponed (maintainer needs more info) » Active
Anonymous’s picture

Status: Active » Fixed

With an upgrade from D5 to D6 you must upgrade D6 first without any contrib modules present in the directory structure. Yes, I know this isn't exactly the way it is documented but it is the only method with which I have had success with it.

avpaderno’s picture

I was updating an existing Drupal 6 installation, but there were a few modules installed that were out of date.

It doesn't seem he was updating from D5 to D6, but from D6 to D6.

Status: Fixed » Closed (fixed)

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