WebLoginPE (1.3.0): Advanced WebUser Management and Extended Profiling.

Im having a hard time getting the viewprofile service to work. If anyone has any pointers they would be greatly appreciated.

<a href="[~54~]?service=viewprofile&username=theUsersName">theUsersName</a>

Quote from: Dr. at Aug 19, 2007, 03:26 AM

TODO.
1. Fix DOB and Last Login so the unset value is not the UNIX epoch.
2. Add TOS agreement which can now be set as "REQUIRED" with the new &regRequired parameter.

We’ll see about finishing those tomorrow, I just forgot about them and didn’t remember until after I posted the update and looked at this thread again.

Just a little reminder for the TOS

And there’s another question: what about a possibility to force the user to enter his e-mail address twice in order to prevent typing errors?

@pixelchutes: Errmmm... That was a long post.
I gotta admit that I don’t agree with your table logic. that looks like either a separate table for each user to keep the tables clean (but cluster fuck the DB) or a huge tangle of an unorganized table. I don’t like either option and I am probably not going to implement this. The current way is easy if you think about it logically. Pick a custom table name (like "my_web_users_stuff") and pass it as a parameter in &customTable. Then all the fields you could possibly want can be passed as parameters (comma separated list) in &customFields. any time you need to access them in a form or template just use [+user.fieldname+]. Any time you want to store the value, post it in a form input <input type="text" name="fieldname" />

That keeps the tables nice and clean and easy to retrieve.

@sD-

Thank you for your feedback. In retrospect, I can agree with your position. Logically, it still makes more sense to store in a custom defined table, complete with proper data types to boot! However, I still think that leveraging the table in some fashion could be doable/beneficial, maybe just not for WLPE.

Really, my idea was sparked thinking of possible ways to handling profile attributes outside of just TEXT inputs...

For example, how would you suggest handling predefined profile options with WLPE (e.g. timezone, favorite music, etc ).

There are times when you may need to define a select menu, radios, or checkboxes opposed to simply "text" inputs. Do you think something like this could even be possible with this great snippet you’ve created?

In addition, what if you wanted TEXTAREA opposed to just TEXT type?

This may be outside the bounds of what WebLoginPE aims to accomplish, but since you were so quick to integrate "extended profiling", I was curious to know the limitations.

What comes to your mind when you think of an example where this would be beneficial? What are you going to pass in a form that does not conform to VARCHAR (int or string)?

<input type="text" ... />

I would suggest doing it in your form template chunk with a <select>.

<select multiple>...</select>

The only issue ATM is if the textarea contained more than 255 chars.

I don’t think "WHAT you want to do" is outside the limitations, it is just "HOW you want to do it".

Again, TGIF This makes perfect sense. I assume this would also account for:

<select multiple>...</select>

Quote from: Dr. at Aug 24, 2007, 06:06 PM

The only issue ATM is if the textarea contained more than 255 chars.

...Even if web_user_attributes_extended custom column is of type TEXT? I’m not sure I see the issue?

Quote from: Dr. at Aug 24, 2007, 06:06 PM

I don’t think "WHAT you want to do" is outside the limitations, it is just "HOW you want to do it".

HOW do you store multiple values in the extended table? Do you use some form of delimiter? Does WLPE allow for editing "extended" profile columns as well? Just curious how, if you are Editing your profile, WLPE handles the mapping of said checkboxes/radios when pre-populating

[!WebLoginPE? &type=`profile` &customFields=`city,timezone,url,favorite_color` &profileTpl=`myProfileChunk`!]

{...}
City:<br />
<input type="text" name="city" value="[+user.city+]" /><br />
Time Zone:<br />
<select name="timezone">
    <option selected="selected" value=[+user.timezone+]></option>
    <option value="EST">Eastern Standard Time</option>
    <option value="CST">Central Standard Time</option>
    <...>
</select><br />
Your Website:<br />
<input type="text" name="url" value="[+user.url+] /><br />
Favorite Color:<br />
Red <input type="radio" name="favorite_color" value="Red">
Blue <input type="radio" name="favorite_color" value="Blue">
Black <input type="radio" name="favorite_color" value="Black">
Spoon <input type="radio" name="favorite_color" value="Spoon">
<br />
You last chose [+user.favorite_color+] <input type="radio" name="favorite_color" value="+user.favorite_color+]" checked="checked">
{...}

Allright, I added now a chunk named TOS which contains - right - my Terms. Then I put &tosChunk=`TOS` to the snippet call (after looking into the snippet code, it’s not yet in the docs). Well, all I’m gettin displayed is "TOS" ... is this the supposed behaviour?

$tosChunk = isset($tosChunk) ? $tosChunk : $wlpeTos;

$tosChunk = isset($tosChunk) ? $wlpe->Template($tosChunk) : $wlpeTos;

Really? Let’s hear it!

if (is_array($_POST[$field])
{
    $field = implode('||', $_POST[$field])
    {...}
}

&input[0]=`inmypocket:select:change,pendrive,knife,widget,phone`
&input[1]=`color:radio:red,blue,black,spoon,rainbow`