There seems to be something broken in the 1.3 version - sitemap is not displayed (in browser - Firefox) and no error is logged (I can't find anything about in Drupal nor in Apache logs). I've tried to download the generated sitemap.xml file - it is generated, but it seems there is some problem with it...
I've switched back to 1.2, and everything seems to be fine now...
Besides, it would be nice to make the install procedure not to complain about the missing gsitemap tables, if they don't exist (new install or if manually deleted in between, as they are not needed anymore...) - so, to check if they exist first, and to merge records only if there is something to be done... It is not a bug, but I don't feel comfortable to I see some red fields being generated at any stage (besides, some users could even believe something went wrong, even if I believe there shall be no problem in this case...).
Comments
Comment #1
darren ohWe use special files to make the site map viewable. You may not be able to view the site map in your browser if you have changed the files directory after XML Sitemap is installed. Disable and re-enable the module to move the files to the new location. Fixed in CVS commit 88766.
The installation already checks to see if gsitemap exists. If so, it is uninstalled. Errors will be generated if gsitemap cannot be properly uninstalled. This could happen if the gsitemap directory or tables have been removed but gsitemap was not uninstalled. If gsitemap was properly uninstalled prior to installing XML Sitemap, no action is taken.
Comment #2
brianpkennedy commentedperhaps i am doing this wrong but I still only see a gray screen when i go to look at the sitemap. I have disabled and reenabled the module a few times and it still seems to not work.
Comment #3
darren ohGive me the URL so I can see what's wrong.
Comment #4
brianpkennedy commentedthe URL is actually an internally hosted one and is not publicly accessible.
Comment #5
brianpkennedy commentedthe url is an internal one that is not accessible to the public.
Comment #6
hquadrat@hquadr.at commentedI have the same issue here. I just get a gray screen when trying to display the sitemap in my browser...
www.hquadr.at/sitemap.xml
edit: maybe I should mention that I had just updated to the xmlsitemap-module 1.3. Previously I had installed "gsitemap.module" in version 1.10. The old module is deinstalled now. Should I rather have updated to gsitemap.module v1.11 before upgrading to xmlsitemap.module v1.3? (And if, how could I fix this again?)
Comment #7
hquadrat@hquadr.at commentedComment #8
darren ohDisabling and re-enabling the module should fix the problem. If not, you can use the development version until the next official release comes out.
Comment #9
hquadrat@hquadr.at commentedDisabling and re-enabling the module did not fix the problem. not with xmlsitemap v.1.3 nor with the .dev version. But I noticed that in Internet Explorer (v.7) the sitemap is shown, where in firefox I still get a grey screen. So in Internet Explorer I could look at my sitemap again, but I had, except from the taxonomy-terms, links like node/xxx, just as described in #191991.
I then uninstalled xmlsitemap.module (in dev-version now) and installed it again with the result that in firefox i still just get a grey screen; in internet explorer i again get a sitemap displayed, now are (nearly) all nodes with correct paths. In return the taxonomy-paths, at least some of them are now in the format taxonomy/term/xx. Furthermore now are also nodes listed where access is restricted through Taxonomy Access Conrtol (if I remember right, this was not like that before).
However, I think there is something seriously wrong with this module now. (I probably rather should've sticked to gsitemap.module v1.10 - at least that had worked for me more or less...)
Comment #10
brianpkennedy commentedit seems like from my own experience as well as hquadrat, this has not been fixed.
Comment #11
brianpkennedy commentedi think that maybe something is wrong with gss.xsl. if i move the file and then try to view the sitemap, i get a page not found error as expected. Then if I move it back i get a solid gray screen.
Comment #12
luti commentedI managed to resolve this issue not uninstalling (and resinstalling after) the new version, but replace the latest version with the old one (yes, all module files - fortunately I keep the old working versions as a backup...), do a complete uninstall (including all settings, through /admin/build/modules/uninstall), replace the old module files with new ones, and do a clean install as this module has never been installed before).
In between, I took care also that no old tables or variables remained in the database from any old version (so it actually was at the end a fresh installation of this module).
Now it works just fine, even if everything seems to be the same as it was... Weird.
Comment #13
darren ohThere was an error in the code for creating private file URLs. Fixed in CVS commit 90798.
Comment #14
hquadrat@hquadr.at commentedi dont know much about the cvs system yet...
... so if I install the current .dev-version, this issue should be resolved?
If yes, I'll make an update and report back my result... otherwise I'll try LUTi's solution...
ty in advance
Comment #15
darren ohIf you click on the version number in the CVS commit, it takes you to a page where you can download a patch. Here is a direct link:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/xmlsitemap/...
Comment #16
hquadrat@hquadr.at commentedFor me this worked, thank you Darren Oh.
Comment #17
brianpkennedy commentedyes this worked for me as well. Thankyou Darren Oh and hquadrat
Comment #18
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.