WebLoginPE v1.3.1 Bugfix (Released August 5th!)

I think it’s as simple as a new filter in the &usersList parameter.
I understand what a random user is but what differentiates a "featured" user from the others?

Quote from: vhollo at Sep 17, 2008, 07:31 PM

I think it’s as simple as a new filter in the &usersList parameter.
I understand what a random user is but what differentiates a "featured" user from the others?

Let’s say a site wanted to show off a particular member, for uploading stuff to the site, etc. It would be an easy way for the staff to add in the name, and WLPE would grab the data for them.

I’ve also seen sites (including the MODx forums) that "feature" the newest user.

Could someone validate this bug for me, before I add it to the Tracker?

I had checkboxes for adding items to the a user’s wishlist/collection on my website. When it saved the data, it emptied the "core" WLPE fields, such as avatar, contact info, location, etc. etc.

I had to include in the default field and hide them from the user (but so the code could see it) to get it not to do that.

This shouldn’t be how the script works. WLPE shouldn’t be looking for the default values when they aren’t being called (only adding data / editing select fields in that case).

I had to include in the default field and hide them from the user (but so the code could see it) to get it not to do that.

That’s what you have to do, I think. The user can only see his/her own data in the code, right?
And the password isn’t needed to be resent in hidden input. I remember there was a hack/mod/bugfix not to clear the userimage if it’s not sent.

Quote from: vhollo at Sep 25, 2008, 06:28 PM

I had to include in the default field and hide them from the user (but so the code could see it) to get it not to do that.

That’s what you have to do, I think. The user can only see his/her own data in the code, right?
And the password isn’t needed to be resent in hidden input. I remember there was a hack/mod/bugfix not to clear the userimage if it’s not sent.

No, I meant I had to call the input fields for username, fullname, e-mail, userpic, etc. etc., but as type="hidden". It takes a long a** time to copy and edit all of the fields.

Basically, if you took away the hidden status, you’d have the user account editor in that page. That’s how bad that issue is. It literally "nukes" the majority of the user’s profile if they’re using the default set of fields WLPE ships with.

Try this but I’m not sure..
Line 915:
[tt]if ($_POST[$field] && $field!=’photo’ || ($_FILES[’photo’][’name’] !== ’’ && !empty($_FILES[’photo’][’name’]))) // for update db with value and blank value (except if the field is ’photo’)[/tt]
Sure it will not delete blank values

Quote from: mcclausky at Aug 31, 2008, 02:46 PM

I believe this is a bug, as I am having exactly the same problem. After Saving the profile, the webShortname session is destroyed!, and this is giving me problems with LoggedOrNot because that snippet relies on the value of webShortname session.

Any suggestions? How can we fix this?

Thanks!

Mc

Hi

Did anyone find a way to solve this session destroyed problem? It happens everytime I Save the profile.

Thanks!

Mc

Quote from: mcclausky at Oct 15, 2008, 10:42 PM

Quote from: mcclausky at Aug 31, 2008, 02:46 PM

I believe this is a bug, as I am having exactly the same problem. After Saving the profile, the webShortname session is destroyed!, and this is giving me problems with LoggedOrNot because that snippet relies on the value of webShortname session.

Any suggestions? How can we fix this?

Thanks!

Mc

Hi

Did anyone find a way to solve this session destroyed problem? It happens everytime I Save the profile.

Thanks!

Mc

Any more on this issue??? I am having all sorts of issues with this problem.

Quote from: rossco at Nov 12, 2008, 10:48 AM

Any more on this issue??? I am having all sorts of issues with this problem.

No news about this issue for months. Perhaps we should start a new thread about it?