-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidnei da Silva wrote:
> On 4/18/07, Kapil Thangavelu <[EMAIL PROTECTED]> wrote:
>> my understanding is that part of the reason this was done, was laziness,
>> on the part of the integrators, who didn't want to deal with the issues of
>> having non pas
On 4/18/07, Kapil Thangavelu <[EMAIL PROTECTED]> wrote:
my understanding is that part of the reason this was done, was laziness,
on the part of the integrators, who didn't want to deal with the issues of
having non pas users from the root acl browsing a plone site, and
conditionally dealing with
my understanding is that part of the reason this was done, was laziness,
on the part of the integrators, who didn't want to deal with the issues of
having non pas users from the root acl browsing a plone site, and
conditionally dealing with those the users within the plone code. i agree
t
I agree, I think the way PlonePAS replaces the root acl_users is very bad. I
hope this gets addressed. Surely there is no need for it to do that.
Ben
On 19/4/07 02:01, "James J Myers" <[EMAIL PROTECTED]> wrote:
> I found the SQLPASPlugin on the Plone site or the collective - not sure
> which.
I found the SQLPASPlugin on the Plone site or the collective - not sure
which.
I pretty much rewrote it to get it to do what I wanted. I got no help
from this list or anywhere else.
PlonePAS provides a PropertyProvider set of interfaces for
setting/getting properties from an external source.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16 Apr 2007, at 13:56, robert rottermann wrote:
Hi there,
I have installed LDAPUserfolder 2.8beta and LDAPMultiPlugun for
Plone 2.5.0
Is there an easy way to list all users from a script.
something like we have in the ZMI user tab of the LDA
