I have recently studied the secondary development of CMS in the Empire/after some time of exploration/finally gained some experience on MVC/architecture.

: This article mainly introduces the recent study of the secondary development of the Empire CMS. after a period of exploration, I finally got some experience about the MVC architecture, if you are interested in the PHP Tutorial, refer. Because the Empire is a medium-and large-sized cms

There are many things and functions that are not actually usable. for security reasons, we recommend that you delete them.

As a traditional cms structure, the following mainly analyzes the underlying idea of this cms.

After the cms is registered as a member, many operations are performed in the Member Center.

This operation will eventually be transferred to the DoAction. php file.

Next, let's take a serious look at what is included in the php file corresponding to each of the remaining operations.

In general, the php file in the process of this operation is called the name of this operation and then suffixed with a php

This php file is named selfDoAction. php, and this file generally involves the database.

After finding the database you want, the problem is basically half solved.

You can clearly see that there is an SQL statement in selfDoAction. php that obtains the field corresponding to the enewsmemberadd table.

If you need to add information for this operation, you can add the desired field in this table.

The rest is the select field.

Then The call method is OK.

It indicates that the problem is quickly solved. I am very happy ~

The above introduces the secondary development of the CMS in the empire. after some time of exploration, I finally got some experience on MVC/architecture, including some content, if you are interested in PHP tutorials.