[Slashcode-development] members-only

[shane <sh...@lo...>]

I've got someone who has a slash-based site, and parts of it need to  
be locked down to paying members only.

Years ago there was someone on IRC that I'd helped accomplish this  
(if you're around, please contact me). But since the code's been  
changing quite a bit since then (section-topics, etc) I'm looking at  
starting from scratch.

When I was running this through my head I thought I'd create a  
skins.acl, then add code to the apache handler that checks if the  
skinds.{user.currentskid}.acl exists, check for the user having that  
acl etc etc.

What's interesting is deciding whether to try and block out .shtm's  
through the apache handler or stop writing them when an article's  
primary skid has an acl associated with it.

Take  http://linux.slashdot.org/article.pl?sid=06/02/14/0429228 and  
view it in the games section http://games.slashdot.org/article.pl? 
sid=06/02/14/0429228

I was suprised at the redirect/url-rewrite to the article's primaryskid.

Now as an AnonCoward: http://linux.slashdot.org/linux/ 
06/02/14/0429228.shtml

and

http://games.slashdot.org/linux/06/02/14/0429228.shtml

I was surprised at that as well. It seems to have kept the  
proper .css file inclusions even though the subdomain in the tld  
changed. Which is great with regard to cosmetics and each individual  
story. It's bad if you want a story to be subscriber only/member only  
for the life of the story.

Any thoughts?

Anyone else interested in this?

  Shane