AutoTemplatePlugin vs AutoViewTemplatePlugin

Extensions/AutoTemplatePlugin and Extensions/AutoViewTemplatePlugin appear to be very similar in functionality. The later was been updated more recently.

AutoTemplatePlugin checks for the other and advises agains installing both.

You have enabled both AutoTemplatePlugin and AutoViewTemplatePlugin.
Please uninstall one or the other.

AutoViewTemplatePlugin doesn't check.

1. Why are there two of these?
2. Could they be combined?
3. Which is "recommended"?

-- VickiBrown - 29 Mar 2014

See RulebasedViewTemplates for the detailed reasons why.

The essence is: that AutoViewTemplatePlugin is standard core Plugin and AutoTemplatePlugin is a fork with extra features that require configure access to control and could provide site-wide new templates. The community saw risks in making these features part of the standard FW set-up hence it's an optional alternative to AutoViewTemplatePlugin.

I think the documentation of AutoTemplatePlugin should be enhanced to reflect this.

-- JulianLevens - 29 Mar 2014

Commenting is disabled while not logged in