How to ask credentials before showing index in user SC

[streagle]

In the staff and admin sections the loginform.tcl shows before everything else and asks for user & pass.
But in the User SC the user can see the index screen with widgets and so on, and on the side a login box.
How can I make the User SC to have the same login behavior as the Staff and Admin SCs?

[craigbrass]

Staff CP -> Users -> Manage Groups -> Guest
allows you to specify no for each of the modules / sections. Once you do this, they will not be able to view them until they login.

[streagle]

It seems I don't have a guest Usergroup. I created one named "Guest" and denied all access. But still when I open index.php of the user SC I see all the widgets, and knoledgebase articles and so on..

[streagle]

As far as I can see only the View Tickets widget hides when you logoff and shows when you login. Except that the screen is identical if you login or logoff.

[Jamie Edwards]

Hi there,

You might be looking in the wrong place, or you might have deleted the default Guest account (which I do not think you can do). Follow these screenshots:

1)



2)



3)

[streagle]

Both "Guest" and "Registered" groups are missing ^^
It appears we have done the impossible.

[Jamie Edwards]

Can you confirm you're looking at Manage Groups under the staff control panel and not under the admin control panel?

[streagle]

Yes. It appears one of my colegues has deleted them probably from mysql interface.

I'm looking at /staff/index.php?_m=core&_a=manageusergroups&offset=0

[craigbrass]

I am suprised the user frontend is still working without these user groups to be honest. You will need to readd these using the "Insert Group" link. Select first type as guest and next registered.

[Jamie Edwards]

Ok, I am surprised you have it working at all!

Here are the missing entries you should re-add and edit:

INSERT INTO `swusergroups` VALUES (1, 'Guest', 'guest', 1, 0, 0);
INSERT INTO `swusergroups` VALUES (2, 'Registered', 'registered', 1, 0, 0);
INSERT INTO `swusergroupsettings` VALUES (145, 1, 'perm_canviewregister', '1');
INSERT INTO `swusergroupsettings` VALUES (146, 2, 'perm_canviewregister', '1');
INSERT INTO `swusergroupsettings` VALUES (148, 1, 'perm_canviewsubmitticket', '1');
INSERT INTO `swusergroupsettings` VALUES (149, 2, 'perm_canviewsubmitticket', '1');
INSERT INTO `swusergroupsettings` VALUES (151, 1, 'perm_cansubmitticket', '1');
INSERT INTO `swusergroupsettings` VALUES (152, 2, 'perm_cansubmitticket', '1');
INSERT INTO `swusergroupsettings` VALUES (154, 1, 'perm_sendautoresp', '1');
INSERT INTO `swusergroupsettings` VALUES (155, 2, 'perm_sendautoresp', '1');
INSERT INTO `swusergroupsettings` VALUES (157, 1, 'perm_canchangepriorities', '1');
INSERT INTO `swusergroupsettings` VALUES (158, 2, 'perm_canchangepriorities', '1');
INSERT INTO `swusergroupsettings` VALUES (160, 1, 'perm_canviewknowledgebase', '1');
INSERT INTO `swusergroupsettings` VALUES (161, 2, 'perm_canviewknowledgebase', '1');
INSERT INTO `swusergroupsettings` VALUES (163, 1, 'perm_canviewdownloads', '1');
INSERT INTO `swusergroupsettings` VALUES (164, 2, 'perm_canviewdownloads', '1');
INSERT INTO `swusergroupsettings` VALUES (166, 1, 'perm_canviewtroubleshooter', '1');
INSERT INTO `swusergroupsettings` VALUES (167, 2, 'perm_canviewtroubleshooter', '1');
INSERT INTO `swusergroupsettings` VALUES (169, 1, 'perm_canviewnews', '1');
INSERT INTO `swusergroupsettings` VALUES (170, 2, 'perm_canviewnews', '1');

[streagle]

It is working because it appears he only deleted the rows from swusergroups.
And after I inserted the guest usergroup back it worked.

[craigbrass]

So it is all sorted now?

[streagle]

Well, no.
I managed to hide everything, but the project leader wants the login for the user section to be the same as the ones for staff and admin sections.
Any ideas on how that can be done?

[craigbrass]

Well once you have disabled all the module links from showing, you could edit the templates to do this.

[Jamie Edwards]

I suppose it could be done with a LoginShare module... but then all your support desk users would need staff accounts - and would thus be able to login to the staff control panel. Is this what you want?