We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30552
    • 75 Posts
    Not sure whether this is documented or not, or if maybe I was doing something wrong, but I thought I could help someone else out if they find themselves in the same boat I was in.

    WebloginPE is great, but more functionality than I need. I really just needed a simple (but functional) login script, and WebLogin is old, and unkept as far as I know. Anyways, my problem with WebloginPE was not being able to make use of the placeholders on the login page I specified via &liHomeId=`x`

    I tried lots of different stuff to make it happen, but in the end, all I needed to do was make a new call to the WebloginPE snippet on the landing page.

    For instance, on my login page, I have this call:

    [!WebLoginPE? &type=`simple` &loHomeId=`25` &liHomeId=`26`!]


    And on my landing page (page ID 26), I make almost the same call, but this time I specified the template chunk I want to be used for that page:

    [!WebLoginPE? &successTpl=`loginSuccess` &loHomeId=`25` &liHomeId=`26`!]


    This seems to solve my problem perfectly. Keep in mind, though, I just figured this out a couple minutes ago, and I don’t make any use of extended functionality, like profiles or anything like that. I only wanted a universal landing page that was separate from the login page (due to the fact that my Login Page title is "Log-In Page," and I didn’t want that at the top of the internal page after the user logged in).

    I personally am not much of a programmer, so I don’t really think like one. If I missed an easier or more obvious way of doing this, someone please correct me.