Thread

Hi there,

With EE v2.1.3 Build 20110411 I find that I am able to create a new template without needing to visit the CMS. I can do it simply by placing the new template file in the file system (within the templates/default_site directory). It even allows me to create a new template group in this way. This makes for a very efficient way to develop a site, based on my particular workflow.

I’m working on another site, using EE v2.2.1 Build 20110705. The above technique does not work until I visit the Design > Templates > Template Manager page in the backend. I have to do this each time I create a new template.

Was this a bug in v2.1.3? Or has it been introduced as a bug since? How does the latest build (v2.3.1 - Build: 20111017) behave? Is there a (supported) way to get the v2.1.3 template auto creation behaviour back?

Thanks,

AD

Hi Design by Front,

I just attempted this in 2.3.1 on my test install and it worked as expected. Could you update to the latest version of EE? That should resolve it for you. If it doesn’t please let me know.

Sean

Hi Sean,

I did a fresh install of v2.3.1 to confirm that the issue is resolved by upgrading. I still see the same behaviour. :-( After creating a template file in the file system, it isn’t recognised by EE until I visit the CMS backend (Design > Templates > Template Manager) in my web browser.

Thanks,

Adrian

Hi Adrian,

Since I’m unable to replicate this, I’m going to ask some of the other support staff if they can replicate it or have a solution for you.

Sean

Hi Adrian,

I’m not able to reproduce this either. Be on the lookout for an email from me. It sounds like this might be an issue that only occurs with certain server environments, so I’d like to test it out in yours, if that’s alright.

Thanks!

Hi Kevin,

I have filled in your form and also sent a reply with further details.

Thanks,

Adrian

Just posting a note here to let onlookers know that we’re working with Adrian privately on this for the time being. I’ll post an update back here once we have something to share!

Just to update anyone wondering- those files need to be writable in order for the auto-sync to happen (and in order to edit them via the cp).  After tossing around the value of keeping the writeable check, we decided it should stay a requirement, but we’ll tweak the docs to make sure folks are aware of it.

Thanks for the access, Adrian!  If you run into any other issues, just let us know.