I just installed the xml sitemap module yesterday, but have been unable to get it working correctly. After hours of attempting to figure this out, I am hoping one of you can help.
When attempting to open my sitemap at 'http://www.mysite.com/sitemap.xml', it says the following:
Error loading stylesheet: An unknown error has occured (805303f4)
http://mysite.com/files/xmlsitemap/gss.xsl
It appears to me that the sitemap tries to link this stylesheet (<?xml-stylesheet type="text/xsl" href="http://mysite.com/files/xmlsitemap/gss.xsl" ?>), but it cannot be found. All of the links in the sitemap start out 'http://mysite.com*', but I want them to start out with 'http://www.mysite.com*'. I think that would fix the problem.
My .htaccess contains these lines, if that makes a difference:
RewriteCond %{HTTP_HOST} ^mysite\.com$ [NC]
RewriteRule ^(.*)$ http://www.mysite.com/$1 [L,R=301]
RewriteCond %{DOCUMENT_ROOT}/sites/%{HTTP_HOST}/%{REQUEST_URI} -f
RewriteRule ^(.*)$ sites/%{HTTP_HOST}%{REQUEST_URI} [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
in sitemap.xml:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://mysite.com/files/xmlsitemap/gss.xsl" ?>
http://mysite.com/
always
1.0
http://mysite.com/FooBar
2008-09-24T07:26:20+00:00
etc......
There is also another .htaccess file at http://mysite.com/files/ (in the path to xmlsitemap) with the following lines:
SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options None
Options +FollowSymLinks
Can someone please help?
Thanks!!!
Comments
Comment #1
Anonymous (not verified) commentedIf files/xmlsitemap/gss.xsl doesn't exit the module should use <modules-path>/xmlsitemap/gss/gss.xsl. Did you have a custom gss.xsl file you wanted to use? What PHP version are you using?
Comment #2
avpadernoThere is already an issue report for this.
Version 5.x-1.6 code creates a copy of gss.xsl in the directory files after it changed the path for the JavaScript, and CSS files used by the XML transformation file; in some cases, the module fails doing that, and that is the reason of the error.
There is not much to do, especially now that the code for Drupal 5 is not developed anymore (if I understood correctly).
Comment #3
Anonymous (not verified) commentedWe're not actively improving 5.x but it is still maintained until the Drupal core version 7.x is released.
So the workaround solution is to copy the gss.xsl file from [modules directory]/xmlsitemap/gss/ to [files directory]/xmlsitemap/. @matadon does this work for you?
Comment #4
avpadernoThe path for the referred files is hardcoded; copying the file as suggested should work in most of the cases.
Comment #5
dave reidComment #7
miaoulafrite commentedhi and thanks a lot for the module!
i just got the same message:
Error loading stylesheet: An unknown error has occured (805303f4)
i'm using 6.x-2.0-beta1
i just ran into production, it was working before on localhost and even on production server before i send it to google and other search engines
what is the point here?
okay, i rebuilt the sitemap and it worked. but i still miss what was the point.
Comment #8
lionel.aubert commentedHi,
another way to prevent the 805303f4 error message is :
* go to the XML Site Map configuration page, go to the parameters folder
* uncheck "Include a stylesheet in the sitemaps for humans", save
* rebuild links
Solved ?
Problème résolu ?
--lionel
Note: for the french users, the message is :
"Erreur lors du chargement de la feuille de style : Une erreur inconnue s'est produite (805303f4)"
Comment #9
drup@dev commentedtry to put www in sitemap url something like following...
http://www.mysite.com/?q=sitemap.xml
either put www in both url i.e. http://www.mysite.com/files/xmlsitemap/gss.xsl and http://www.mysite.com/?q=sitemap.xml or remove www from both url.
You can manually remove www from xmlsitemap.module file.
Cheers
Drup@dev
Comment #10
Anonymous (not verified) commentedDrup@dev, it is a bit rude of you to post in an issue that has been closed for 2 years and requires no further information. This is not a discussion forum. This is therefore considered SPAM.
Comment #11
drup@dev commentedYou are not able to decide which one should be in spam...
I was facing same problem but i did not get any solution in comments...
After that i got a solution which resolved my issue and it may be for other that's why i posted it..............