Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
0 + 5 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     

Re: Profile Module (Was: xlanguage will not work with profiles)
by Mamba on 2013/1/21 14:49:41

Quote:
moderators ?

topic name maybe should be change to "proposals for a new profile module in 2.6" like suggested by irmtfan

It is already split for several days now, and the title reflects that:
Quote:
Profile Module (Was: xlanguage will not work with profiles)
and it is already in the 2.6.0x Support forum
Re: Profile Module (Was: xlanguage will not work with profiles)
by sabahan on 2013/1/21 14:29:10

Quote:

irmtfan wrote:
[quote]

@forum moderators:
This topic goes off-topic already. please create a new topic (name: proposals for a new profile module in 2.6) and moved all posts after number 14 or 15



moderators ?

topic name maybe should be change to "proposals for a new profile module in 2.6" like suggested by irmtfan

Profile Module (Was: xlanguage will not work with profiles)
by irmtfan on 2013/1/14 6:48:55

Quote:

All configs that are not supposed to be displayed on profile pages (no visibility/ no permissions) can be moved into userconfigs (theme, receive emails, show email, etc)


It is very good approach.
So we deal with legacy fields one by one. It means we think about the right place for each field in the future.
here is my proposal include some features that i saw in sourceforge tracker.

fields moved to profile module:
- uid: not editable/unremovable
- uname: not editable/unremovable - requested featuires: varchar(25) is not enough at all . It should be changed to varchar(60). ability to have spaces(spaces between words. should be aware of bad spaces)
- email: not editable/unremovable - ability to login with email (a very very long wish - just needs 2 lines of codes)
- pass: not editable/unremovable
- name: editable/unremovable - better to be unremovable becuase it is widely used in core and modules
- url: editable/removable
- user_avatar: editable/removable
- user_from: editable/removable
- user_sig: editable/removable - tinytext is not enough - should be changed to text
- user_occ: editable/removable
- bio: editable/removable - tinytext is not enough - should be changed to text
- user_intrest: editable/removable
- user_icq: editable/removable - drop or not? keep just for legacy purposes?
- user_aim: editable/removable - drop or not? keep just for legacy purposes?
- user_yim: editable/removable - huum even drop?
- user_msnm: editable/removable - drop or not? keep just for legacy purposes?

fields moved to logger module
- user_regdate
- actkey: logger or profile?
- last_login: therte is a long wish for a login history and not only last login. easily can be implemented in logger module.

fields moved to userconfigs module:
- user_viewemail
- attachsig
- theme
- timezone_offset: userconfigs or profile module? nobody need to be known my timezone?
- umode: flat, nested, threaded. I wish to also see hybrid=(flat+threaded) it is in Vbullletin
- uorder: ASC or DESC
- user_mailok

fields moved to mypoints module:
- posts
- level
Previously i think we must have a Like module too. just the same as FB Like. It can also have "dislike" in addition to like/unlike features.
Now i think it can be in mypoints? or we still need a separate like module.

fields moved to userrank module:
- rank: features:ability to have more than 1 rank per user. also text ranks

fields moved to notifications module:
- notify_method
- notify_mode


@forum moderators:
This topic goes off-topic already. please create a new topic (name: proposals for a new profile module in 2.6) and moved all posts after number 14 or 15
Re: xlanguage will not work with profiles
by trabis on 2013/1/13 12:35:19

Quote:

irmtfan wrote:
Yes i also think we should drop the legacy fields.
but you know some of those fields are unique and are used widely in core/modules.
eg: posts, theme, umode, uorder
so the new profile module should care about them too. is that possible to make other modules be aware of these unique fields?
some fields are useless now. eg:user_msnm, user_icq are dead.

There is already a userconfigs module in 2.6.0 that will be used to hold configs by user. For example, the comments module will be using userconfigs table instead of user table. All configs that are not supposed to be displayed on profile pages (no visibility/ no permissions) can be moved into userconfigs (theme, receive emails, show email, etc)

I think 'posts' could be managed by other module, perhaps a refactored 'mypoints' could do it.
Re: xlanguage will not work with profiles
by irmtfan on 2013/1/13 5:47:11

good i was thinking about these too.
Quote:

All other modules should use the profile api to get user data.

Yes i also think we should drop the legacy fields.
but you know some of those fields are unique and are used widely in core/modules.
eg: posts, theme, umode, uorder
so the new profile module should care about them too. is that possible to make other modules be aware of these unique fields?
some fields are useless now. eg:user_msnm, user_icq are dead.

IMO only uname, email and pass are vital for a website that dont need any profile system.

hope i could help more.


Who's Online

229 user(s) are online (165 user(s) are browsing Support Forums)


Members: 0


Guests: 229


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits