Closed (fixed)
Project:
XML sitemap
Version:
6.x-1.0-beta5
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Apr 2009 at 20:39 UTC
Updated:
22 Jun 2009 at 17:10 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedDid 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.
Comment #2
Anonymous (not verified) commentedComment #3
avpadernoThe 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.
Comment #4
avpadernoThe usual cross posting issue we should report on the Drupal.org webmasters issue queue. ;-)
Comment #5
Anonymous (not verified) commentedIt 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.
Comment #6
avpadernoThat is the reason the project page suggests to remove the old files, before to update to the latest version.
Comment #7
Anonymous (not verified) commentedI 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.
Comment #8
avpadernoI 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.
Comment #9
Anonymous (not verified) commentedThe front page looks good we just need to hear from @drfuzetto.
Comment #10
avpadernoI guess that we should set as fixed this report.
Comment #11
Anonymous (not verified) commentedIf there is still an issue please set status to active.
Comment #12
rsvelko commentedI've just installed the current stable 6 - beta3 and I received the same error - quite nasty.
Comment #13
rsvelko commentedcritical cause not installable
Comment #14
Anonymous (not verified) commentedTry the -dev release. -BETA3 is known buggy. -BETA0 at least works but isn't optimized.
Comment #15
rsvelko commentedI 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.
Comment #16
avpadernoI am changing back the report metadata as they were before.
Comment #18
GeekElectro commentedStill having the same xmlsitemap_flag_sitemap function missing issue with beta5. Any ideas?
Comment #19
dave reid@GeekElectro Can you be more specific about the error? Which file did it come from?
Comment #20
GeekElectro commentedI 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.
Comment #21
avpadernoComment #22
Anonymous (not verified) commentedWith 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.
Comment #23
avpadernoIt doesn't seem he was updating from D5 to D6, but from D6 to D6.