WebLoginPE (1.3.0): Advanced WebUser Management and Extended Profiling.

WebLoginPE explodes &disableServices at the comma into an array.
At every TYPE checkpoint and at every SERVICE, WebLoginPE checks to see if that type or service is in the array of disabled services. If it is, a return statement is issued and no code is executed.

Ok I got it working.. only on registration that is...
i used $_POST[’username’] but then ofcource for editing this would not work. mm maybe i put this in the wrong spot: $this->Username = $_POST[’username’]; ? where in de code do i set this?

it looks like $this->Username never makes it into the CreateUserImage()

...I have a "View Profiles" document with the snippet call: [!WebLoginPE? &type=`users`!]

When you click on the username to view more details, I get a "404" page. I can’t find how to get the detailed information to show up. Am I missing a parameter or do I need something else?

I can create accounts with international characters with WebLoginPE, but when trying to log in with that name just get "The username you entered does not exist."

Anyone else seen this?

<?php
print 'POST Data:<pre>'.print_r($_POST, true).'</pre>';
?>

See what shows up for the username.
If $_POST[’username’] is showing up as expected, then there is a problem with WebLoginPE.

Array
(
    [username] => Ådi
    [password] => ******
    [stayloggedin] => 
    [serviceButtonValue] => login
    [service] => 
)

The username you entered does not exist.

The username is there:

Quote from: ejcross at Sep 12, 2007, 10:09 AM

...I have a "View Profiles" document with the snippet call: [!WebLoginPE? &type=`users`!]

When you click on the username to view more details, I get a "404" page. I can’t find how to get the detailed information to show up. Am I missing a parameter or do I need something else?

No, I don’t think you are missing anything. A few things come to mind when you are getting a 404 page instead of the requested data.
#1) a snippet is throwing an error. If you are logged into the manager, you MAY see the error details, otherwise, MODx tries to hide error reports for users as much as possible, so if something breaks.... send them to the 404!

#2) Access Permissions on the page. Are they set to "All Document Groups (Public)"?

#3) Page caching. In the "Page Settings" tab of this document is the "Cacheable" box checked? I always have my pages with dynamic content (like the users page) set to cacheable unchecked (not cacheable).

#4) Clear the cache. Manager > Site > Clear Cache.