Questions about registration and logon of website front-end members

Some questions about website front-end member registration and logon are currently required by the company to be an enterprise site. the front-end personnel can register members and select the type of member to be registered. depending on the type of registration, after logon, the functions of members are different and different user Center interfaces are displayed. Members can post images, texts, and other information on their websites. After the release, the background administrator will review it. after the review is successful, it can be displayed on the website. How can we implement such similar functions. I graduated from college and used to work on templates. Currently, this CMS only supports background login and news publishing. So I would like to ask you on the forum to give great guidance to your younger brother. thank you !!!!!

Reply to discussion (solution)

Which framework do you plan to use or implement the native code?
Let's see if you are working on a set of templates. you should also be familiar with the background.

Which framework do you plan to use or implement the native code?
Let's see if you are working on a set of templates. you should also be familiar with the background.

I used DUXcms. I have never used a framework before, but I looked at canphp. because duxcms is based on canphp, there are too few tutorials on this framework and cms on the Internet. But the boss asked to use it. the boss said that the extended functions can also be written using native PHP.

This is a good solution. We use permission control. different registration types are actually different permission Group roles. each group of roles maintains a set of templates in the background.

This is a good solution. We use permission control. different registration types are actually different permission Group roles. each group of roles maintains a set of templates in the background.

Can you give me more details ......

Simply set the type of the registered member to "type". during registration, set the value (such as 1, 2, 3, and 4) according to the registration type ), when logging on, determine the interface for which the type value is assigned.

I understand what the train of thought is, but how can I upload an article after login, and the background can be reviewed? after the review is passed, it can be displayed on the foreground

Simply set the type of the registered member to "type". during registration, set the value (such as 1, 2, 3, and 4) according to the registration type ), when logging on, determine the interface for which the type value is assigned.

I understand what the train of thought is, but how can I upload an article after login, and the background can be reviewed? after the review is passed, it can be displayed on the foreground

Add a field to the document published by the user to identify whether the document has passed the review. if it is not displayed on the front-end, it will not be displayed.

Add a field to the document published by the user to identify whether the document has passed the review. if it is not displayed on the front-end, it will not be displayed.

Well, how can I use this review field as the background administrator? I have now added a simple judgment on the front-end template, which is a little difficult. Please give us a detailed tutorial ..........

Add a field to the document published by the user to identify whether the document has passed the review. if it is not displayed on the front-end, it will not be displayed.

Well, how can I use this review field as the background administrator? I have now added a simple judgment on the front-end template, which is a little difficult. Please give us a detailed tutorial ..........

The background administrator review is to change the ID field. for example, if the user's post is initialized to 1 (not reviewed), the background administrator changes the status to 0 (reviewed) when the user clicks review ), in the front-end presentation, you can add an article with the identification field 0 in the select statement based on this field.

Add a field to the document published by the user to identify whether the document has passed the review. if it is not displayed on the front-end, it will not be displayed.

Well, how can I use this review field as the background administrator? I have now added a simple judgment on the front-end template, which is a little difficult. Please give us a detailed tutorial ..........

The background administrator review is to change the ID field. for example, if the user's post is initialized to 1 (not reviewed), the background administrator changes the status to 0 (reviewed) when the user clicks review ), in the front-end presentation, you can add an article with the identification field 0 in the select statement based on this field.

Oh, can you tell me that this code needs to be written into that folder ?? I used this cms, including module, model, themes, and admin, and the module, model, and themes files. I can understand that admin controls all the pages and functions of the website background. The details are a bit messy. MVC vulnerabilities

Is someone here .......