Landing Page Permissions for regular users are set to 0, and permissions for administrators are set

This is not divided into numeric values and strings. You used session, when you set up session, if it's session="0"It's a string, and if it's session=0, it's a numeric value. You only need to use the same type for comparison as you do for setting.

As. session="0"

0 is a normal user, 1 is an administrator, and 2 is a superuser.

These 3 are, of course, numerical ones.

You're in the program"0" indicates an administrator"1"Represents a normal user, and then make a judgment after submission, if your jradiobutton is 0, read the database, select to get the username and password that are identified as 0, and determine whether the one you entered is consistent.

The effect you're trying to achieve isn't

When you enter a user name, determine whether the user is an administrator or a student, and then the radio button below is selected.

If so, you can use AJAX technology to query the identity of the user based on the user name, and then use a ternary expression to determine whether it is the selected value under the radio button.

It is judged according to the three conditions of user name, password, and identity identification.

Look at the level of the account you are logged in to now is not at the administrator level. It prompts you that your account level is insufficient. Admin level required.

User permissions are also set in the table of the library, for example, administrators use 1 to dedicate to ordinary users, and ordinary users to denote 0.

After looking up the table, select * from the table name, and then determine if(user permission==1){}else{}

Generally, a system architecture will be separated: a list of permissions, a table of roles, a table of users, a user corresponds to a role, and a role can use multiple permissions, and each permission refers to the function of adding or deleting or querying or modifying certain data in the system.

Now to answer your question, the user logs in, determines what role it is, and then determines how many permissions there are under that role (whether it has permission to display a certain panel or if so) and that's it.

You can add a field to the table to record the user's permissions.

For example, the value is 0 for a normal user.

The value is 1 Admin.

The value is 2 Super Admin.

The value of this field is found when the user logs in.

You make a separate user rights form, and before entering this page, determine the identity...

Search for the names of the two panels in the disigner file and find a way to delete the line if there is panel2. Then find the end, there will be a way, add panel2 to it, and you're good to go.

The reason for this is that one panel is treated as another sub-control.

su root

Then enter the password to root permissions.

Join the root group. Or open the terminal and type sudo or su root

Add a column to the user table of the database to distinguish different levels of permissions, for example, the value of the level column int has 1,2,3,5....If level=1 is usually used in Jianyehu, declassify in turn and then write a very simple function to judge Sun Zhiyi, and add this function to verify on each page.

This is to do permission filtering is simpler with tags and databases, according to different login users, to display the content that can be displayed.

I quote a point from asp, build a user table, each different user has different permission value, the smaller the flag authority, the greater the authority, then when calling data or form initialization, if the permission value of this form is lower than the permission value of the access user, the data cannot be accessed, or the form cannot be called out!

Add a property to the user table in the database and call it for the time being"Permissions"bar. If the manager's username is JL, the password is PWD, and the permission is 1, then when logging in, the permission value should be determined according to the username and password, and then the permission value should be followed to enter different forms.

Note: Examples of permission settings are: Manager --- Permissions: 1 Administrator --- Permissions: 2....

That's it!

After verifying the identity, isn't it all over with the visible properties of the control?