CMS Made Simple Forums

Hi there,

I'm just setting up CMSMS for a client at the moment. The site needs to have two different versions, one for Australia and one for NZ. The default home page will be the Australian home page (although at some stage this may be a generic 'international' home page). Users then select their country and get shown the appropriate content.

After grappling with the logic of it for a while, it really seems that you can't 'share' pages across the heirarchy in CMSMS (or any CMS, really). So I was thinking of setting up a page structure like this:

1. Australian home page
1.1 About Us
1.2 Services
1.3 Contact
2. New Zealand home page
2.1 About us (NZ version)
2.2 Services (NZ version)
2.3 Contact (NZ version)

(there is actually a lot more content than this )

I was thinking I could have two templates, one for Australia and one for NZ. On the Australian template I want to have a menu showing only the Australian pages, likewise for NZ. Does this approach make sense? Ideally, I'd then like to be able to copy content pages within CMSMS, but I think this will be a bit of a task...

Alternatively, I could just have a separate cmsms install for each country.

Any thoughts/suggestions on how to tackle this? Otherwise I'll just trudge through the code snippets in the wiki and try to hack something out.

Thanks

Matt

mattandaniel wrote: After grappling with the logic of it for a while, it really seems that you can't 'share' pages across the heirarchy in CMSMS (or any CMS, really).

If I'm right you can 'share' pages with module ContentAliases. But it works not with current version (also the patch in the tracker) so you have to use version 0.13.

Why not have a structure like this:

1.0 - home page (users select their location)
2.0 - australia section header (not shown in menu)
2.1 - australia home page
2.2 - australia page 2
2.3 - australia page 3
2.4 - australia page 4
3.0 - NZ section header (not shown in menu)
3.1 - NZ home page
3.2 - NZ page 2
3.3 - NZ page 3
3.4 - NZ page 4

then, when viewing the 1.0 home page you can create all the funky links you want (using cms_selflink) to the aussie and NZ home page, but they won't show up in the menus

then on the australia template, you could do a  {cms_module module=menumanager startelement=2.1 show_root_siblings=1} (or something similar to that, I'm not sure if I have the syntax correct),  and the menu will just show the aussie content.

On the  NZ template you could do the same thing, just set the startelement to 3.1

Thanks for your posts, guys.

Calguy - that's exactly the kind of advice I was looking for! Seems I won't have to hack the code after all.

With regards to shared content, I suppose we may just have to wait until the module is updated for the current version.

Thanks again!

Well yeah.... when the content aliases module gets fixed I think that'd do it.  I'd fix it, it's not that hard (I hope) I just don't have time.

In the mean time, you're stuck with GCB's I think.

GCBs?? Not sure what that means 

Global Content Block

you put whatever you want into the text area, then give it a name and call it like {the_name_i_supplied}.  very useful for repeating blobs of html code.

Any idea if/when Content Aliases will be upgraded for the new release? I may be able to offer some small amount of client $$

calguy1000 wrote: Why not have a structure like this:

1.0 - home page (users select their location)
2.0 - australia section header (not shown in menu)
2.1 - australia home page
2.2 - australia page 2
2.3 - australia page 3
2.4 - australia page 4
3.0 - NZ section header (not shown in menu)
3.1 - NZ home page
3.2 - NZ page 2
3.3 - NZ page 3
3.4 - NZ page 4

then, when viewing the 1.0 home page you can create all the funky links you want (using cms_selflink) to the aussie and NZ home page, but they won't show up in the menus

then on the australia template, you could do a  {cms_module module=menumanager startelement=2.1 show_root_siblings=1} (or something similar to that, I'm not sure if I have the syntax correct),  and the menu will just show the aussie content.

On the  NZ template you could do the same thing, just set the startelement to 3.1

Would this work in the following situation?

I want to be able to restrict non members from viewing certain content on my site until they pay the joining fee and have being using the customcontent startup if group = webusers or something like that.

If i was to copy the template and then add the {cms_module module=menumanager startelement=2.1 show_root_siblings=1} to this template and then make all restricted access pages use this template will this work?

I presume startelement=2.1 (the number realtes to the menu numbering system)

What does show_root_siblings=1 (is this how many child entries to display)

Thanks