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



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

Re: Additional user fields
by rh94040 on 2004/4/26 22:12:13

Hi There,

Since there is no set schedule for XOOPS 2.1/2.2 that may
have the configurable user profile feature that I need,
I'll need to hack the code myself to add this capability.

I looked at your site and would like to do something similar.
Would you mind telling me how your changes were achieved?
What files were modified and for what? And what additional
tables did you have to create (or alter)?

Your help is much appreciated.

Ray
P.S. I'm on XOOPS 2.0.6.
Re: Additional user fields
by DaBoyz on 2003/4/16 10:11:29

Quote:
We really need an example for "class XoopsUserPlus extends XoopsUser"....


The same for me ... I need it for an upgrade ... I did a lot of modification for 1.3.5 for an Identity card but I would like to have if I upgrade ...

You see the result here (in french) ...
Re: Additional user fields
by CoolPops on 2003/4/16 5:32:25

Try queryF ... query() only SELECT's unless you are in a POST instead of a GET ... It will then UPDATE, DELETE, INSERT. This is a security feature that I have come to like.

queryF runs the query no matter what but it can open to some security flaws. Take a peek at:

https://xoops.org/modules/newbb/viewtopic.php?topic_id=8161&forum=4&jump=1

--
Jeremy
http://cowgar.com
Re: Additional user fields
by mbogosian on 2003/4/16 4:12:59

Quote:
maseal_s wrote:
The only answer i've find is to hack core files.
It is not a solution

An alternative is to create blocks which are only viewable on the user page. Check out this thread or this patch to see what I mean.
Re: Additional user fields
by trewitt on 2003/3/30 20:10:33

I have the same need, to a much greater extent. See http://www.lone-star.org/xoops/html/register.php

I hacked a LOT of core files under XOOPS 1.2, and wish to avoid editing ANY core files when rewriting under V2. Adding a 'users_plus' SQL table is easy enough, but I need to know what the "Officially Sanctioned Core Class Extension" methodology is. IE, how do I write a module file which extends \kernel\user.php, such that my own module code can reference User properties just as if they had been declared in \kernel\user.php?

We really need an example for "class XoopsUserPlus extends XoopsUser"....

I also need to override the default behavior and appearance of the user login core 'module' (I concatenate First and Last names into uname - see site above). Is there an Officially Sanctioned way to do this without hacking the core (/user.php)?

Who's Online

214 user(s) are online (174 user(s) are browsing Support Forums)


Members: 0


Guests: 214


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