Parameter for Disabling Profiles?

I’m trying to do a site where all the user can do is use a standard login to get to documents on the other side of the login. I don’t need profiles,
which means I don’t want the users to be able to create a profile, edit a profile, view a profile, delete a profile, or anything else with a
profile. I assume that’s going to be in the &disableServices= parameter. I can’t find all of the individual services that can be disabled anywhere
so I am not sure what to disable. Help?

Quote from: stjaxn at Dec 03, 2008, 04:20 PM

I’m trying to do a site where all the user can do is use a standard login to get to documents on the other side of the login.

It’s not completely clear what you want.

Do you mean "get to" documents in the Manager or the front end of the site?

If you mean the Manager, you wouldn’t need WLPE at all (unless you need it for something else). You can set Manager User roles for each user and just have the users log in as Manager Users (like you do) and see a limited Manager.

If you mean the front end, you can just use WebLogin and then use the Personalize snippet to show a different menu to logged on users to let them access the documents (if that would do what you want).

I want to use WebloginPE for users to log in...forget what happens after logging other than what relates to profiles. I just don’t want them to have any access to profiles at all.

Well, a buddy showed me how to do it...and it was actually pretty easy.

I created a chunk called no_profile and called it in the WebloginPE snippet:

&successTpl=`no_profile`

Then simply took the default successTpl chunk and modified it by removing the Profile button from the page.

<div id="wlpeUser">
<div id="wlpeUserInfo">
<div id="wlpeWelcome">
<img id="wlpeMyProfileImg" src="[+user.photo+]" alt="[+user.username+]" title="[+user.username+]" height="100" width="100" />
<p id="wlpeWelcomeParagraph">Welcome back [+user.username+]!</p>
</div>
<p id="wlpeLoginCount">You have logged into [(site_name)] [+user.logincount+] times now.

Your last login was [+user.lastlogin+]</p>
<blockquote>
[+user.comment+]
</blockquote>

</div>
<form id="wlpeUserForm" action="[~[*id*]~]" method="POST">
<fieldset id="wlpeUserButtons">
<button type="submit" id="wlpeLogoutButton" name="service" value="logout">Log Out</button>
</fieldset>
</form>
</div>

Maybe this will help some other noobs like me that don’t have the level of experience to understand some of the answers we get.

You do realise that users can still get to their profile page by simply adding &service=profile (or &service=viewprofile) to the url ?

You can disable services by using the &disableServices parameter. You can find which services are available in the webloginpe documentation (assets/snippets/webloginpe/docs/views.html). For instance

[!WebLoginPE? type=`simple` &disableServices=`profile,saveprofilesimple,deleteprofilesimple` ~]

I agree with BobRay though, I don;t quite understand why you are not just using the standard WebLogin snippet instead if you are not using any of the extended functionality of webloginpe.

Quote from: TobyL at Dec 21, 2008, 06:01 AM

You do realise that users can still get to their profile page by simply adding &service=profile (or &service=viewprofile) to the url ?

You can disable services by using the &disableServices parameter. You can find which services are available in the webloginpe documentation (assets/snippets/webloginpe/docs/views.html). For instance

[!WebLoginPE? type=`simple` &disableServices=`profile,saveprofilesimple,deleteprofilesimple` ~]

I agree with BobRay though, I don;t quite understand why you are not just using the standard WebLogin snippet instead if you are not using any of the extended functionality of webloginpe.

That was actually my initial question. I asked what parameter needed to be in the disable services deal. I never got an answer to that question, so I had to figure something else out.