WebLoginPE quick question

so.. I’m using the WebLoginPE snippet.

After the user logs in, he is redirected to this page:


If the user wishes to make changes to his profile, after he presses the Edit profile button he then gets to:


Now, as u can see there’s a problem with that page. The profile options display both in the sidebar and in the content section. I don’t want that.

My question.. well how do I do it? Any ideas?

It’s because you have to WebLoginPE calls on the same page. At the moment the only way around is to use a different template without the second call for that page or use a conditional Phx call to feed it. For example I normally use the following

[+phx:if=`[*id*]`:is=`3`:or:is=`34`:or:is=`42`:then=`{{NoLoginCall}}`:else=`{{LoginCall}}`+]

If the user is on pageID 3,34 or 42 the the Chunk without the WebloginPE call is use else the chunk with the call is used.

Hope this helps

I’m gonna try it. Also, can you provide a basic example of 2 page sources. That use that phx condition. I haven’t currently used Phx yet and so I’m really unfamilliar with it.

From that example, I understand that the {{NoLoginCall}} and {{LoginCall}} are two chunks. The question lies: should I add the [+phx: condition after the WebLoginPE or in the chunk I wish not to use?

[LaterEdit]

Ok, managed to do that. That has fixed my problem but has raised another one.

If I remove the 1st WebLoginPE call, then the [+user.username+] doesn’t get parsed (because it’s only plain HTML now) and it isn’t displayed. It shows only the ’Logged in as .’ when it should show ’Logged in as *USERNAME*.’

Here’s what I mean:

Hi you could probably use the Personalize snippet to display the username instead since your placeholder can’t be parsed.

You could probably also write a simple snippet to output the name instead.

$test = $modx->getLoginUserName();
echo $test;

I havn’t tried these but they sould probably work for you.

Quote from: hexagone at Jun 04, 2008, 12:19 PM

Hi you could probably use the Personalize snippet to display the username instead since your placeholder can’t be parsed.

You could probably also write a simple snippet to output the name instead.

$test = $modx->getLoginUserName();
echo $test;

I havn’t tried these but they sould probably work for you.

I use Personalize to output a drop-down menu for my visitors. It’s a great script to use.

1

To avoid the 2 instances issue when using WebLoginPE, I decided to replace the login with my own snippet that displays the username when logged in, or creates a ’login’ link to my login page. Fairly straightforward stuff here...and with some effort i was able to get the ’simple’ services all working. However, one small issue remains that continues to elude me. As follows:

Assuming a working version of 1.3.1 service simple, user logs in, hits
profile, updates profile and chooses ’save’...

Expect: return to profile with status update message, and
$modx->getLoginUserName() returns value of the ’username’.

Results: return to profile with status update message, and
$modx->getLoginUserName() returns value of ’’.

The function $modx->getLoginUserName() value displays properly on all pages
until you save the profile, then it mysteriously disappears on all pages,
although a user remains logged in and $_SESSION[’webValidated’] remains true.

Any ideas??

You could also use the <strong>1.32 Beta</strong> version. I ran into a similar issue. It allows you to use id names for the various instances.

I had a login on the sidebar as well as another on a success login page (that had the same sidebar and when the login success was processed my simple login became a profile editor. Obviously I wasnt looking for that) so they were conflicting. I tried that version out and no problems.

-P

I’ll give that a shot, however WebLoginPE probably shouldn’t interfere with core modx functionality.

Quote from: pseudorad10 at Sep 25, 2009, 04:29 PM

To avoid the 2 instances issue when using WebLoginPE, I decided to replace the login with my own snippet that displays the username when logged in, or creates a ’login’ link to my login page. Fairly straightforward stuff here...and with some effort i was able to get the ’simple’ services all working. However, one small issue remains that continues to elude me. As follows:

Assuming a working version of 1.3.1 service simple, user logs in, hits
profile, updates profile and chooses ’save’...

Expect: return to profile with status update message, and
$modx->getLoginUserName() returns value of the ’username’.

Results: return to profile with status update message, and
$modx->getLoginUserName() returns value of ’’.

The function $modx->getLoginUserName() value displays properly on all pages
until you save the profile, then it mysteriously disappears on all pages,
although a user remains logged in and $_SESSION[’webValidated’] remains true.

Any ideas??

Im currently trying to set up something similar - I am looking through documentation at the minute, but if anyone can point me in the right direction that would be great!

Depending if the user is logged in I either want to display ’login’ at the top of the page or the users username if they are already logged in..

Thanks