customFields... how ?

Hi,

I’m new to WebLoginPE, and as far as I read, this is a great addition to modx. But, I have a problem, and I think it is very simple, but I can not find the solution on the forum.
I have 300 users into my users database. I want to add custom fields to them (like, the company they work for, the sector, etc...) and also make these new fields available for an admin into the manager.
Can someone can explain me how to do that, or just give me a link where I can find the answer

thanks in advance,

Arnaud

Check the docs: webloginpe/docs/parameters.html (in the unzipped snippet folder)

&customTable, &customFields

For total control, WebLoginPE creates a table in your MODx database to store as many user attributes as you want. The default name for this table is ’web_user_attributes_extended’, but you can override that with the customTable parameter. You can specify an unlimited amount of column names for this table using the customFields parameter.
[!WebLoginPE? &customTable=`my_web_users` &customFields=`website,aim,msn,city,address1`!]

ok, but can I change the manager interface easily ?

Quote from: arnaud404 at Jan 15, 2008, 03:03 PM

ok, but can I change the manager interface easily ?

Huh? There’s isn’t a "manager" interface in WLPE, AFAIK.

Quote from: Soshite at Jan 15, 2008, 08:59 PM

Quote from: arnaud404 at Jan 15, 2008, 03:03 PM

ok, but can I change the manager interface easily ?

Huh? There’s isn’t a "manager" interface in WLPE, AFAIK.

Actually there is, though it’s called a "view" ([!WebLoginPE? &type=`manager` !])

But what I guess arnaud means is the interface for managing webusers in the original MODx manager, and as far as I know, I am afraid the answer is no. It’s a hassle to change it, and requires changing core files. I’m not really sure which ones to change, several files have names that implies that they are involved...

I’d love to see WebLoginPE replacing the original user management system, or at least that the built in sytem includes the possibility of extended attributes. It is a major hassle to use extended attributes in combination with multisort at the moment, as multisort fails catastrophically if not all users have a value in all the attributes you sort on...