Hello,
I'm using the latest 5.1.x-1.x-dev (October 19th, 2007), and I noticed since updating, I receive a notice in my watchdog log, that gss.css and gss.js. Specifically, this notices seems to appear after I manually view my sitemap.xml in a web-browser.
Functionality wise, I'm not sure anything actually broke. I know bugs are expected to occur with dev version of modules, but however, I thought I'd note it here, in case someone's willing to look into it.
Thanks
Comments
Comment #1
darren ohIs there a gsitemap directory in your files directory containing gss.xsl? And are the paths to gss.css and gss.js contained in that file correct?
Comment #2
jonli447 commentedYes, there is a gsitemap directory under sites/all/modules. There is a file called gss.xsl, and it's under gsitemap/gss.
The paths, I would think are correct. Here is the relevant code, where gss.xsl and gss.css are called:
There is no other reference to gss.css and gss.js in gss.xsl.
FYI, I looked again in the logs, and the error is definitely happening when I view the sitemap in a web browser.
Comment #3
jonli447 commentedOops, I forgot to add, that gss.css and gss.js reside under the gsitemap/gss. I assume that is the proper location.
Comment #4
darren ohgss.xsl is supposed to be copied to the files directory during installation. This is necessary so that it can be modified to contain the correct location of gss.css and gss.js. Was it copied?
Comment #5
jonli447 commentedHi,
Well, I upgraded from the standard 1.10 to the development version. In files, I do have a directory called gsitemap, however, underneath, I do not have a file called, gss.xsl, but rather a file called "filer58ebQ" (which seems to be gss.xsl, but renamed).
In filer58ebQ, there are the links to gss.css and gss.js, and they have correct paths (/sites/all/modules/gsitemap/gss/gss.css and /sites/all/modules/gsitemap/gss/gss.js respectively).
Comment #6
darren ohFixed in CVS commit 85509. Disable and re-enable the module to fix.
Comment #7
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.