Welcome to Geeklog, Anonymous Wednesday, November 27 2024 @ 02:52 am EST
Geeklog Forums
User registration plugin and related stuff.
Status: offline
remy
Forum User
Full Member
Registered: 06/09/03
Posts: 162
Location:Rotterdam & Bonn
Comments needed.
Working on some final code regarding a nice custom interface to registering:
When a person wants to register as a user, an account must be created.
The standard GeekLog core requires an username and an email address.
A password is than generated and submitted by email.
The person can than enter the system and fill out the profile.
Eventually username, email and fullname may be changed.
In case the system uses moderation of new users, the GeekLog core requires an username, an email address and the fulname (new ).
An empty password is generated (so nobody can login using the username).
The moderator may now approve or reject the person (moderator sees the fullname), and the result is emailed to the new user.
In case the system uses the custom_member functions, a separate form is used to register the person. This form contains username, firstname, lastname, country, company, email.
The system takes username, email and fulname=(firstname++lastname) into the table 'users' and the other items into the table 'custom_memberinfo'.
In case the system uses the plugin 'registration', a separate form is used to register the person. This form contains username, firstname, lastname, address, postalcode, city, country,private_phone, company, company_city, company_phone, email.
The system takes username, email and fulname=(firstname++lastname) into the table 'users' and the other items into the table 'custom_memberinfo'.
In case the system uses the plugin 'contacts', new functionality becomes available. The table 'custom_memberinfo' contains 'member_id' and if 'member_id' is entered when the user wants to change the profile, the data of the table 'custom_memberinfo' are taken into the table 'contacts'.
The user can only enter member_id once.
The moderator or manager of the table 'contacts' may change or fill in 'member_id', which is than taken into the table 'custom_memberinfo'.
In order to use this extra functionality, the system must use custom_memberinfo functions, or have the 'registration' plugin enabled.
The idea is, to have a simple customized user registration, or make it more advanced using the plugin 'registration'. In order to exploit a nice member administration for (payed) memberships etc.
The 'contact' plugin can connect to users in a automatic way.
Configuration options:
GL core:
$_CONF['custom_registration'] = true; // Set to true if you have custom code
$_CONF['usersubmission'] = 1; // set to 1 to enable submission queues (moderation)
'registration' plugin:
$_REG_CONF['database'] = true; // Set to true if the database is part of the plugin
'contact' plugin:
$_CONTACT_CONF['membership'] = true; // set to true if contacts must be users
Some other changes neccesary.
Since the user can change his/hers identity (username, passwd) this could be a cause for abusing other users. In order to prevent this, the functions to change these wil be using a separat template. In this way, one can decide to have these avalable in the GL core (profile) or the custom functions (Account).
Also, I tend to have the change of username moderated, if moderation is activated.
There is an issue on the real name. The GL core uses only Full name, while custom functions use firstname and lastname. Additional, the contacts use fisrtname, middlename and lastname. To my opinion the GL core can't be adjusted on this. So, on account_create the custom templates form fullname=firtsname+lastname.
Changing these items later, has no effect on fullname.
In either case, the new code has to guarantee the uniqueness of username, email, member_id.
Notes:
-editing the user shows up as 'myProfile'
-the custom registration shows up as 'myAccount'
-the registration plugin shows up as 'myGeeklog'
-the contacts plugin shows up as 'contacts' or 'members'
Working on some final code regarding a nice custom interface to registering:
When a person wants to register as a user, an account must be created.
The standard GeekLog core requires an username and an email address.
A password is than generated and submitted by email.
The person can than enter the system and fill out the profile.
Eventually username, email and fullname may be changed.
In case the system uses moderation of new users, the GeekLog core requires an username, an email address and the fulname (new ).
An empty password is generated (so nobody can login using the username).
The moderator may now approve or reject the person (moderator sees the fullname), and the result is emailed to the new user.
In case the system uses the custom_member functions, a separate form is used to register the person. This form contains username, firstname, lastname, country, company, email.
The system takes username, email and fulname=(firstname++lastname) into the table 'users' and the other items into the table 'custom_memberinfo'.
In case the system uses the plugin 'registration', a separate form is used to register the person. This form contains username, firstname, lastname, address, postalcode, city, country,private_phone, company, company_city, company_phone, email.
The system takes username, email and fulname=(firstname++lastname) into the table 'users' and the other items into the table 'custom_memberinfo'.
In case the system uses the plugin 'contacts', new functionality becomes available. The table 'custom_memberinfo' contains 'member_id' and if 'member_id' is entered when the user wants to change the profile, the data of the table 'custom_memberinfo' are taken into the table 'contacts'.
The user can only enter member_id once.
The moderator or manager of the table 'contacts' may change or fill in 'member_id', which is than taken into the table 'custom_memberinfo'.
In order to use this extra functionality, the system must use custom_memberinfo functions, or have the 'registration' plugin enabled.
The idea is, to have a simple customized user registration, or make it more advanced using the plugin 'registration'. In order to exploit a nice member administration for (payed) memberships etc.
The 'contact' plugin can connect to users in a automatic way.
Text Formatted Code
Configuration options:
GL core:
$_CONF['custom_registration'] = true; // Set to true if you have custom code
$_CONF['usersubmission'] = 1; // set to 1 to enable submission queues (moderation)
'registration' plugin:
$_REG_CONF['database'] = true; // Set to true if the database is part of the plugin
'contact' plugin:
$_CONTACT_CONF['membership'] = true; // set to true if contacts must be users
Some other changes neccesary.
Since the user can change his/hers identity (username, passwd) this could be a cause for abusing other users. In order to prevent this, the functions to change these wil be using a separat template. In this way, one can decide to have these avalable in the GL core (profile) or the custom functions (Account).
Also, I tend to have the change of username moderated, if moderation is activated.
There is an issue on the real name. The GL core uses only Full name, while custom functions use firstname and lastname. Additional, the contacts use fisrtname, middlename and lastname. To my opinion the GL core can't be adjusted on this. So, on account_create the custom templates form fullname=firtsname+lastname.
Changing these items later, has no effect on fullname.
In either case, the new code has to guarantee the uniqueness of username, email, member_id.
Notes:
-editing the user shows up as 'myProfile'
-the custom registration shows up as 'myAccount'
-the registration plugin shows up as 'myGeeklog'
-the contacts plugin shows up as 'contacts' or 'members'
6
11
Quote
All times are EST. The time is now 02:52 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content