Frequently Asked Questions About Using ALite CMS
Notes:
– all actions with page templates are described in relation to the interactive page builder of the ALite CMS system.
The easiest way is to add the following lines in the view:
The module views are specified in the mod.ini file in the parameters amanager (for the administrative area) and umanager (for the user area). For example, for the "News" module, it is indicated:
amanager = "/_modules/news/anews.php"
umanager = "/_modules/news/unews.php"
To change the view, create a new file and specify it in mod.ini in the corresponding section. For instance:
umanager = "/_modules/news/my_view_news.php"
It is recommended that you do not modify existing views to preserve the possibility of subsequent updates.
The templates created in the page builder are set as follows:
• if necessary, upload templates to the server in the folder /your_site_root/_themes/theme_name/templates/;
• edit field Template in sections of the site that will use this template;
• name template tmpl_main you can not specify because it is used by default if no other template is specified or inherited;
• when specifying the default template, it must be borne in mind that nested sections inherit the template of the parent section;
• left-click on the page builder icon of the desired section or open the page builder from the menu and go to any section that will use the new template;
• in the page builder menu do Save (saves page layout service files on the server) and Apply (directly creates/modifies the page template for use in the user part);
• perform action Clear cache in the administrative part (if you do not perform this action, the new template may not display correctly until the next cache update);
• after performing these steps, the new template should be displayed in the user part for all sections using this template.
Follow the steps in How to install/use ready-made templates, for each (!) used template available in your configuration.
There are two ways to create a new page builder template:
Method 1. Enter the name of the template in the field Template in the desired section. Open this section of the site in the page builder. This will automatically create a new blank layout with the previously specified name. To use it on the site in the page builder menu, do Save and Apply.
Method 2. Perform an action in the page builder Save as.... A copy of the current open layout with a new name will be created. Follow the steps for the new template How to install/use ready-made templates.
Blank mockup with name tmpl_main It is created automatically when you open the page builder. To use it on the site in the page builder menu, do Save and Apply. The created template will be used by default for all sections of the site that do not have or do not inherit other templates. To create additional templates, see How to create a new template.
The final template file is a standard php-file and can be created in any environment that supports working with php-scripts. The finished template must be located in the folder /your_site_root/_themes/theme_name/templates/ and indicate it in the appropriate sections of the site.
It is still recommended that you use the page builder even in this case. First, create a page layout as close as possible to what you want in the page builder, display all the necessary data, and then finalize the resulting php file, modify it with other means to meet your requirements. This will ensure the correct output of data generated by php templates, plugins, etc..
In this case, it is necessary to take into account that the template created or modified by other means is most likely to be inoperative in the page builder.
Most likely, the user part uses data from the stored cache. In most cases, after editing data, changing settings, etc. the cache is flushed automatically, but this does not always happen. Without fail, it is reset only after the time specified in the system constant u_cache_timeout (cache storage time in the user part). You can force the cache to be reset at any time from the administrative part by performing the action Clear cache. You can completely disable caching by setting a constant value u_cache_timeout equal to 0.
Cache data is created and updated when the corresponding page is opened. Therefore, for each page, the creation or last update time of the cache will be different.
Page Layout - this is a set of files for the page builder containing a description of the page itself and its individual elements. The layout consists of 3 files that are created automatically, should not be changed manually and are used only by the page builder:
1. Pattern_name_maket.ini - contains a general description of the html page as a whole.
2. Pattern_name_tplsit.ini - contains a description of the editable internal content of the individual elements.
3. Pattern_name_tplsphp.ini - contains a description of the connected php-templates of individual elements and properties passed through php-templates.
Page Template - this is a php-file named pattern_name.php, generated by the page builder command Apply template. This is an executable file that generates an html page and is used only in the user part. If you create/modify an html page template outside the page builder, you should use this file.
In the administrative part, go to the menu Tooks → Settings, bookmark System. Set constant u_modules_title_show (show module headers in the user part) respectively in No or Yes.
Icons for groups of modules are displayed automatically if the constant a_menu_image_show (display pictures in the administrative part menu) has the meaning Yes. Just upload a PNG or GIF image and file name gm_module_group_name to folder /your_site_root/_images/. For example, an icon for a statistics group has a file name gm_statistic.png.
If the module is installed correctly and works, then most likely the reason is the incorrect setting of administrator rights. Go to Accounts → Administrators group in the administrative part and set the necessary rights to the corresponding group of administrators.
If the module is installed correctly and works, then most likely the reason is the incorrect setting of user rights. Go to Accounts → User Groups in the administrative part and set the necessary rights to the corresponding user group. Unauthorized users belong to the default group guest.
© ALite CMS |