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.x2.1.x2.2.x2.3.x2.4.x2.5.x2.6.x2.7.0
No1.4.01.4.01.5.01.6.31.6.31.6.31.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

  1. Enable the extension
  2. Add content type mappings via the preferences page
  3. 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

Symphony 2.1.0 to 2.2.5

  • Added the preferences UI section;
  • Updated the compatibility array, since this extensions works with 2.1.0 to 2.2.5