Ok that tab, mmm i am using FC 5-0-1 and still in mollio setup making
some plugins etc first before going to design.
I do not have any problems like that, so it must be something of FC
5.0.2 or the code you use.

You might first try locally to create a standard mollio setup and then
check, just to know for sure in which direction the problem is.

I thought of some flush action, or indeed as you say some tag like
donotcachethis, but that should't be the solutions.

So i would check the mollio setup, then if that works you might could
check / compare the code.

On Sep 17, 12:28 am, "Tomek Kott" <[EMAIL PROTECTED]> wrote:
> Marco,
>
> I'm using FC5.0.2, I've attached a picture of the 'tab' that I was refering
> to. It shows up when you browse the project website while also logged into
> the back end. This is what shows up if the page is cached while logged in.
> And the process you described is exactly it, even with Anonymous user .
>
> I just wonder if I'm missing a standard <cf DON'T CACHE THIS> tag or
> something.
>
> I guess I can always change the webskin tag to not put in that tab, even
> when logged in.
>
> Didn't quite think of that until now, should work though.
>
> Thanks,
>
> Tomek
>
> On Tue, Sep 16, 2008 at 6:06 PM, Marco van den Oever <
>
> [EMAIL PROTECTED]> wrote:
>
> > I wish i could help but i can't see the picture, isn't it so that the
> > admin tab is only shown when your a admin? So what you are saying is
> > that:
>
> > You log in as admin -
> > The page is getting cached so also the admin tab -
> > Then when logged out as admin and logged in as user you still see the
> > tab because of the caching -
>
> > Don't know if the version of FC is important to notice?
>
> > And that tab is a navigation tab front end? or back end?
>
> > On Sep 16, 7:51 pm, "Tomek Kott" <[EMAIL PROTECTED]> wrote:
> > > Anyone? It's my own fault for not noticing it before, but I guess I
> > figured
> > > I was logged in at the time.
>
> > > Is there a way to make sure that the admin tab doesn't get cached along
> > with
> > > the rest of the page? Or is there a way to locally (within the page)
> > state
> > > what should be cached?
>
> > > Thanks,
>
> > > Tomek
>
> > > On Mon, Sep 15, 2008 at 5:58 PM, Tomek Kott <[EMAIL PROTECTED]>
> > wrote:
> > > > Hi All,
>
> > > > I am having a small issue with one of my forms (using idlForm, with an
> > > > added Captcha). Generally, the form works, until after I successfully
> > send
> > > > in a comment. Then, the ending text (#stObj.sendt#) is shown
> > constantly. In
> > > > addition, the admin tab is visible, even in a newly launched browser
> > (i.e.
> > > > Explorer if I was using firefox to use the form while logged in).
> > Perhaps it
> > > > is not the best idea to test the form out while in admin mode, but I am
> > > > worried about the admin tab showing up for "normal" users.
>
> > > > So that's one of the problems. The other problem I am having is that
> > there
> > > > seems to be a cache disconnect on the page. That is, once I have used
> > the
> > > > form once after a updateapp, it only shows the "after successful
> > submission"
> > > > text. It does not save the form again, or email it (as it would have to
> > if
> > > > it went through the full displayPageStandard.cfm file and showed the
> > text).
>
> > > > I do have a navigation link in there that would, by default, get
> > cached.
> > > > But I figured since the displayPageStandard for idlform is not being
> > cached,
> > > > then the page would refreshed each time I pointed to it. Could someone
> > > > clarify the caching of skins inside a non-cached object?
>
> > > > Many Thanks,
>
> > > > Tomek
>
>
>
>  admintab1.gif
> 1KViewDownload
>
>  admintab2.gif
> 9KViewDownload
--~--~---------~--~----~------------~-------~--~----~
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