[TYPO3-core] RFC #16027: Let typolink honour secure filelink configuration

[Stanislas Rolland]

Re-generated the patch against current trunk because 
class.tslib_content.php has changed a lot.

Stanislas


Le 2010-10-16 22:53, Stanislas Rolland a écrit :
> Hi,
>
> This is a SVN patch request.
>
> Branches: trunk
>
> Type: feature
>
> BT reference: http://bugs.typo3.org/view.php?id=16027
>
> Problem:
> filelink may be configured to be rendered as secure file download link.
> Not so with typolinks in general when they are links to internal files.
>
> Solution:
> The attached patch makes typolink honour the following configuration:
> typolink.jumpurl =1
> typolink.jumpurl.secure =1
> typolink.jumpurl.secure.mimeTypes = list of mimetypes, syntax [ext] =
> [mimetype]
>
> With such configuration, typolink will be rendered as secure download
> link whenever the link is to an internal file.
>
> How to test:
> For example, assuming CSS Styled Content is installed and assuming that
> DAM is either not installed or not integrated with RTE, the following
> settings in TS template will make any link to an internal file inserted
> in the RTE be rendered as a secure file download:
> lib.parseFunc_RTE.tags.link.typolink.jumpurl = 1
> lib.parseFunc_RTE.tags.link.typolink.jumpurl {
> secure = 1
> secure.mimeTypes = pdf=application/pdf, doc=application/msword,
> png=image/png, gif=image/gif, jpg=image/jpg
> }
>
> Note:
> This will require update to TSRef and follow-up patch to DAM to render
> similarly the media tag.
>
> Kind regards,
> Stanislas

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: typo3core_feature_16027.patch
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20101112/3bf88f6f/attachment.asc>