Thanks for the suggestion. I'd like to try that, but when I go to Design->Templates->/node/view/full.tpl (or any of the templates in the list) I always get an error message like this:
"You don't have permission to access /visual/templateview/node/view/full.tpl on this server."
I presume this is a permissions issue with some part of the file system (I'm obviously logged on as admin), but I haven't been able to work out what to do about it. All the templates in /design/standard/templates/ have permissions of 664 and the folders are 755. Is that what they should have?
I would be grateful for any suggestions on what I should do so I could use the admin interface.
However, how would using the admin interface be different to just directly editing the override.ini.append.php and moving the override blocks around? I did try moving the /node/view/full.tpl down the file one block at a time, but had no luck.
Thanks very much, that fixed the permissions problem, although I also realised that I had the rewrite rule to remove index.php from the admin pages URIs in the Vhosts directive for the admin site. Removing the rewrite rule so that index.php is included in the URI means that I can now use the admin interface to create and edit override templates.
However, I still have my original problem. No matter what priority I give to the override block for the /design/standard/templates/node/view/full.tpl template in the override.ini.append.php file, the override doesn't work. Even if I use an override.ini.append.php file that contains just a single override - i.e. for the full.tpl template - it still doesn't work, and the default full.tpl template from the standard site design is always used. The overrides for the line.tpl all seem to work properly, but none of the overrides for full.tpl.
Well, I found the cause of the problem. It was having this block:
[OverrideSettings]
#Remember to enable this when finished development
Cache=disabled
in the site.ini.append.php file. When I changed it to "enabled", the override of full.tpl worked. This has never given me any problems before in sites developed with ezp3.4.x, so I don't understand why it would now.
Of course, I had to do a complete new plain install, using the installer, and do a whole lot of modifications, before I figured it out. :-( I realised what the cause was when I started copying entries from an old site.ini.append.php file into the new one.
Happy days!
Cheers Iain
You must be logged in to post messages in this topic!
