CMS Made Simple Forums

Hello,

I have an issue with a 2.2.2 website upgraded from a freshly installed 2.2.1 site.

I have two page templates(Core::Page) only at the moment, homepage & general. Homepage was created first and then general. From within the Design Manager the template 'general' has been selected as the default from the advanced tab and all looks set correctly.

However, whenever I create a new page the page template defaults to 'homepage' and I cannot find a simple way to resolve the issue. I have to manually change the template every time for a new page.

For me, this happened on the original 2.2.1 & upgraded 2.2.2

Am I doing something wrong or is this a bug?

Thanks,

Mark.

Hi

markS wrote:whenever I create a new page the page template defaults to 'homepage'

Have you tried 'Site Admin -> Settings - Content Manager -> New Page Defaults' ?

I guess a default template (type) is used in the absence of an explicit instruction -- and a page-default is a different kettle of fish.

Hello,


Well I hadn't even found that page in cmsms 2.x! Thanks that's solved my problem.

It does seem a bit counter intuitive that there's a default page template setting there and also one in the design manager. Surely it should be overridden by the setting chosen there.


Oh well, cmsms 2.x not nearly as simple as it used to be.

Regards,

Mark.

markS wrote:It does seem a bit counter intuitive that there's a default page template setting there and also one in the design manager. Surely it should be overridden by the setting chosen there.

Yes, it can look odd coming from 1.* but it's line with the holy grail of Design/Logic/Content separation;

1. Design Manager: Templates are organised by type and if there wasn't a default we wouldn't be able to do things like "{Navigator}" or "{News}".
2. Content Manager: Pages are pages and you can set a default design & template for new items.

markS wrote:Oh well, cmsms 2.x not nearly as simple as it used to be.

I've not found the transition easy and I'm still only starting to get to grips with template inheritance, the nuances of scope (processing order), etc - but I like 2.* in ways that didn't exist with 1.* Great steps.