WebLoginPE 1.3.0 Bug Reports

Just to check, is this in 1.3.0 or 1.3.1?

Header says 1.3.0 in my local file. I didn’t think to check in 1.3.1. Sorry.

P

hello

I still have two big problems that i want to fix before starting to use customfields in my weblogin PE. Status and age don’t work properly.
Status: nothing appears
Age : when unfilled "Unknown" appears (wich is normal)
When filled properly (MM-DD-YYYY) no answer on my forms

i’m using the following snippet code with webloginPE version 1.3.1:

[!WebLoginPE? &lang=`fr` &type=`users` &viewProfileTpl=`tplprofile` &usersList=`bourlingueurs:default:tplutilisateurin:photo:ASC:`!]

here is (tplutilisateurin) tplate/chunck code :

<div class="wlpeUserPage"><div id="uti1">
<div id="uti2">
<div id="atlas">
<div align="center">
<a href = "[~[*id*]~]?service=viewprofile&username=[+view.username+]&userid=[+view.id+]">
<img src="[+view.photo+]" alt="[+view.photo+]" title="[+view.username+]" height="80" width="80" />
</a></div></div></div>

<div id="uti3">
<p class="wlpeUserPageAttrUsername"><strong><span class="wlpeViewUsersUsername">nom de l’utilisateur</span></strong>: [+view.username+]</p>
<p class="wlpeUserPageAttrAge"><strong><span class="wlpeViewUsersAge">Age</span></strong>: [+view.age+]</p>
<blockquote class="wlpeUserPageAttrComment">[+view.comment+]</blockquote>
</div>
</div>
</div>

uti1,uti2,uti3 and atlas are defined in an alternate css file.
any idea?

Ok i found the problem for the status, in the french lang file the following lines not appeared:

$wlpe_lang[35] = ’un utilisateur non-actif à été supprimé’;
$wlpe_lang[36] = ’L utilisateur "[+000+]" a été supprimé. "[+000+]" Enregistré le [+111+] il n a pas activé son compte.’;
$wlpe_lang[37] = ’Votre message à été envoyé à ’;
$wlpe_lang[38] = ’privé’;
$wlpe_lang[39] = ’pays’;
$wlpe_lang[40] = ’sexe’;
$wlpe_lang[41] = ’En ligne’;
$wlpe_lang[42] = ’Hors ligne’;

Just to add this at the right place still the age wich don’t work...

That’s odd. MM-DD-YYYY works for me...

Quote from: Soshite at Jun 10, 2008, 12:59 PM

Quote from: MackenzieB at Jun 10, 2008, 08:38 AM

Hi, I installed 1.3.0 yesterday and I did the snippet call [!WebLoginPE!] so the type ’simple’ was used. I couldn’t get the updating and deleting a profile to work. Now I’ve looked into it and had to change the following lines in the snippet in order to make it work:

line #297 case ’saveprofilesimple’ : becomes case ’saveprofile’ :
line #304 case ’deleteprofilesimple’: becomes case ’deleteprofile’ :
line #309 case ’confirmdeleteprofilesimple’: becomes case ’confirmdeleteprofile’ :

So basically the services called when the type is simple is without ’simple’ at the end of the value.

I’m surprised I have to do this since it’s a default installation and nobody mentioned this before. Could there be anything I’m doing wrong?

pixelchutes had actually mentioned that earlier in this thread. It’s a spelling mistake Scotty made.

You might want to try out the Beta 1.3.1 release, which includes the majority of the fixes posted in this thread.

I just installed version 1.3.1 and when using the `simple`mode the profile was not updated. So I had to create a template based on defaultProfileTpl and change the value of the button from value="saveprofile" to value="saveprofilesimple". I thought this bug was already fixed in 1.3.1

Quote from: mcclausky at Aug 17, 2008, 03:06 AM

Quote from: Soshite at Jun 10, 2008, 12:59 PM

Quote from: MackenzieB at Jun 10, 2008, 08:38 AM

Hi, I installed 1.3.0 yesterday and I did the snippet call [!WebLoginPE!] so the type ’simple’ was used. I couldn’t get the updating and deleting a profile to work. Now I’ve looked into it and had to change the following lines in the snippet in order to make it work:

line #297 case ’saveprofilesimple’ : becomes case ’saveprofile’ :
line #304 case ’deleteprofilesimple’: becomes case ’deleteprofile’ :
line #309 case ’confirmdeleteprofilesimple’: becomes case ’confirmdeleteprofile’ :

So basically the services called when the type is simple is without ’simple’ at the end of the value.

I’m surprised I have to do this since it’s a default installation and nobody mentioned this before. Could there be anything I’m doing wrong?

pixelchutes had actually mentioned that earlier in this thread. It’s a spelling mistake Scotty made.

You might want to try out the Beta 1.3.1 release, which includes the majority of the fixes posted in this thread.

I just installed version 1.3.1 and when using the `simple`mode the profile was not updated. So I had to create a template based on defaultProfileTpl and change the value of the button from value="saveprofile" to value="saveprofilesimple". I thought this bug was already fixed in 1.3.1

No template fixes were made in 1.3.1.

Sounds like a good, quick 1.3.2 release reason to me.

Quote from: rthrash at Aug 18, 2008, 01:18 AM

Sounds like a good, quick 1.3.2 release reason to me.

I’ll try to get it done before the end of the week, although uni starts for me next week, so it might be delayed because of that.

I was trying to see if the more than one error message, or the pagenation fixes could be done before that, though.

Get it into SVN at Google code and make sure bravado is on the project and pagination will make it in.