Thanks a lot, Javier! There were a few caveats to getting this to work
for me, but I've gotten there, finally!
For anyone else who wants to use this solution, check out this posting
by a bloke named Andre, who was extremely helpful when I emailed him
asking for a bit of a hand:
http://andre.liqu
On Thu, Aug 13, 2009 at 3:43 PM, stupidgeek wrote:
> Thanks to both of you for the advice - Ben, yours seems to be like a
> step four to Javier's solution. I like it, but will only say I'll
> maybe try it once I've got the serving done Javier's way.
what i get from Ben's comment is more like my s
Thanks to both of you for the advice - Ben, yours seems to be like a
step four to Javier's solution. I like it, but will only say I'll
maybe try it once I've got the serving done Javier's way.
Javier, could you post some example code? I'm pretty sure this is bang-
on what I want, although as I sa
If you want to prevent hotlinking to your documents or illicit access,
then I would suggest writing a view that generates a unique URL per
access. For instance, a user hits your view, they get a randomly
generated link to access the file. You store that random link in
their session as a one-to-o
On Thu, Aug 13, 2009 at 1:00 PM, stupidgeek wrote:
> I've written a faculty review system, with tight checks on access for
> reviews, based on committees, etc. Each review contains a document,
> held by a models.FileField, and I would like to restrict access to the
> file; ie not put it under my D
5 matches
Mail list logo
