Login!
Lost password?
 

MODx Bug/Feature Tracker and Feature Requests

Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!

FS#79 — Move/add 'content type' and 'content disposition' to template

Attached to Project — MODx
Opened by Anonymous Submitter - Sunday, 09 October 2005, 06:12PM
Last edited by Jason Coward (opengeek) - Saturday, 19 May 2007, 11:30AM
Task Type ToDo
Category Core Distribution
Status Closed
Assigned To Jason Coward (opengeek)
Operating System All
Severity Medium
Priority High
Reported Version TP3.2
Due in Version 0.9.7
Due Date Undecided
Percent Complete 100%

Details

See: http://modxcms.com/forums/index.php/topic,1073.msg6757.html#msg6757

It would be a lot easier to be able to set the

- content type and
- content disposition

for a template.

The CSS files I use now have a 'blank' template assigned and have the CSS content type. I'd make more sense if you could simply create and assign a CSS template. Same goes for other content types like eg XML.
This task depends upon

This task blocks these from closing
Closed by  Ryan Thrash (rthrash)
Tuesday, 23 September 2008, 10:48PM
Reason for closing:  Implemented
Additional comments about closing:  Revolution
Comment by Ryan Thrash (rthrash) - Monday, 10 October 2005, 02:34PM
I agree that this makes a lot of sense. I elevated the priority to high.

Comment by Mark Kaplan (mark2005) - Sunday, 20 November 2005, 12:29AM
There might be a better way to handle this.

When selecting a template, if you choose blank, the content type menu appears below it. Otherwise the content type is set by the template.

Comment by Brett (The Man Can!) - Tuesday, 05 December 2006, 02:22AM
Yes, this would be great. (Wow, this is an old task.)

Comment by Jason Coward (opengeek) - Saturday, 19 May 2007, 11:30AM
Yes, this is an old task -- 0.9.7 will solve this using an approach similar to that described by Mark...

The base-level element processed by a modResource will define the final content-type, but you can override this behavior by extending the modResource class. IOW, if a modTemplate is assigned to a resource, it is the "base" content element, and will define the content-type being returned; if no template is assigned, then the content TV, ([*content*] is really just a predefined TV), would be responsible for defining the content-type (i.e. the content-type defined by the resource).