So what I did (and it works) is put in a <skin:view > call near the top of the standard displayPageStandard. Are you saying that in displayPageStandard I should only have(for example in quick notation)
<skin:view header> <skin:view loginHeader> <skin:view body> <skin:view footer> And let farCry take care of caching things? Right now it's more like: <skin:view header> <skin:view loginHeader> .... code code code.... <skin:view footer> If that makes sense... Would there be a big difference? Thanks! Tomek On Wed, Jan 7, 2009 at 9:09 PM, Blair McKenzie <[email protected]> wrote: > Put the login form / logged in info in it's own webskin, and make sure any > other stuff is also in its own webskin. This way you can cache parts of a > page even when one section is uncached. > > > On Thu, Jan 8, 2009 at 12:44 PM, Tomek Kott <[email protected]> wrote: > >> Sorry if this has been asked before, I might have searched for the wrong >> terms under the google groups... I imagine this has been done. >> I wanted to have a little additional menu right under my main menu that >> simply listed if you were logged in and how to log out which would only >> should once you were logged in as a member. (Something like the admin tab >> but for normal users who don't have admin privaleges). I was wondering what >> the best way of doing this was, since I don't know how it would interfere >> with the object broker caching. Where would the right place be to put in >> something like this so it only shows up when logged in and doesn't appear >> for anyone else through the beauty of caching? >> >> Thanks! >> >> Tomek >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
