- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: Partial implementations #2: XSLT in Google Search Appliance
There are two things that help debugging at a distance: (1) seeing the code and (2) getting a good error message. In this case, I have neither, so all I can give is general advice:
proxyreload=1in the URL you’re using to test the feed, so that it reloads the XSLT each time you change it<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">— use only spaces, use double quotes around attribute values and definitely don’t have any other attributes on that start tagsystem-property('xsl:vendor')Those were the only problems I encountered. This is no guarantee that there aren’t others.
So if none of those help, cut your stylesheet down to the basics by commenting out code. Comment out all the templates to start with, to make sure that it’s nothing dumb (like attributes in the “wrong” order; who would do that?) and gradually re-introduce the code from there.
Let us know what it was!