We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 12379
    • 460 Posts
    Can’t get custom fields from modx_web_user_attributes_extended database to display in profile template

    Registration form page:

    [!WebLoginPE? &type=`register` &liHomeId=`23` &regType=`verify` &customFields=`weddate` &regRequired=`email,fullname,phonearea,username,phone,country,zip` &groups=`Registered` &notify=`xxxxxxx` &regSuccessId=`23` &regSuccessPause=`8` &registerTpl=`wlpeRegisterForm` &loHomeId=`33`!]

    And in registration form, wlpeRegisterForm:
    <input id="wlpeUserWeddingDate" name="weddate" type="text" value="[+post.weddate+]" maxlength="8" size="8" />

    And in profile template:
    <input id="wlpeUserProfileDob" type="text" name="dob" value="[+user.weddate+]" />

    I can confirm that "modx_web_user_attributes_extended" database exists with data written to it. Just need to figure out why it isn’t visible in the profile template.
      Mostly harmless.
      • 813 ☆ A M B ☆
      • 326 Posts
      I’m having the same problem, except with a <select> rather than a text input. Have you had any luck making this work? I’m wondering if it has to do with MODx 1.0.0 or a newer version of WebLoginPE? I never had this problem before I set up a site with this new version.
        • 12379
        • 460 Posts
        Looking into it again now. If I can’t resolve then I’ll pass it on as a bug to the Google Code repository for this project...
          Mostly harmless.
          • 12379
          • 460 Posts
          Sorry, this won’t be much help to you but I just discovered the INPUT field for my custom value was being covered by the country dropdown, so false alarm!

          I’m not sure what to suggest in your case other than to recheck everything you’ve done using what I’ve done above. Get into the database to see if the value was saved to the database upon registration. Check the source code of the profile page where it should display to see if the value is infact there. Perhaps make sure the profile page is called as such: [!WebLoginPE? &type=`profile` ...
            Mostly harmless.