1.6.3releasedContent Type Mappings
Configure additional page MIME types
Clone URLhttps://github.com/symphonists/content_type_mappings.git
Add as a submodulegit submodule add https://github.com/symphonists/content_type_mappings.git extensions/content_type_mappings --recursive
Compatibility
2.x.x | 2.1.x | 2.2.x | 2.3.x | 2.4.x | 2.5.x | 2.6.x | 2.7.0 | 2.7.1 | 2.7.2 | 2.7.3 | 2.7.4 | 2.7.5 | 2.7.6 | 2.7.7 | 2.7.8 | 2.7.9 | 2.7.10 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
No | 1.4.0 | 1.4.0 | 1.5.0 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 | 1.6.3 |
Readme
Content Type Mappings
Allows more control over frontend page content type mappings. Each mapping is stored in the Symphony configuration file, and page type is matched against these mappings.
Installation
- Enable the extension
- Add content type mappings via the preferences page
- If a page uses a type listed in the config, that appropriate content type will be set. Should more than one match be found, the last one encountered will be used.
Content disposition
To force download of a page (by setting the Content-Disposition
header), give it a page type that begins with a '.'. The page will be downloaded with a filename = $page-handle.$type
. For instance, a page with handle form-data
and a page type of .csv
will be downloaded as form-data.csv
.
Depending on the Content Type you map to a page type, it may not be necessary to add this Content-Disposition header in order to cause the page to download.
Version history
Symphony 2.4 to 2.x.x
- Fix wrong github link
Symphony 2.4 to 2.x.x
- Updated compatibility info
Requires Symphony 2.4
- Code clean-up
Requires Symphony 2.4
- Symphony 2.4 compatibility
Requires Symphony 2.3
- Symphony 2.3 compatibility
- Added the preferences UI section;
- Updated the compatibility array, since this extensions works with 2.1.0 to 2.2.5