1
mboyden
XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 1:16

  • mboyden

  • Moderator

  • Posts: 484

  • Since: 2005/3/9 1


I've been asked to work on the development of the core Profiles module for the 2.3 release of XOOPS, the merge of the 2.0.x and 2.2.x branches, based on the 2.2.x Profiles module and the direction for 3.0's profile module.

I'd like us to get some feedback from the community about this as we move into the development of the module. What's worked, and what hasn't and what's important that we haven't captured and have?

I've posted a Profiles Module wishlist of functional requirements (in the XOOPS Wiki Wishlist area). Please provide your thoughts and feedback here in this forum and we can move the synopsis and such in the wiki (so it doesn't get too cluttered).
Pessimists see difficulty in opportunity; Optimists see opportunity in difficulty. --W Churchill

XOOPS: Latest | Debug | Hosting and Web Development

2
irmtfan
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 3:13

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


do you see my wish list in the Wishlist_for_XOOPS_30?
i just describe it in Profiles_Module
also i edit your post and correct links.

3
fredgsanford
Re: XOOPS 2.3 Profiles Module - Requirements Gathering

I would like to see custom profile fields that admin could add.
Maybe allow members to leave comments on other member's profiles?

4
irmtfan
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 4:19

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


Quote:

allow members to leave comments on other member's profiles

i name it "scrapbook"
as you can see i add it to wikipage

5
DarinAllan
Re: XOOPS 2.3 Profiles Module - Requirements Gathering

Quote:

fredgsanford wrote:
I would like to see custom profile fields that admin could add.


I will second that, for a community site that concentrates mainly on one topic, generic fields are fairly irrelevant, you need to be able to create specific fields easily that make sense to your members.

Also the ability to make the fields you want mandatory and others optional, if you can get them to fill out the important things on "sign up" it has to be a good thing me thinks! It creates a sense of community.

Cheers....Darin ;o)

6
phppp
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 15:23

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


As the developers have discussed, our priority is firstly to make it ready for public review.

So the development will start from critical features desired by the community. Once the critical features are stable, we can then consider other features.

So, please check the wiki pages and forum topics mboyden mentioned and advise us with your desired priority list.

7
mboyden
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 15:26

  • mboyden

  • Moderator

  • Posts: 484

  • Since: 2005/3/9 1


I guess I wasn't absolutely clear in the Functional requirements, but the concept is to allow administrators to add any field they want and as many or as little as they want, showing or not, etc. The only defined fields will be those that already exist for legacy reasons, but you won't have to use them on your site, and/or you can add more. So, yes, custom fields will be done, and we'll pre-populate a set of them for everyone to use. However, we'll still have to figure out a few things on this since language will be an issue and such. Anyhoos, keep the comments coming. Much thanks.
Pessimists see difficulty in opportunity; Optimists see opportunity in difficulty. --W Churchill

XOOPS: Latest | Debug | Hosting and Web Development

8
DarinAllan
Re: XOOPS 2.3 Profiles Module - Requirements Gathering

Excellent, sounds good!

9
stefan88
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 16:29

  • stefan88

  • Community Support Member

  • Posts: 1086

  • Since: 2004/9/20


Maybe it will be nice to have multistage registration (multiple pages with diferent information configured by the admin. For example: page one - user name, real name; page two - real world contacts); page three - internet contacts; page four - preferences-notification options, subscriptions, theme , password ... )

Also some sort of regkeys field - when is entered, user goes to predefined group based on the key.

User selection of gruop (yes/no and available grups defined by the admin)

Some sort of user points maybe...
..

10
mboyden
Re: XOOPS 2.3 Profiles Module - Requirements Gathering
  • 2008/1/11 16:30

  • mboyden

  • Moderator

  • Posts: 484

  • Since: 2005/3/9 1


irmtfan wrote in Wiki:
Quote:
there should be 2 part in the profiles.

part 1:(base Profile) login name , pass , email these fields should be remained in XOOPS Core and not Profile module. so everybody can uninstall Profile module and still all users base information are remains in the database.

part 2: extensible profile system.
* display name that can be enabled from admin by yes/no
* all other fields should be flexible (you describe it in detail)
* rating system so users from group XX can vote for users from group YY

Absolutely. The way I envision it now, for legacy reasons, is similar to how SmartProfile did it, leaving the XoopsUser table as is for legacy reasons. The rest would be added in another XoopsUserProfile table linked to XoopsUser. Should you not like this Profile module, then you can remove it and add another to your liking. However, I will note that the user.php, register.php, and similar core pages will be modified ala 2.2.x to point to this one, and other modules would have to provide updates to the core files. Unless someone can see a better way to accomplish this.

irmtfan further wrote in Wiki:
Quote:
describe: can we extend it by define a calculate system? you see all other fields can just get one entry not multi entry. can we name it a "Multi Entry" field?
* scrapbook
* my blog and my page
* my gallery

The functional requirements allow for all types of fields including multi-choice checkbox, radio, select (single or multi), etc. As to a scrapbook, myblog, mypage, mygallery, etc., I think those would be best handled by other modules, and then you could link to them somehow. Or maybe I'm not fully understanding your point on this one. Generally, the profile module is for collecting profile information not providing major publishing functionality.
Pessimists see difficulty in opportunity; Optimists see opportunity in difficulty. --W Churchill

XOOPS: Latest | Debug | Hosting and Web Development

Login

Who's Online

162 user(s) are online (109 user(s) are browsing Support Forums)


Members: 0


Guests: 162


more...

Donat-O-Meter

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

Latest GitHub Commits