I did get the default to show up by changing the container name. But I
guess I would still like to know which tables I could go to in order
to delete the rows. Having to rename a container just to change the
defaultMirror seems a little crude and so does deleting data, but at
least deleting data is doing some cleanup.

I suppose for a future version it may be nice to set the Reflection
back to Default for a give page.

On 10/16/07, Matt Williams <[EMAIL PROTECTED]> wrote:
> Hey Geoff, thanks for the response. This does help my understanding.
> But changing the container's label attribute doesn't seem to change
> anything. Are there any records in the db that I could delete to force
> it to read those containers again?
>
> Basically I have several news articles that were created, originally
> with the standard content template. I then created a new template,
> with the default Mirrors I wanted in the containers. I changed the
> template in the news object, approved it, but the containers are not
> showing their default. I am just working with one news item now, but
> have several that should use the same template with the same defaults.
> And the same defaults should be used when a new news item is created
> also. Let me know if you have any suggestions here...
>
> I chose the ID over the label since I am hard-coding it into a
> template, it seemed the ID was less likely to change than the label,
> which is a CMS user-editable value.
>
> Matt
>
>
> On 10/16/07, modius <[EMAIL PROTECTED]> wrote:
> >
> > On Oct 16, 5:03 am, "Matt Williams" <[EMAIL PROTECTED]> wrote:
> > > Any reason why my template wouldn't pick up defaultMirror changes in a
> > > container?
> > >
> > > I have a template like so
> > > <con:container label="#stobj.objectID#_Right-A"
> > > defaultMirrorID="C21E1ACD-1143-104D-F6E6948DDEA98FCA">
> >
> > defaultMirrorID?  I know that's in there but not sure I've ever used
> > it in production ;)  Any reason you're not using label?
> >
> > Default mirrors are only allocated upon container creation.  So once a
> > container is created, there is a one time check for a default mirror.
> > If no default mirror is specified then its assumed the page container
> > is just empty.  From that point on, the container will never be
> > reallocated the mirror -- ie. you may in fact intend for the container
> > to be empty.  In order to get the mirror to reapply you would need to
> > delete the page container.
> >
> > Does that help?
> >
> > -- geoff
> > http://www.daemon.com.au/
> >
>


-- 
Matt Williams
"It's the question that drives us."

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" 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/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to