Recently I have been studying the secondary development of Empire CMS/after a period of exploration/finally gained some experience about MVC/architecture.

Since Empire is a medium-to-large cms

There are many things and functions in it that are actually unusable. Due to security issues, it is recommended that you delete them

As a traditional cms structure, the following is the main analysis An idea at the bottom of this set of cms

After registering as a member of this cms, there are many operations in the member center

Then this operation will eventually be transferred to the file DoAction.php

Then next, we will You have to carefully look at what is included in the php file corresponding to each remaining operation item. Generally, the php file in the process of this operation is called the name of the operation, and then suffixed with php. We name this php file. For selfDoAction.php, this usually involves the database. If you find the database you want, then the problem is basically half solved.

You can clearly see that there is a sql statement in selfDoAction.php to obtain the corresponding field in the enewsmemberadd table

So if you need to add information for this operation, you can add it to this table The desired field

All that is left is to select this field

and then call it through the Empire’s own <?= field name?> method and it’s OK

It means that the problem is almost solved, I am very happy~

The above introduces the recent secondary development of empire cms/after a period of exploration/finally gained some experience on MVC/architecture, including aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials. .