Generally speaking, secondary development mainly involves modifying the interface and adding functions
Let’s talk about modifying the interface first
MVC architecture program, in the interface, basically calls data.
There are three common interface data structures
1. It is a business-side or control-side data-driven interface. Basically, whatever data is output from the background is what data is displayed on the interface. The troublesome thing about this is that if you want to replace the template, the knife will move a lot, unless there is no need to replace the template. If the data on the control end is not modified, the interface design will be more restricted.
2. It is interface-driven data, and the interface customizes the call data. Most cms basically do it this way. Data is obtained through tags or by defining a general PHP call data function. This is more friendly to the interface design, but it will be more troublesome to cut the picture and cover the code.
3. The third method is a bit more difficult, which is to define the front-end calling module through the WYSIWYG model in the background, and define the data through system configuration or manual configuration, and then generate html data, which can be read by the front-end in one go , just set a reasonable cache interval. Like Taobao and Shopex, this is the model that puts greater pressure on backend development.
shopnc’s program belongs to the first type, with a background data-driven interface. Therefore, if you want to change the interface, you usually need to change the controller and the view. It is best to record the modified files. Otherwise, it will be very troublesome if the source files are replaced in future upgrades.
The URL of shopnc is usually like this
http://localhost/shopnc/shop/index.php?act=show_groupbuy&op=index
The act parameter represents the controller, and op represents the name of the business function in the controller
Looking back at the directory structure of shopnc, we go to the controller directory to find show_groupbuy.php. This is the business logic of the controller
Just take a look at the code
<span>class</span> show_groupbuyControl <span>extends</span><span> BaseHomeControl { </span>...<span> } </span>
The name of the controller followed by a Control string and inherited from BaseHomeControl
And op is the function in the show_groupbuyControl class
<span>/*</span><span>* * 默认跳转到进行中的团购列表 </span><span>*/</span> <span>public</span> <span>function</span><span> indexOp() { </span><span>$this</span>-><span>groupbuy_listOp(); }</span>
The name is composed of the op parameter in the url plus the Op string
If you want to change the data displayed in the foreground, you need to find the corresponding controller and function and modify the code
The templates at the front desk are also regular
The functions of the folders under the templates/default directory have the following meanings:
buy Buy function templates, such as shopping cart, order and other templates
css style folder
home The templates for the front-end display function modules are all here
images Template picture folder
layout Layout folder, if you want to find the header files of each functional area, they are here
member Member Center Template
seller Seller Center Template
sns sns function template
store Seller store template
Go to the corresponding folder to find the relevant file template to modify the view logic
It may be a bit confusing to find the corresponding view at first, because the view and the controller do not correspond, but it is easier to find based on the op parameter. Of course, it is recommended to find it from the controller code
Find the corresponding op function
At the end of the function, find words similar to Tpl::showpage('index');. Such words mean that the view of index is called from the corresponding folder, so we find index.php which is the corresponding view. Filed
If there is no word Tpl::showpage('index');, it is usually because other functions are called or the view file is not output, such as directly outputting a string or outputting json.
After you find the view file, you need to find the corresponding data display module before you can modify it.
Let’s first go back and find the corresponding controller and look at the code. We find the homepage file, taking group purchasing as an example
<span>//</span><span>团购专区</span> Language::read('member_groupbuy'<span>); </span><span>$model_groupbuy</span> = Model('groupbuy'<span>); </span><span>$group_list</span> = <span>$model_groupbuy</span>->getGroupbuyCommendedList(<span>array</span>(), <span>null</span>, '', '*', 4<span>); Tpl</span>::output('group_list', <span>$group_list</span>);
Except for the first sentence of the comment, you can guess it without looking at it. It calls the language file
The second sentence is to call model. The location of model is in data in the upper directory, and the file name of the model file is Model('groupbuy'); groupbuy plus .php suffix
The third sentence calls the function in the model to obtain the desired data
The fourth sentence is to assign the obtained data to the variable group_list in the template
We open the view file and find group_list to locate the location we are looking for in the template. The templates are all pure PHP syntax and can be modified directly. Remember to back up!