[Hippo-cms7-user] [HST] "preview only" modules
a.schrijvers at onehippo.com
Tue Feb 10 16:11:50 CET 2009
> Hi Niels,
> I guess you could just duplicate the hst:configuration in
> your CMS console and create a version that is in unpublished
> mode. Now the state of the hst:configuration is probably set
> to published?
As the published version is typically a result of publishing the
unpublished (:-)) version, it might be confusing to rely on different
configurations for both.
As I would prefer to have a different session user (different userid, so
for example a preview user and a live user ) for live & preview (not
sure if you can easily build this in the hst2 trunk), I think the
cleanest solution is as follows:
1) define a (marker only) mixin nodetype, for example:
2) create two users, a live and preview user. The live user has no read
rights on nodes of type 'myproject:previewonly'
3) add the mixin 'myproject:previewonly' via the console on those nodes
that are not allowed for the live user.
That should do the trick
> Niels van Kampenhout wrote:
> > Hi,
> > I created a bunch of modules that together add inline editing
> > functionality to a website. The user can login using a
> small login form.
> > If a user is logged in, some extra CSS and JS files are loaded that
> > enable inline editing when double cliking on some areas.
> > It's a proof of concept, and as such it works quite well.
> However the
> > inline editing functionality should only be available in
> the preview
> > site. Is there a (preferably easy ;-) ) way to have a different HST
> > configuration in preview and live? I just want to leave out some
> > modules in the preview.
> > Thanks,
> > Niels
> > _______________________________________________
> > Hippo-cms7-user mailing list and forums
> > http://www.onehippo.org/cms7/support/community.html
> View this message in context:
> Sent from the Hippo CMS 7 mailing list archive at Nabble.com.
> Hippo-cms7-user mailing list and forums
More information about the Hippo-cms7-user