Bummer. Well, thanks for your help.

On Sep 18, 7:49 am, Gavin Cope <[email protected]> wrote:
> That's the behaviour by design in CMS. Content is either published or it's
> not, there is no middle ground.
> Cheers,
>
> Gavin
>
> 2009/9/18 Eight Hour Lunch <[email protected]>
>
>
>
> > Actually, that's pretty much what we have implemented now. Now that I
> > think about it, I believe I described it incorrectly. The foundation
> > page *does* stay in place. So say you have foundation page 1, and
> > content block (or page in RedDot vernacular) A inside of it as the
> > home page, and you want to schedule a promotion to go live in a week.
> > This requires a change to block A on the home page. Right now if I
> > change block A, container 1 stays up, but the page will stay empty
> > until the date and time of the appearance schedule. I hope I'm
> > phrasing that better this time.
>
> > Anyhow, in any other CMS I've used, the new content is held in the
> > background for the same ID, and the original content stays published
> > until the scheduled date, which is nice, because it means I don't have
> > to bother creating and scheduling two objects that really apply to the
> > same space.
>
> > Doug
>
> > On Sep 17, 2:43 pm, Gavin Cope <[email protected]> wrote:
> > > I'm not sure how you're pages are structured but what about putting the
> > > content in a container on the page, then assigning the schedule to a page
> > in
> > > the container. So you'll have two pages connected to the container, each
> > > with their own schedule.
> > > Cheers,
>
> > > Gavin
>
> > > 2009/9/18 Eight Hour Lunch <[email protected]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to