Some questions about the registration and login of the website foreground member

Now the company requires to do a business station, the front desk request can register members, and can choose to register the type of membership, according to the different types of registration, login after the member's function is not the same, and display a different User center interface. Members can post some information such as pictures and text on the website. After publishing the background administrator for review, audit success can be displayed on the site. May I ask how this similar function should be implemented? I graduated from college, before is to let dry template work. And now use this set of CMS only background landing and news class release function. So I would like to consult the Forum on the guidance of the Big Brother, thank you!!!!!

Reply to discussion (solution)

Which framework or native code are you going to implement?
See you say is the work of the template, then you should have familiar with the backstage bar

Which framework or native code are you going to implement?
See you say is the work of the template, then you should have familiar with the backstage bar

I used the DUXCMS, previously did not use the framework, but looked at canphp, because Duxcms is based on canphp, this framework and CMS in the online related tutorials too little. But the boss, the boss said the extended function can also be used in native PHP to write

This is a good implementation ah, with permission control to achieve, different registration type is actually different permissions group role, each group of roles in the background to maintain a set of templates.

This is a good implementation ah, with permission control to achieve, different registration type is actually different permissions group role, each group of roles in the background to maintain a set of templates.

Could you elaborate on it?

The simple point is the type of the registered member, the registration of the type to give it a value (such as 1, 2, 3, 4, etc.), log in to determine the type value to its corresponding interface.

Thinking of what I understand, but after landing how to implement can upload articles, and backstage can be audited, after approval can be displayed in the foreground

The simple point is the type of the registered member, the registration of the type to give it a value (such as 1, 2, 3, 4, etc.), log in to determine the type value to its corresponding interface.

Thinking of what I understand, but after landing how to implement can upload articles, and backstage can be audited, after approval can be displayed in the foreground

Add a field to the user's post to identify whether it is approved and not to show it at the front desk.

Add a field to the user's post to identify whether it is approved and not to show it at the front desk.

Well, this audit field, the background administrator how to use it, I have done in the foreground template plus a simple judgment what, this is a bit difficult. Would you please give us a detailed tutorial on this?

Add a field to the user's post to identify whether it is approved and not to show it at the front desk.

Well, this audit field, the background administrator how to use it, I have done in the foreground template plus a simple judgment what, this is a bit difficult. Would you please give us a detailed tutorial on this?

Background Administrator audit is to change the identity field, for example, the user published at the time of initialization is 1 (not audited), the background administrator click on the audit to change the status of 0 (has been approved), the foreground display when the field in the SELECT statement to add the identification field of 0 of the article to display on it.

Add a field to the user's post to identify whether it is approved and not to show it at the front desk.

Well, this audit field, the background administrator how to use it, I have done in the foreground template plus a simple judgment what, this is a bit difficult. Would you please give us a detailed tutorial on this?

Background Administrator audit is to change the identity field, for example, the user published at the time of initialization is 1 (not audited), the background administrator click on the audit to change the status of 0 (has been approved), the foreground display when the field in the SELECT statement to add the identification field of 0 of the article to display on it.

Oh, can you tell me that this code has to be written into that folder?? I use this set of CMS inside have module,model,themes and admin, and Admin also have module,model,themes file. I can understand that the admin control is the site background pages and features. The details are a bit messy. MVC's a hole.

Is there anyone in the wood?

