Hide Forgot
Description of problem: Exception due to my content type's .xsl not being found. in my development env I have <projname>/web/static/content-types/<package tree>/<mycontent>.xsl ant deploys this to $CCM_WEB_HOME/webapps/<projname>/static/content-types/<package tree>/<mycontent>.xsl The rest of the content types are in webapps/ROOT/static/content-types/<package name> and if I create a link then the exception disappears Version-Release number of selected component (if applicable): aplaws 2 dec-5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What's happening is that your content type is deployed to its own webapp, whereas (for backwards compat) the other types are deployed in the 'ROOT' webapp. This means you need to add in the '<projname>' as the first component of the path to the XSL. So, what path are you specifying for the XSL filepath in the your initializer ? I suspect you've got /web/static/content-types/<package tree>/<mycontent>.xsl If so, then try changing it to <projname>/web/static/content-types/<package tree>/<mycontent>.xsl
I've actually got /static/content-types/<package tree>/<mycontent>.xsl I'll try your suggestion out. Is this documented in the content-type tutorial and elsewhere?
It works if I use /<projname>/web/static/content-types/<package tree>/<mycontent>.xsl with the leading forward slash.