Can someone please explain the table structure for the FEusers module ?
We have a separate online application for member management. We would like to use this member information in our new CMSMS-base website. Therefor we have renamed the existing FEusers_users table and FEusers_belongs (added the extension _old) and replaced them with a view from our other member table, respecting the field names.
We use the standard verification code for loggedin member and the group belonging.
{if ($ccuser->memberof($extra1) and $ccuser->loggedin()) or $extra1 == ''}
The login works fine , but the module does not recognise if the user belongs to the group "members" as identified in the extra1 field. (we only have "members" and "pending members").
I see that there are also other FEuser tables, but i cannot see what they are used for.
As this is quite urgent, I'm looking forward to all your helping & clarifying replies. Thanks in advance !
FEUSERS table structure
Re: FEUSERS table structure
Do you have a FEU group called "members" already set up in the FEU admin panel (Groups tab)?
also, as I read your if statement, the content following the statement will be shown in two cases:
1. the user is logged in and a member of the group
or
2. the extra1 field is empty
This means that ANYONE (logged in or not, member of x group or not, etc.) can see the "protected" content on any page if you forget to put something in the extra1 field.
Obviously I don't know your site or any other logic you may have in the template or page, but I would advise against logic like this.
also, as I read your if statement, the content following the statement will be shown in two cases:
1. the user is logged in and a member of the group
or
2. the extra1 field is empty
This means that ANYONE (logged in or not, member of x group or not, etc.) can see the "protected" content on any page if you forget to put something in the extra1 field.
Obviously I don't know your site or any other logic you may have in the template or page, but I would advise against logic like this.
Re: FEUSERS table structure
Hi jmcgin51,
Thanks for your prompt reply.
The group "members" is indeed setup in the FEU admin panel GROUP Tab.
The page security has been tested and works fine with the code mentioned. Anyone who is not logged in has no access to protected content, even if they know the direct url to the protected page.
Protected content is put in a separate content block which is controlled by that "if statement". In this case we can have public and restricted content on the same page and have it displayed depending on the login status.
Any suggestions for improvement are welcome.
Thanks for your prompt reply.
The group "members" is indeed setup in the FEU admin panel GROUP Tab.
The page security has been tested and works fine with the code mentioned. Anyone who is not logged in has no access to protected content, even if they know the direct url to the protected page.
Protected content is put in a separate content block which is controlled by that "if statement". In this case we can have public and restricted content on the same page and have it displayed depending on the login status.
Any suggestions for improvement are welcome.
Re: FEUSERS table structure
if it's working the way you need it to work, that's ok. I'm still having trouble understanding the logic, though. Can you elaborate on why you would want the statement to evaluate true if (the member is logged in and member of the x group) OR if (the extra1 field is empty)??myleen99 wrote: Hi jmcgin51,
Thanks for your prompt reply.
The group "members" is indeed setup in the FEU admin panel GROUP Tab.
The page security has been tested and works fine with the code mentioned. Anyone who is not logged in has no access to protected content, even if they know the direct url to the protected page.
Protected content is put in a separate content block which is controlled by that "if statement". In this case we can have public and restricted content on the same page and have it displayed depending on the login status.
Any suggestions for improvement are welcome.
Re: FEUSERS table structure
At this moment 2 conditions are important:
- visitor is logged in
- visitor is member of the group "members"
I'm not sure about the condition "OR extra1 field = empty". I just copied the code from another post and it helped me at that moment. You made a good point here. I will further investigate this.
BTW : do you have information on the FEusers tables and how they are used to verify if someone is registred and to which group he/she belongs ? That was the main purpose of my initial question.
- visitor is logged in
- visitor is member of the group "members"
I'm not sure about the condition "OR extra1 field = empty". I just copied the code from another post and it helped me at that moment. You made a good point here. I will further investigate this.
BTW : do you have information on the FEusers tables and how they are used to verify if someone is registred and to which group he/she belongs ? That was the main purpose of my initial question.
Re: FEUSERS table structure
sorry, can't help you with the table structure.
I would suggest removing the or $extra1 == '' from the if statement. I think it will still behave the way you want, and your content will be more secure.
I would suggest removing the or $extra1 == '' from the if statement. I think it will still behave the way you want, and your content will be more secure.
[SOLVED] Re: FEUSERS table structure
Thanks for the suggestions.
I've removed all additional conditions and kept only the login check $ccuser->loggedin().
Our external user management is secure enough and all users belong to the same group, so there is no need for additional diversification and control.
This makes life already a lot simpler.
I've removed all additional conditions and kept only the login check $ccuser->loggedin().
Our external user management is secure enough and all users belong to the same group, so there is no need for additional diversification and control.
This makes life already a lot simpler.
