Developer forum

Forum » Swift » Hide sign in when logged in

Hide sign in when logged in

Alexander Tømmerholen
Reply

Hello,

On a solution using Swift 1.6.1 I`m not able to hide the menu element sign in when logged in. I have tried using permissions but that does not work.

What I want to hide when logged in:


Permissions settings:

Are there any settings I`m missing?


Replies

 
Fredrik
Fredrik
Reply

Hello

I have the same issue. I created a new user in a new usergroup in the BO. The standard DemoUser works, but the new user still has the "Sign in" menu visible.

Best regards,

Fredrik

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Hi Frederik

I cannot reproduce the issue.

Can you show the new user and how it is setup? And the permissions of the login page?

 
Fredrik
Fredrik
Reply

Hello

The user is created in a new group called "Bas" with the default permission "Read".

The group's persmissions is all set to "None", except "Websites", "Shops" and "Languages" that has "Read".

Permissions for login page is attached.

Do you need any more info?

Best regards,

Fredrik

Skärmklipp.PNG
 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Nicolai and Fredrik,

 

We may have found out the core issue. This happened with us when a user was set as an Admin with "Allow backend access" set to true

 

I understand that by default Administrators having Full access, will allow this to happen.

 

I don't know if it's possible to get this to work; meaning a single user having both backend and frontend priveledges without there being conflicts. I regularly find conflicts between them, and have 2 separate users for both backend and frontend, but I see a lot of our customers expecting a single one.

 

Hope this helps.

 

Nuno Aguiar

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Administrator means administrator. We cannot have an administrator that is not administrator. Or what do I not get...?

Why not just make them "non-administrator" and give them the privileges they need? I.e. just set them to "Default user" and then things will work...

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Nicolai,

 

Yep, I agree. I was just sharing our findings too. I tend to explain to customers that having separate users is better. It raises lesser questions and avoids lesser configuration conficts (that's at least been my experience).

 

Maybe it's an matter of Ego. Customers want to know they are an Admin, but then test in the frontend as if they are not and hope that everything is as expected... oh well... at least we know the root cause and it's exposed here for anyone else that needs it.

 

Best Regards,

Nuno Aguiar

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Yeah - then create a group called "Administrators" and add them to that :-)

 
Fredrik
Fredrik
Reply

Hello

But my demo account is a standard (Default) and not a admin and also has no backend access.

I also wonder;

When I go to the permission page for a group I see the list "INHERITED PERMISSIONS" but I can not change any setting. Where can I change that settings and exactly what does they affect? E.g. It only says "Read" but not what that group can read.

The group "Bas" that the demo user is added to has "None" as setting in this table, maybe that has something to do with the problem (too)?

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

You right click the page and choose permissions - so it is page permissions.

Inherited means from its 'parent' - for a subpage the parent is a page, for a root page the parent is the content root, and for the content root the parent is the website. So one of those will be the parent.

BR Nicolai

 

You must be logged in to post in the forum