Andreas Hartmann wrote:
Jürgen Ragaller schrieb:
Am 09.08.2007 um 23:27 schrieb Joern Nettingsmeier:
Jürgen Ragaller wrote:
Hi
I am trying to achieve the following behaviour in a sitemap pipeline:
When a user belongs to a group foo, a resource is returned (using a
cocoon-reader), else the user gets a login screen (and after the
login redirect gets the resource). We intend to use this behaviour
for lenya-access-protected assets.
by "resource", you probably mean a static file under <pub>/resources?
No - a new folder (maybe somewhere inside the content folder) with
assets in it.
Actually I'd discourage this - with Lenya 2.0, you rather work with
repository items than with files. It is highly recommended to use the
repository API for document storage.
these files bypass the access controller afaik (but i would need to
check).
why do you want to do this? if access-controlled assets is what you're
after, why don't you just use a lenya document (of resource type
media, or maybe some custom type) and the live access control features
that are already there?
maybe i'm misunderstanding what you're after... if so, please explain
some more.
We have a large number (~ 500) of assets that we do not want to upload
one by one so we put them in a folder wich allows simple mass operations.
Maybe you could implement an import functionality? You could probably
start with the Importer service and customize it to your needs.
if it's a one-time mass upload (say, during a migration) and not an
everyday requirement, you could maybe also write a canoo web test that
does an upload... i haven't done it before, but from what i heard in
andreas' presentation, it should be easy. if iterating over documents is
hard in canoo, do it the unix way: write a shell script that writes a
web test :)
no, i'm really serious. of couse, all this only makes sense if your mass
uploads are rare and only done by site administrators.
regards,
jörn
--
Jörn Nettingsmeier
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
