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

Quote from: Soshite at Sep 14, 2007, 08:58 PM

Okay. So do you know how it’ll output that when the field is called in the View User Profile page? I was thinking of using this for a list of clubs/fanlistings a user is a member of, once HTML is allowed in inputHandler, hence why I’m asking. It’ll also be useful for the collection/wishlist stuff, like I mentioned earlier.

BTW, I replied to your PM, and sent an extra one w/ something I forgot to put in the first one.

Good point. Maybe it would be better for me to store it in the database as a comma separated list. That way on the view user page, when it outputs the value of "favorite_cars" it will display:
Ferrari,Lamborghini,peugeot

instead of:
Ferrari||Lamborghini||peugeot

I simply used double pipes because I thought it would be less likely to be a value stored than a comma would? Now that I think about it, a comma would be a rather uncommon occurrence in a <select multiple>.

BTW, I got your PMs and I will give a personal response to them ASAP. I truly appreciate your feedback. I think you and I have very different expectations for WebLoginPE, so it is crucial that you keep me informed so we can keep this as universally useful as possible.

-sD-
Dr. Scotty Delicious, Scientist

Quote from: Dr. at Sep 14, 2007, 11:21 AM

Quote from: Uncle68 at Sep 14, 2007, 11:08 AM

I have the issue with not being able to log in with names with international characters

I am not sure what the problem is? I have not been able to recreate this error (using non-english, UTF characters) on any of my servers.

I today tested to create an account on your demo page with the name Ådi will the following result:

Register: No problem
In the email confirming my account it says "Username: Ã…di" instead of Ådi
Trying to log in with either "Ådi" or "Ã…di" I get the same message telling me that there is no account in that name.

But after that I could not test anymore, I just get modx parse error now: "Line 1178 source: foreach($attributes as $field => $value) "

I’m sorry if it was my "Ådi" user name that crashed your demo (I hope not!), but it should have happend sooner or later anyway I guess...

EDIT: Found source of the problem

If I remove the "BINARY LOWER" part of the sql query on row 2350 and 2356, then I can log in. However, don’t know if something else will break.

LOL
It was your name that crashed my server!
I deleted your account and all is well again.
I might have to ban you for life you trouble maker just kidding!

-sD-
Dr. Scotty Delicious, Scientist DFPA.

Sorry for that I bet I got your attention now for this little problem!

I will NOT create any more such names, I promise. But anyone else can now, if they want to crash your demo. Don’t blame me if they do!

I found the source of the problem with logging in with international characters user names, see the edit part of my last post.

Quote from: Dr. at Sep 14, 2007, 09:08 PM

Good point. Maybe it would be better for me to store it in the database as a comma separated list. That way on the view user page, when it outputs the value of "favorite_cars" it will display:
Ferrari,Lamborghini,peugeot

instead of:
Ferrari||Lamborghini||peugeot

I simply used double pipes because I thought it would be less likely to be a value stored than a comma would? Now that I think about it, a comma would be a rather uncommon occurrence in a <select multiple>.

Hmm...is it possible for WLPE to be able to add a space in between the commas when it’s stored in the database? Only because it might look a tad bit odd when it’s displayed on a website.

So it’s like this...

Ferrari, Lamborghini, peugeot

(And those last two ideas I had in the PM were just random stuff I thought of. The stuff about the script as it is now was more important to me, since it’s either a tweaking of something already existing or expanding on something already existing.)

Quote from: Soshite at Sep 15, 2007, 06:38 AM

Hmm...is it possible for WLPE to be able to add a space in between the commas when it’s stored in the database? Only because it might look a tad bit odd when it’s displayed on a website.

Sure thing

-sD-
Dr. Scotty Delicious, Scientist DFPA.

Hmm...looking at the Testing Site you have for WLPE --- I take it that the "signature" doesn’t allow basic HTML to be entered (since the
tag isn’t being parsed for your signature)?

Would it be a security risk to allow HTML in that field, or even allowing basic HTML (bold, italic, underline, links, etc.)? In PPP, this could be allowed, only because it used EForm to parse the profile data (and EForm had a option to allow/disallow HTML). But WLPE uses it’s own code to input profile data, so...

@ Uncle

Ha! Thanks bro.
The BINARY part was part of the original weblogin snippet. I think we can safely remove that.
The LOWER part is necessary for case-insensitive logins.

-sD-
Dr. Scotty Delicious, Scientist DFPA.

Quote from: Soshite at Sep 15, 2007, 08:05 AM

Hmm...looking at the Testing Site you have for WLPE --- I take it that the "signature" doesn’t allow basic HTML to be entered (since the
tag isn’t being parsed for your signature)?

Would it be a security risk to allow HTML in that field, or even allowing basic HTML (bold, italic, underline, links, etc.)? In PPP, this could be allowed, only because it used EForm to parse the profile data (and EForm had a option to allow/disallow HTML). But WLPE uses it’s own code to input profile data, so...

oops!
I used some new db escaping functions, one of them is htmlentities().
Looks like I need to use html_entity_decode() in the placeholders. I really just wanted the quotes converted to entities, not the brackets.
Sorry!

-sD-
Dr Scotty Delicious, Scientist DFPA.

Quote from: Dr. at Sep 13, 2007, 08:10 PM

I will work on getting the LABEL to use a chunk if you want to use HTML, but for now, you gotta take the HTML out of the snippet call or, as they say, "It ain’t gonna work".

When that gets enabled, that will also work work <img /> tags, right, not just <a href=""> tags?