Different suffixes for different content types

Do I interpret item MODX-1223 in JIRA correctly?

Move the FURL alias extension to the respective custom content type definitions:

.html -> text/htm
.xml -> text/xml
.rss -> application/rss+xml
.css -> text/css
.js -> text/javascript

I take it to mean we can expect to be able to use different suffixes with different content types when MODx 1.1.0 arrives?

I was just experimenting with CSS in a resource, so I could upload developing pages (and their associated styles) as site content in the database, instead of having to FTP style files as well, and ran into the same problem as http://modxcms.com/forums/index.php?topic=43166.0

Handling suffixes in the context of the content type just seems like common sense to me - I realy don’t want to mess around with plugins for this kind of thing, it starts to feel like Wordpress...
KP

This is already available in Revolution, MODx 2.0.0.

In Evolution, I recommend not using a suffix and putting them on resources specifically, i.e. alias = alias.ext.

Quote from: OpenGeek at Dec 16, 2009, 11:58 AM

In Evolution, I recommend not using a suffix and putting them on resources specifically, i.e. alias = alias.ext.

This is broken in Evolution 1.0.4: when you save the resource ’alias.ext’ is being transformed into ’aliasext’ as the dot character is forbidden in alias field.
That’s very disappointing as I at least need to give my SEO access to robots.txt and to generate sitemap.xml

Quote from: xEviL at Aug 23, 2010, 04:23 AM

This is broken in Evolution 1.0.4: when you save the resource ’alias.ext’ is being transformed into ’aliasext’ as the dot character is forbidden in alias field.
That’s very disappointing as I at least need to give my SEO access to robots.txt and to generate sitemap.xml

Check you TransAlias plugin options: you can allow or disallow periods with "Remove Periods" configuration option.

Lammikko, thanks for the tip!