Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the tickets before posting?
Have I read the documentation before posting (which pages?)? No
Joomla! version: (2.5.6)
PHP version: (5.3.13)
MySQL version: (5.1.63)
Host: (Rochen)
Admin Tools version: (free & pro)

Description of my issue:
I have isolated and can repeat steps that uncover an apparent bug. The problem is that a custom template (a variation of the standard component.php in the template directory) will render fine unless I upgrade from Akeeba tools from the free version to the pro version. I did not find the problem if I install the pro version without ever installing the free version - so it appears something left over from the free version is causing the problem.

Symptoms: If I append ?tmpl=component, then I see just the component. If I refer to any other template in that template directory (e.g., component2) and even though that template exists, the resulting display is the full page and not the what I had been seeing from that custom template.

simple Steps to demonstrate and recreate problem...

• Start with a fresh install of Joomla (2.5.6)
• clone the component.php from the site's template directory, rename the clone component2.php and add some text to it so you will know if this template is being called. (e.g., <h1>component 2</h1>)
• view the page ?tmpl=component2 . This should look as expected, proving that you are viewing the cloned template.
• Install the free version of Akeeba Tools. (I installed com_admintools-2.2.0-core.zip) Test the display - I found component2 to still be displaying correctly
• Install the latest pro version. (I installed com_admintools-2.2.10-pro.zip) Test the display. The problem is now viewable. The page displays as if the URL was not including ?tmpl-component2. however, if I return to ?tmpl=component, then all I see is the component.

requested solution
How do I fix a site that has gone through this upgrade and is showing this wrong behavior?

Nickolas,

I found the setting and solution. As you know, the section "Visual Fingerprint Protection" allows me to whitelist which templates can be used for tmpl=. (I didn't think I posted this ticket too early, but after a little more probing, I found that setting that had eluded me. Sorry.)

The strange part, which made me think it was a bug, is that when I installed the Pro version without an upgrade, I was not seeing my custom template being blocked. I still don't know why that is, but the important part for me is that now I have a fix.