Maybe a cached/not-cached flag should be part of any page (and a feature of the core Radiant CMS). Static content is better edited by Radiant but served by apache/nginx/... anyway.
Jan Petrik de Heus scripsit dd. Mon, 22 Jun 2009 08:17:05 +0200 (internet: @303) >> I haven't looked closely at the extensions out there for member >> management. I believe that a common approach is to just piggy-back on >> the existing users, but personally I would not do that. The purpose of >> Radiant's users and your extra users are different enough that they >> make sense being separate, and you'd also control that better by >> rolling your own authentication scheme. I think Ba does this (http:// >github.com/aslakhellesoy/ba/tree/master >> ) > >I've extracted the user management part out of Ba: >http://github.com/p8/radiant-restricted-access-extension/tree/master >It's still a bit beta though: >- User registration will be added today. >- I've turned off caching to allow "logged in as USERNAME" links, >otherwise cached pages would show usernames of other users. >Any ideas on how to fix this? I'm still on 0.7.1 > >Petrik >_______________________________________________ >Radiant mailing list >Post: [email protected] >Search: http://radiantcms.org/mailing-list/search/ >Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
