Problems using server actions from another project

[Dave]

In your log in Action you can use the security provider ID to filter the user via a simple query.

Logged User Session Name

When you setup a log in system, a session is being created by the log in script and it contains the logged user identity. This session and its value can be accessed by any other script by calling it (in your scripts). The name of session storing logged in user identity depends on your security provider name. It’s name is: securityProviderName + Id so if your security provider is called siteSecurity like here: [Screenshot_65] Then the session name will be: siteSecurityId So, for example in …

Getting Details of the Logged In User and Binding them to your page

Personalise your clients browsing experience by knowing who they are. You can get the logged in user details by filtering the user table in your database, by the logged user ID. This gives you access to all the details of your logged in user, allowing you to personalise the visitor experience by greeting them by name, or any captured data you might have about them.   Step 1: First you need to create a new server action: [image]   Step 2: We call it userDetails: [image]   Step 3: Ri…

That should see you on your way nicely Andrew.