10
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.
