LiveSite with multiple stores

Hey all,

After reading the developers guide to LiveSite (2.2.1), it mentions more then once that sites are stored/maintained in the "default" store as per forms publisher etc. Can anyone confirm if it works with multiple stores or stores not named "default"?

Thanks a mil!

Pat

Find more posts tagged with

Comments

Shazzer

It works with whatever stores you have on the same box, regardless of name - you can check this very quickly by just navigating to a workarea in any of the other stores and seeing if the File > New Site option is visible.

Nicholas

Hey all,

After reading the developers guide to LiveSite (2.2.1), it mentions more then once that sites are stored/maintained in the "default" store as per forms publisher etc. Can anyone confirm if it works with multiple stores or stores not named "default"?

Thanks a mil!

Pat

Yes, this line in manual makes confusion somewhere and I was thinking too but just tried creating new one in other store and it works.

Thanks Nicholas

patrickm

Yep, thanks for this! It's only after installing and playing with it I see this. I'm not very impressed that all sites and components are available on all branches and stores. And new sites can be created based on others in other branches. I suppose there isn't a formal way to restrict any of this?!

wscott

If a user lacks file permission to read a particular site, that site will not be presented as an option when creating a new site.

Likewise, if a user lacks file permission to read a particular component/template, that will not be presented for them to add to a page.

However this is restricted on a per-user or per-group basis. There's no way to restrict particular sites/components/templates to particular branches. You can use it to keep different teams from seeing each other's data by applying the permissions on a group basis.