Hi,
This is now checked in on the miwa-adapterise-memberdata branch of
CMFCore.
I'll merge it in next week.
Miles
Miles wrote:
Hi,
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this
Am 18.03.2009 um 18:02 schrieb Miles:
Sure. Example use cases are fairly simple things like:
- I set members to have first_name, last_name, job_title attributes
and
I want to give them an attribute proper_name that returns
'%s %s (%s)' % (first_name, last_name, job_title);
- I
Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2009, at 16:12 , Wichert Akkerman wrote:
Previously Miles wrote:
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 19, 2009, at 12:50 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
One use case I have: I need a different Member Data object (and thus
the whole overridden tool) for Products.CMFLDAP in order to have
custom overridden methods
Hi,
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this is that the only way to use a different MemberData
class is to provide a custom wrapUser method.
I'd like to propose that this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2009, at 16:23 , Miles wrote:
Hi,
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this is that the only way to use a different
Previously Miles wrote:
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this is that the only way to use a different MemberData
class is to provide a custom wrapUser method.
I'd like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2009, at 16:12 , Wichert Akkerman wrote:
Previously Miles wrote:
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this is that the
Hi,
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular sites.
The reason for this is that the only way to use a different MemberData
class is to provide a custom wrapUser method.
I'd like to propose that this is
