We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Using CustomFields in a User List => buggy?

    • 5253
    • 17 Posts
    chrizz Reply #1, 17 years, 6 months ago
    Hey ya!

    First of all: WLPE is a great extension with a very intuitive usage... smiley
    After working some days with WLPE I’ve configured a lot and nearly eveything works fine...
    BUT:
    I’ve a page with this Snippet Call:
    [!WebLoginPE? &type=`users` &usersOuterTpl=`wlpe_usersOuterTpl` &usersTpl=`wlpe_UserTpl` &customFields=`user_gender,registered_since` &dateFormat=`%d.%m.%Y um %H:%M Uhr` &usersList=`:default:default:username:ASC` ⟨=`de`!]


    THis page should display all registered (and activated) webusers within an own template. I use some custom fields in this overview.
    For testing purposes I have inserted 2 webusers.
    User A has filled out his profile complete. => a new row in the user_attributes_extended appears
    User B just registered without filling out his profile => no row for this user in the extened table

    When both users show up on the overview with the following template, User B "owns" the values of the extended table from User A... i.e. if User A inserted a Website URL in his profile the same URL show up with the User B row...
    Here’s the template:
    <tr>
<td rowspan="4"><a href = "[~[*id*]~]?service=viewprofile&username=[+view.username+]">
<img src="[+phx:if=`[+user.photo+]`:is=``:then=`assets/snippets/webloginpe/userimages/default_user[+user.user_gender+].gif`:else=`[+user.photo+]`+]" alt="[+user.username+]" title="[+user.username+]" alt="[+view.photo+]" title="[+view.username+]" height="50" width="50" />
</a>
</td>
</tr>
<tr>
<td>[+view.username+]</td>
</tr>
<tr>
<td>Letzter Login: [+view.thislogin+]</td>
</tr>
<tr>
<td>Dabei seit: [+phx:if=`[+user.registered_since+]`:is=`0`:then=``:else=`[+user.registered_since:date=`%d.%m.%Y`+]`+]</td>

</tr>
<tr>
<td>Webseite: [+user.website+]</td>
</tr>


    Does anybody have an idea how to solve this problem? It seems to me as if it’s a bug... :/

    thanks in advance!
    Cheers
      *there are no strangers - just friends who never met*
      • 11712
      • 8 Posts
      Hamster Jovial Reply #2, 17 years, 6 months ago
      Hi,

      Maybe I read your post a bit quickly, but it seems to me that your chunk is mixing [+view.***+] and [+user.***+] placeholders

      For use with &type=`users`, you should use [+view.***+] placeholders only.

      I hope it helps you,
      Olivier
        • 5253
        • 17 Posts
        chrizz Reply #3, 17 years, 6 months ago
        Hi Olivier!

        thanks fot this hint.... after working hours on this it’s easy to lose sight on some important points.... wink
        But now there’s a new question... Hopefully somebody could help me again smiley)

        I want to show visitors the registration/activation date of a user. I created a new custom field (cause i can’t find any timestamp in the regular modx user tables?) called registered_since.
        This field contains a unix timestamp so i thought I could format it with phx:date. I don’t know why, but this won’t work out...
        my phx call:
         [+view.registered_since:date=`%d.%m.%Y`+]
and/or
[+phx:if=`[+view.registered_since+]`:is=`0`:then=``:else=`[+view.registered_since:date=`%d.%m.%Y`+]`+]

        This 2 calls outputs nothing....
        For a short test, this call worked corectly:
        [*createdon:date=`%d.%m.%Y`*]

        Ideas are welcome smiley

        Thanks!
          *there are no strangers - just friends who never met*