Red Hat Bugzilla – Bug 108156
Content type Templates don't display properly in Preview
Last modified: 2007-04-18 12:58:49 EDT
Description of problem:
Content types do not display correctly in the preview pane, though they display
correctly on publication.
In preview, only the name & title show up
I think the bug was due to a combination of two factors:
(a) cms-item.xsl did not "/__ccm__/servlet/content-type/index.xsl"
until change 37632.
(b) /__ccm__/servlet/content-type/index.xsl has no effect unless you
use the PatternStylesheetResolver instead of the default
So, if you set
then the preview should work, I think.
is the above the default in tip?
It's not the default. We could try changing the default from
LegacyStylesheetResolver to PatternStylesheetResolver and see
hm, it seems like we should, assuming nothing else breaks, or else get
this to work with the default...
jon, can you switch it and rerun the regressions?
justin, vadim: do you think this is the right solution?
The part I don't understand is, if PatternStylesheetResolver
is backwards compatible with the old stylesheet resolution
process, then what do we need LegacyStylesheetResolver for?
I don't know the answer to this question yet.
See bug 109171
> (b) /__ccm__/servlet/content-type/index.xsl has no effect unless you
> use the PatternStylesheetResolver instead of the default
Actually, I did fix LegacyStylesheetResolver so that it would work
with the ContentTypeXSLServlet correctly - it now generates http://
URLs just like PatternStylesheetResolver. see p4 37488
> The part I don't understand is, if PatternStylesheetResolver
> is backwards compatible with the old stylesheet resolution
> process, then what do we need LegacyStylesheetResolver for?
The pattern stylesheet resolver itself *isn't* backwards compatible
because you have to re-arrange your top level XSL files. The
LegacyStylesheetResolver is the bit that makes the new XSL
infrastructure backwards compatible, with zero change required other
than setting the templating.stylesheet_resolver property.
As such it is intended for any existing projects who haven't migrated
to the new pattern based resolver. THese projects will have set up a
metric ton of PackageType<->Stylesheet and SiteNode<->Stylesheet
mappings in the DB. For them to switch to the pattern based resolver,
they'd have to move / rename all their existing XSL to fit the formal
naming conventions required by the rules in stylesheet-paths.txt.
LegacyStylesheetResolver should be finally removed at the same time
SiteNOde, PackageType & friends are finally removed.
Fixed at 37765. See bug 109171.