Dynamic Attribute: Show no longer works

[sitestreet]

I had some output set to only display when the user is logged in (it’s actually a ‘Log Out’ link in the nav menu) which was working fine but now isn’t so I’m assuming it’s a bug introduced in the latest version.

The code generated is this:

<li class="nav-item" dmx-show="$_SESSION['siteSecurityId']">
  <a class="nav-link" href="logout.php">Log out</a> 
</li> 

I thought I was going mad and then wondered if it’s a new bug.

[Hyperbytes]

Not sure if it is a solution but have tried setting a full condition rather than an implied one:

$_SESSION[‘siteSecurityId’] != Null

or even

$_SESSION[‘siteSecurityId’] != ‘’ (in case then session is set but to empty string now rather than null)

[sitestreet]

Thanks, @Hyperbytes, but I’ve already tried that. I also output the session variable to check it had a value and it does.

[sitestreet]

For now I’ve hard-coded some PHP:

<?php if(isset($_SESSION['siteSecurityId'])) { ?>
                          <li class="nav-item">
                            <a class="nav-link" href="logout.php">Log out</a> 
                          </li>                             
<?php } ?>

but I’d rather do it the Wappler way.

[Teodor]

@sitestreet

dmx-show="$_SESSION['siteSecurityId']"

But that's not the way to check this. You cannot check session like this with this syntax in a dmx-show attribute.
You need to access the logged user ID from the security provider step in your server action, which returns the logged user details, just like explained here:

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

Nice work @George and @Teodor! I created a user registration system with login functionality and security restrictions in about 1 hour following your guide, with no prior knowledge of how it worked. One thing I noticed, and perhaps it was user error, was that I wasn’t getting data back from my query in Step 17 until I went in and added the columns that I wanted returned, thereby changing my SELECT * to a SELECT UserID, Name, EmailAddress FROM Users WHERE UserID = :security_identity I thought…

[Hyperbytes]

I think this may be the source of the confusion

@Teodor

So, for example in your custom PHP script you’ll be referring to it like: $_SESSION['siteSecurityId']
The same is valid for the other server models.

[Teodor]

Yes but you use this wrapped with PHP tags, in some PHP code - not just randomly placing it on your pages.
The same way you cannot just place echo('test') on the page and expect it to work without the PHP tags around it.

[Hyperbytes]

you are of course correct, using the security provider rather than pho sessions is the correct way to do it

[Teodor]

This should also be working:

dmx-show="<?php isset($_SESSION[‘siteSecurityId’]) ?>"

[sitestreet]

Brilliant. That was the instructions I needed:

https://community.wappler.io/t/getting-details-of-the-logged-in-user-and-binding-them-to-your-page/2850/2

I’ve gone through all the steps and can now set it to show when logged in and it’s all done the Wappler way. Happy days.

Huge thanks.

[Hyperbytes]

I suppose to be technical the correct way in Wappler is via site security and reference to the sitesecurity.identity variable as described in the below post rather than using session variables:

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…

[psweb]

Agreed @Hyperbytes, rather use the correct Wappler way and avoid all the confusion while at the same time making sure all your bindings work correctly and everything is accessable within the interface instead of using custom php and then having to try get Wappler to know what are doing.