autoformat plugin no longer found about template2

[abw]

On 11/02/2012 05:22, Vick Khera wrote:

When processing a template which uses the autoformat filter, it fails with the complaint that it cannot find the filter.
[...]
plugin error - autoformat: plugin not found

Hi Vick,

I'm guessing you're on a Mac. The problem is that Apple's HFS file system is case insensitive, so Template::Plugins is trying to load 'Template::Plugin::autoformat' rather than 'Template::Plugin::Autoformat' (capital 'A') and it's succeeding when it should be failing.

The reason this changed between 2.23 and 2.24 is because I removed the explicit entry for 'autoformat' from Template::Plugins, given that it's now no longer in the core.

--- Template-Toolkit-2.23/lib/Template/Plugins.pm
+++ Template-Toolkit-2.24/lib/Template/Plugins.pm
@@ -33,7 +33,6 @@
 our $PLUGIN_BASE = 'Template::Plugin';
 our $STD_PLUGINS = {
     'assert'     => 'Template::Plugin::Assert',
-    'autoformat' => 'Template::Plugin::Autoformat',

I could add the entry back, but that would only be patching over the real problem which exists with all external plugins. I've raised an RT bug to remind me about it.

https://rt.cpan.org/Ticket/Display.html?id=74865

The short-term workaround is to use the correctly capitalised name in the USE directive.

<% USE Autoformat %>

Although you still have to use the lower case variant in the FILTER name.

<% FILTER autoformat %> ... <% END %>

Cheers
Andy

[khera]

Thanks Andy. I am running on FreeBSD. The docs for auto format plugin
still show it lower cased. I will update my use lines and move on to
bigger and better problems. :-)

On Feb 11, 2012, at 4:13 AM, Andy Wardley
[email protected]
wrote:

On 11/02/2012 05:22, Vick Khera wrote:

When processing a template which uses the autoformat filter, it fails with the complaint that it cannot find the filter.
[...]
plugin error - autoformat: plugin not found

Hi Vick,

I'm guessing you're on a Mac. The problem is that Apple's HFS file system is case insensitive, so Template::Plugins is trying to load 'Template::Plugin::autoformat' rather than 'Template::Plugin::Autoformat' (capital 'A') and it's succeeding when it should be failing.

The reason this changed between 2.23 and 2.24 is because I removed the explicit entry for 'autoformat' from Template::Plugins, given that it's now no longer in the core.

--- Template-Toolkit-2.23/lib/Template/Plugins.pm
+++ Template-Toolkit-2.24/lib/Template/Plugins.pm
@@ -33,7 +33,6 @@
our $PLUGIN_BASE = 'Template::Plugin';
our $STD_PLUGINS = {
'assert' => 'Template::Plugin::Assert',

• 'autoformat' => 'Template::Plugin::Autoformat',

I could add the entry back, but that would only be patching over the real problem which exists with all external plugins. I've raised an RT bug to remind me about it.

https://rt.cpan.org/Ticket/Display.html?id=74865

The short-term workaround is to use the correctly capitalised name in the USE directive.

<% USE Autoformat %>

Although you still have to use the lower case variant in the FILTER name.

<% FILTER autoformat %> ... <% END %>

Cheers
Andy

---

Reply to this email directly or view it on GitHub:
#4 (comment)

[atoomic]

@khera worked around the issue