Sitekit Forums

Sitekit CMS Help» Sitekit Forums» Developer Discussion» Identifying Localities - perhaps user defined magic words ...

Sitekit Forums

Developer Discussion - Identifying Localities - perhaps user defined magic words ...

Andy Hadley

Andy Hadley

Posted on 26 August 2014

Quote
We have a desire for locality intranets, but actually much of the content they want is common, maybe 80%. At the moment, users are not logging in, so not easily identifying themselves. We would hope that they will adopt the locality page as their homepage, or at least a springboard favourite. I need something akin to a cookie that tells me which locality a user started on, so that I can give them a button to easily return there (one of 13 so an array of buttons wouldn't be very neat). (I have created a directory which passes the locality as a variable as part of the .xsl url, but I can't pass that all around all the sites). Any smart ideas how I can tackle this ? What I want to do is place a button "return to xyz Locality pages" which would appear across all pages on the common section of the site. Perhaps I am after a user definable magic word (or two - cluster is another level to track).

James Delaney

AdminJames Delaney

Posted on 01 September 2014

Hi Andy,

Are you looking at an initial domain/subdomain you'll send them to? If so, you could use a the same Sitekit CMS page accessible via different domains/subdomains. When visitors hit that page from their appropriate page you store the initial domain magic word value as a cookie/web storage (http://www.jstorage.info/ for older IE compatibility), then redirect the user to the appropriate homepage. That stored value could then be retrieved via script and used as necessary to provide the necessary code.

Would that work for you?

James Delaney

AdminJames Delaney

Posted on 01 September 2014

Alternatively, depending on the complexity of the Active Directory set-up, if your Sitekit CMS sites are hosted behind the N3 firewall, you could use some sort of authenticated set-up and identify staff as being within certain groups and use those groups to manage the content displayed to your users (for example display different redirects to different user groups)