I can move that element in our theme.xml in a heartbeat, but is this
"contentType" field now the same as "outputType"? I.e., populate
outputType with what that contentType says once it is moved to the
template-level?
Glen
On 07/19/2014 09:45 AM, Dave wrote:
Hmm... I think that is a bug. The contentType field should be at the page
(or in this case stylesheet) level and not nested inside templateCode.
- Dave
On Sat, Jul 19, 2014 at 9:30 AM, Glen Mazza <glen.ma...@gmail.com> wrote:
OK, outputtype will be retained.
But actually, the contentType is defined in the theme.xml's for the theme:
<!-- stylesheet -->
<stylesheet>
<name>basic-custom.css</name>
<description>Stylesheet for Basic theme</description>
<link>basic-custom.css</link>
<templateCode>
<templateLanguage>velocity</templateLanguage>
<contentType>text/html</contentType>
<contentsFile>basic-custom.css</contentsFile>
<type>standard</type>
</templateCode>
<templateCode>
<templateLanguage>velocity</templateLanguage>
<contentType>text/html</contentType>
<contentsFile>basic-mobile-custom.css</contentsFile>
<type>mobile</type>
</templateCode>
</stylesheet>
Are you sure contentType is of no use? We can remove it... Just FYI,
it's always text/html for our prepackaged themes.
Glen
On 07/19/2014 09:24 AM, Dave wrote:
At this point the UI allows a user to set the content type for a page
template and the PageServlet respects that choice. We do not have a way to
set the content type for each rendition of a page template, and I'm not
sure we really need that feature. So, for now I'd recommend removing
content type from custom_template_rendition, since it is not used.
- Dave
On Sat, Jul 19, 2014 at 9:08 AM, Glen Mazza <glen.ma...@gmail.com> wrote:
But isn't that the contenttype value in custom_template_rendition?
Glen
On 07/19/2014 08:58 AM, Dave wrote:
Please do not remove outputtype either. Page templates can be used to
generate XML, JSON and other types of output and you need to be able to
set
the content-type when you produce those types.
- Dave
