Thread

Hi, I’m evaluating EE for use in a membership site, but it seems that the evaluation version of EE does not include the membership functions which I need to evaluate.
I’m kind of stuck, I don’t really want to purchase a product simply to find out if it might work for the project.

As a brief outline of the site requirement: Each member will have access to a per-user homepage, so it’s not really a “user group accesses group content”, rather that each user is granted access to their own personal area full of personal files and data.

From the EE documentation I cannot tell if this is possible, it mainly seems to indicate granting membership groups access to general areas, for groups of users.

Is there any way to actually try out the full EE system?

Hi, angstrom - welcome to the forums!

The membership module gives front-end membership abilities, but you can set up what you’ve described, using Core as long as you use the CP to register and login.

I’m also going to send you an email shortly, to the email listed on this account.

Thank you.

Yeah, I’m looking for something similar. I need to know if the membership module allows you to store some custom HTML data as an admin, that can then be retrieved by the member via their profile page or status or whatever.

Thank you

PS: please don’t email me, I used a 10 minute email to register.

You can set up custom profile fields in the backend to store data specific to each user, and you can set those to be available on the front-end, yes.

Maybe I should have used justhere4twoquestions as my username 😊

I realize that I did not express my question the right way. I am not looking for custom fields added to the profile. I’m looking for a way to have the admin STORE additional data for each user by going to “edit user”, that will then be showed to the user without the possibility to edit it. In other words, it is not just another field, like “What’s your favorite drink?” and then the text box next to it for the user to fill in the answer.

It’s a textarea that gets stored in the DB under that user’s ID, and is then retrieved from the DB, when the user visits their profile, and displayed as regular HTML on the page, not as part of the update profile form.

For example, the admin will store the following for user Jim:

Jim, there is a <font color=red>past due balance</font> on your account in the amount of $500. 
<a >Click here</a> to go to our secure payment page.

And later on, when Jim logs in, he’ll see the above at the top of his Profile page, under a heading that says “Your financial status”.

It does not have to be in the profile page however, it can be pulled anywhere else once the user logs in. The point is to have an easy way of storing custom information on a per user fashion that will only be displayed to that specific user.

I hope I said it right this time.

You can do that using a custom profile field; you can set it so that the user can’t edit it, but you can set it up so that it is output on the front-end where and when you need it.

Still a custom profile field though. =)

I understand. Thanks so much for the prompt reply.