Wrong template directory after update

Permalink
Hi all,

I've started using C5 for the homepage of the organisation where I work. Loving it, but I've run into a weird little problem while trying to customize the autonav using templates. I copied and renamed header_menu.php and edited it to my liking, but I could choose it when selecting custom templates. After a while of troubleshooting I noticed that C5 wasn't looking for the file in /concrete/blocks/autonav/templates as I was expecting, but rather looked for it in /updates/concrete5.4.0.5/concrete/blocks/autonav/templates/

I've searched but haven't found this issue reported. Something must've went wrong with the updates, but no errors were reported. Though I had to manually change config/site.php and remove the old version info. Also, I do not know if this is relevant but I noticed that breadcrumb.php was missing the ending php-tag "?>" and vi reports that both breadcrumb.php and header_menu.php have partial last lines.

Any ideas how I can fix this and make C5 look for the templates in the appropriate dirs?

*edit*
I might add that I've not run into this problem before with any other templates or customizations.

 
Remo replied on at Permalink Best Answer Reply
Remo
No, that's intentionally I think. I'm not really happy about that but I think their approach was an easy "go back option".

A new core is installed in a different directory. After a while you end up having several cores but only the one specified in the config file is used.

This is usually not a problem as you should never ever modify any files within the concrete folder.

You must put these files in the root!

/blocks/autonav/templates/myTemplate.php
Remo replied on at Permalink Reply
Remo
you don't need php end tags..
carlchristophe replied on at Permalink Reply
Ah ok, that makes sense. Thanks a lot!

This website stores cookies on your computer. These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Privacy Policy.