When I install new version of module data isn't updated in any case: old entity, updated entity, new entity. I have one record in my sitemap.xml for root catalogue.
The most of nodes have settings by default (0.5).
Can you explain me why it happens please? I have successful practise with previous version already, but may be in this version was added new features?
Comments
Comment #1
wdrupal100 commentedi also experience an all but empty sitemap.xml file. it only contains the root / node
Comment #2
lammertsm commentedMy sitemap.xml is empty after the upgrade.
Comment #3
avpadernoComment #4
eagereyes commentedI also consider this critical, but anyway ;) Subscribing.
Comment #5
luti commentedIt shall be critical - isn't it all about exactly this? What would be the benefit of a map without the content? ;-)
Comment #6
marcus0263 commentedYep, same here. There's only one record in the sitemap, everything else is gone
Comment #7
avpadernoI am not sure if critical is the right priority, checking the description of the priorities I find following the links showed in the issue pages. That is not the most important thing, at the moment; the most important thing is that there is the issue.
Actually, the code is being re-written, and the tarball you download from the nightly development snapshot can contain incomplete code. As there are more people working on the project (we should be in 4, but it doesn't change even if we are only in 2), I prefer to submit code to the development snapshot even if I didn't rewrite it completely); in this way the code in CVS is updated at the last changes I made, and the maintainer can start to work from what I changed). That is the purpose of the nightly development snapshots, IMHO.
So far, I changed the code for xmlsitemap.module; the next module will be xmlsitemap_node.module which is the module which puts node data in the site map.
Comment #8
DAuBeP commentedI think it is meaning the module dosen't exist for site if this functionality dosen't work.
I hope for output tarball with new version ASAP.
Comment #9
drewschmaltz commentedHey!
Developers, you guys don't get enough THANKS A BILLION!!! I'm absolutely sick of inconsiderate people demanding these modules!
I'm so glad that someone is dusting off this module and giving it some attention. I think (as great as the module was) it always just "got by", but continues to be very important to SEO.
Saying this, I was fooled by a new release and had a good amount of headache re-implementing the older version. While each may have their own idea of what a nightly snapshot or development version may be - for the longest time the .dev has been considered a working version, the change could have been better documented.
Comment #10
andypostsubscribe
Comment #11
dbeall commentedYou take all the time you need or want to make the mod do it's thing...we will love having it and most everyone really appreciates the work you are doing with it. It will be a welcome addition to D6.
Some folks forget that a module labeled .dev is in 'flux' or 'not for production', usually because it is not ready and may very well not work as expected.
thanks so much !
dave
Comment #12
avpadernoComment #13
fellow commentedi also have this problem. Subscribe
Comment #14
SimonVlc commentedSame here. Subscribing.
Comment #15
fpainchaud commentedsubscribe
Number of site maps in this index: 0
Number of site maps in this index: 1
Comment #16
avpadernoComment #17
andypostI've checkout CVS version - bug still there but now gss.php erroneous (parse error)
To reproduce just open http://example.com/sitemap.xml
Comment #18
matb commentedworks for me, thx!
Comment #19
eagereyes commentedWorks for me, too! Thank you!
Comment #20
andypost@matb what version are you using? I've tried latest cvs DRUPAL-6--1
Comment #21
avpadernoThe issue as been fixed. I tested the code which now works. To be sure you have the right version, open CHANGELOG.txt, and check if there is a line saying Ported xmlsitemap_node from 5.x-2.x-dev.; if you don't such a line, then you don't have the right version.
I will submit a change to xmlsitemap.install to be sure that sitemap.xml doesn't get the content from Drupal cache; in that way there would not be false reports about the sitemap being still broken.
Comment #22
avpadernoAn issue should be set to postponed only by the mainteiners. Please don't touch anything you don't really need, to avoid confusion.
Comment #23
andypostProblem caused by \n before <?xml in gss.php
patch just removes empty line 2
Comment #24
andypostTested on FF3 and Opera 9.62
Comment #25
avpadernoIn my file I don't see any empty line after
<?php /* $Id: gss.php,v 1.1.4.3 2008/11/17 19:00:30 kiam Exp $ */ ?>.To be sure the first PHP comment doesn't cause any problem, I moved it to the last line of the file.
Comment #26
andypostSuppose it depends on editor
Attached image - left side was and right side now (last cvs checkout)
Comment #27
lammertsm commentedWorksfine now.