- CMS Made Simple Development Cookbook
- Samuel Goldstein
- 571字
- 2021-04-09 21:13:17
Will a Tag Solve My Problem?
As in the previous recipe, you know that we have three different possibilities for extending CMS Made Simple and solving a problem: User-Defined Tag, Tags, and Modules. Deciding which of these is the best approach, however, requires additional knowledge about the strengths and weaknesses of each technique.
This recipe will help you examine your problem and consider whether creating a Tag is the most appropriate solution.
How to do it...
The criteria for deciding to use a Tag to extend CMS Made Simple are quite similar to the criteria for a User-Defined Tag.
To figure this out, consult the following list, and determine if each item applies to the problem you are trying to solve. Feel free to write down a list of your answers (yes/no).
- Can your problem be solved with Smarty logic in your page template?
- Are you trying to solve a problem that requires multiple actions? An example of multiple actions would be both displaying a form and processing its results.
- Will you need to support localization and internationalization to solve your problem? For example, if your code will be displaying messages, will the messages need to be translated into multiple languages?
- Will your solution require an Administration panel?
- Do you need to create new database tables or set up new preferences to solve your problem?
If you answered "no" to all of the above questions, either a Tag or a User-Defined Tag would be a viable approach. To decide whether a Tag would be better than a UDT, consider the following questions:
- Will you want to share this solution with other people so they can install it into their own CMS Made Simple sites, or will you want to reuse this code yourself on other sites?
- Do you want your code to display help text in the Admin area, so site administrators understand what parameters are available and what the code does?
- Will your solution serve as a Smarty modifier? A Smarty modifier is a function that reformats a variable for display, for example,
{$variable|uppercase}where the modifier("uppercase")serves to transform the variable ("$variable").
If you answer "yes" to any of these three questions, you should write a Tag instead of a User-Defined Tag.
How it works...
A Tag is a way to connect a Smarty tag to some PHP code. The PHP code can do anything. Like in the case of User-Defined Tags, there are very few things that cannot be done in CMS Made Simple using Tags.
Because Tags are so versatile, the best way to determine if they are the ideal approach is by disqualification. We ask questions about the few things for which Tags are not ideal, to see if any of those things match our requirements. If none of them match, then the problem could be solved by either a Tag or a User-Defined Tag. To make the decision between those two approaches, we consider a few other criteria that will steer us in the right direction.
Let's consider the disqualifying questions again and examine why they would encourage us to use a different approach. The first five questions are the same as they were for User-Defined Tags.
Now, let's consider the three things that differentiate a Tag from a User-Defined Tag:
See also
- Will a User-Defined Tag Solve My Problem recipe?
- Will a Module Solve My Problem recipe?
- Create a "Hello World" Tag recipe
- Adobe Photoshop 網(wǎng)頁(yè)設(shè)計(jì)與制作標(biāo)準(zhǔn)實(shí)訓(xùn)教程（CS5修訂版）
- jQuery Mobile First Look
- Final Cut Pro短視頻剪輯入門(mén)教程
- VRP11/3ds Max虛擬現(xiàn)實(shí)制作標(biāo)準(zhǔn)實(shí)訓(xùn)教程
- ASP.NET Core 3從入門(mén)到實(shí)戰(zhàn)
- After Effects印象 影視高級(jí)特效光影篇
- 深入淺出WebAssembly
- CINEMA 4D新手快速進(jìn)階實(shí)例教學(xué)
- 中文版Photoshop平面設(shè)計(jì)入門(mén)教程
- 企業(yè)微信公眾平臺(tái)開(kāi)發(fā)實(shí)戰(zhàn)：再小的個(gè)體也有自己的品牌
- 中文版Photoshop CS5基礎(chǔ)培訓(xùn)教程（移動(dòng)學(xué)習(xí)版）
- Joomla! 1.5 JavaScript jQuery
- AutoCAD快速自學(xué)寶典（2019中文版）
- 深度學(xué)習(xí)圖像識(shí)別技術(shù)：基于TensorFlow Object Detection API和OpenVINO? 工具套件
- Joomla! 1.5 Multimedia