Paul Hendrick wrote:
Hi all,
I'm using CookieCrumbler on a project which sits in / on one server,
and /project in another.
...that could do with more explanation :-S
I'd like to secure a part of the site through *.metadata files so that
users of a certain role can't access it.
This is _not_ the correct way to do this. Are you using Plone or
something similarly silly?
What are you trying to do? What lead you to believe .metadata files are
the way to go?
however, when they try to access a part of the site which is secured,
they're:
a- given a log in popup prompt which they don't have the details for.
and
You've likely managed to make the login form unaccessable to anonymous
users...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
