Home > CMS Tutorial > Empire CMS > Summary of basic issues in the secondary development of Imperial CMS

Summary of basic issues in the secondary development of Imperial CMS

silencement
Release: 2019-11-25 13:37:03
forward
2307 people have browsed it

Summary of basic issues in the secondary development of Imperial CMS

Many Imperial CMS users often conduct secondary development of Imperial CMS due to personalized functional requirements and other reasons during use. They also encounter many problems. Now, Common questions are summarized as follows:

1. First check the front desk submission flow chart and its remarks:

http://bbs.phome.net/showthread-34-118212-0.html

2. The way ECMS processes information is basically a process like this:

①Form submission enews=?
②The information processing script page receives the enews value and selects references based on its value File, and processing function
③ Processing function for processing, and refer to the relevant processing function to process the information content according to the process and enter, update, delete data
④ According to the situation, use the printerror() function to terminate the function and continue running downwards. , and print prompt information, return to the page;

3. According to the prompts in 2, insert some functions that cannot be provided by the background:

① If the function is outside the information processing function flow, then You can reference files or insert processing functions on the form processing script page;
eg: Feedback is sent to the email address http://bbs.phome.net/showthread-13-117813-0.html
Note: In fact, feedback is sent To the mailbox is not a sufficient example, because if the feedback content is not completed or is unsuccessful, there is no equivalent judgment in the referenced feedback sending mailbox file; this program will not be perfect; possible situations are: Feedback The content is not entered into the database, but is sent to the mailbox; of course, there is no problem in doing so when the customer does not need the ECMS background feedback content and it is equivalent to the feedback content received by the mailbox.
② If the customer requires peer-to-peer information, then add the reference file of the "Feedback Sending Mailbox" before the information processing function returns the success message;
③ It involves a large number of functional additions, so you can consider citing the file on the form processing page , and insert the function in the reference file into the function body that needs to be inserted;

4. Why not write the secondary function directly in the function body, but use the reference file:

①No It is easy to manage secondary development files;
②Writing code in the source code function body will cause inconvenience in future upgrades;

5. In what folder should I put my secondary development files?

ECMS There is no special folder set up for the second version. You can set up two directories respectively under the e directory and the e/admin directory to place your new files for the second version. For example, my settings are as follows:

e/cmsextends non-backend related file directory
e/cmsextends/js JS directory
e/cmsextends/css CSS directory
e/cmsextends/Mail non-backend related new PHP file related to Mail
e/ admin/cmsextends New file directory in the background
The following is the same as e/cmsextends

6. Secondary document requirements:

Maintain good secondary document habits, which is conducive to code rewriting and The upgrade of the program includes the following:
①New file code content comments
②New file function description
③Modified file description
④Other memo notes

7. User documentation and plug-in installation documentation

The installation documentation is basically the content of the secondary document. The usage documentation introduces how to use the functions!

The above is the detailed content of Summary of basic issues in the secondary development of Imperial CMS. For more information, please follow other related articles on the PHP Chinese website!

Related labels:
source:www.word666.com
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template