U4-86 - Move EXSLT references from being predefined in core to xsltExtensions.config

Created by Lee Kelleher 27 Jun 2012, 15:06:51 Updated by Lee Kelleher 23 Aug 2012, 19:06:30

Subtask of: U4-136

[Copied over from CodePlex work item: 27035|http://umbraco.codeplex.com/workitem/27035]

Since Umbraco v3 the EXSLT extension have been part of the core (see [CodePlex work item: 5238|http://umbraco.codeplex.com/workitem/5238]).

During my 4+ years of Umbraco and heavy XSLT development, I have found that I very rarely use any of the EXSLT functionality, but since the libraries are referenced as "predefined extensions" in the core, they are loaded into each and every instance of an XSLT-based macro.

From looking at the debug/trace, adding XsltExtensions have minimal overhead, but since I don't use the EXSLT libraries, it seems redundant to load them; (via {{umbraco.macro.GetPredefinedXsltExtensions}}).

My suggestion is to move the EXSLT references from being "predefined extensions" in the core and place them into the {{\config\xsltExtensions.config}} file. This way they will still be available as default, but provides a developer with a way to disable/remove them from an install.

Example of the default {{\config\xsltExtensions.config}} would be:


Lee Kelleher 23 Aug 2012, 18:57:00

Implemented in changeset: [75e087c7d893|http://umbraco.codeplex.com/SourceControl/changeset/75e087c7d893]

Priority: Normal

Type: Feature (request)

State: Fixed

Assignee: Lee Kelleher

Difficulty: Normal

Category: Extensibility

Backwards Compatible: False

Fix Submitted:

Affected versions: 4.8.0, 4.9.0

Due in version: 4.9.0


Story Points: