N 191 intitle datalife engine control panel. Creating a simple module for CMS Datalife Engine (DLE)
Let's talk about the menu on the dle website. More precisely, how to add your own items to the menu, or replace existing ones with new ones. Quite often, beginners who have just installed this CMS have a question: “How can I replace the standard menu items in a standard template with my own?” If, in WordPress, this can be done without editing the code, then in dle the situation is different; you still have to get into the code and figure it out a little. However, there is nothing difficult about adding new items, and I hope you can see this today.
So let's get down to business. First, we need to create items that will later need to be implemented in the dle menu, be it pages or categories. To do this, go to the admin panel and click on the item “list of all sections.”
And then everything depends on the situation. If we need to add a link to a site category to the menu, then go to the “Categories” item, and if we need to create a page to which the menu item will direct the user, then go to the “Static Pages” item. There is no fundamental difference between them, so we will choose one of two options, for example, “Categories”.
A form for creating a new category on the site will appear. Everything is simple there. For what each form field is used, see the image.
Not all fields that are described in the figure are required, but only the first and second fields. And the points that I did not touch on in the image do not relate to categories at all, but relate to global engine settings, such as news output settings dle , and also provide the ability to assign unique template, for each category separately.
After filling out the required fields, at least the first two, click on the add button. This action will create a new category on the site, a link to which we will add to the dle menu. And pay special attention to the second field, where it was necessary to enter an alternative name for the category, which will form the address where the category will be located. In my example, it will look like this: http://site.ru/primer_category/
Now, let's move on to directly adding a new item to the dle menu.
To do this, in the admin panel you need to go to the “Site Templates” section.
And then you need to select one of two files, if used standard template, which contain the menus on the website. The standard template has two types of menus: this, horizontal and vertical. The topmenu.tpl file is responsible for the horizontal menu, and the sidebar.tpl file is responsible for the vertical menu in the left column of the site. Both of these files can be found in the left column of the “Site Templates” section. And when you click on one of them, the code of this file itself will appear in the right column.
After opening the file, we need to correct any existing item to ours. That is, change the name, in this case to the name of the category. And substitute a link to the category itself (alternative name), instead of #. That is, if I replace the “About the site” item, the menu code will look like this:
By analogy, you can change other items in the menu. As for the second, horizontal menu, the situation there is absolutely the same. And of course, everything unnecessary that you don’t need can be removed. And of course, save the edited file.
If you are not sure about something, for example, that you will delete something unnecessary, then just do it so that in case of unforeseen situations it can be restored.
And that's all for me.
This is the current version of CMS DataLife Engine
The following changes were prepared and implemented:
1. The distribution includes three completely new templates. These templates are created using HTML5 standards. They are fully adaptive, both for desktop browsers and for tablets and smartphones. Also, vector graphics are actively used in the layout of the templates, which ensures their high-quality display on HiDPI (Retina) displays.
2. Added a new type of additional fields for publications: \"Uploaded image\". With this type of field, the user is prompted to upload a picture for this news, which will be displayed later when the news is displayed on the site. For this type of field, you can set parameters such as restrictions on the weight and size of the image, whether you need to create a small copy for it, the size of the small copy, and whether to put a watermark on it. Thus, using this type of field makes the process of writing news easier; for example, you can create various types of pictures (posters, screenshots, etc.) and arrange their output in a template, and when adding news, all you have to do is download them in one click.
3. Added a new type of additional fields for publications: \"Uploaded file\". With this field type, the user is prompted to upload a file for this news, which will then be downloaded as an attachment. In the settings of this field, you can set file extensions that are allowed for this field when uploading, as well as the maximum weight of the uploaded file. Thus, using this type of field makes the process of writing news easier, for example, you can create various types of files, including pictures directly for downloading (wallpapers in different resolutions) and arrange their output in a template, and when adding news, only them will remain download in one click.
4. Added a new type of additional fields for publications: \"Switch \'Yes\' or \'No\'\". When writing news, this type of field is displayed as a switch \’Yes\’ or \’No\’ (On or Off). This field displays \’Yes\’ or \’No\’ as a value, depending on what was set when writing the news. However, the main purpose of this field is to manage text and text tags. If the switch was turned on, then the text tags will display the corresponding text, and the text tags will remove it, and vice versa. Thus, using these additional fields, you can easily manage the information displayed on the site in templates, in relation to each specific news. For example, enable or disable the display of any tabs with a description on the page, or organize the display of galleries with screenshots or posters, etc.
5. For additional news fields that have the \"List\" field type, the ability to create individual values that are displayed in the list when adding a publication, and those that are displayed on the site after the user selects them as values has been added. To do this, when adding a field, you need to use the separator \’|\’ in the list of values, for example: Yes|Yes. When writing news, the user will be given the option Yes to select, and the field value will be displayed on the site as Yes.
6. For additional user profile fields that have the \"List\" field type, the ability to create individual values that are displayed in the list when editing the profile, and those that are displayed on the site after being selected by the user as values, has also been added. To do this, when adding a field, you must also use the separator \’|\’ in the list of values, for example Yes|Yes. When editing a profile, the user will be given the Yes option to select, and the field value will be displayed on the site as Yes.
7. The \"Use as cross hyperlinks\" mode for additional news fields has been significantly redesigned and improved. If the field has this option, then the search for news by the field value is based on the complete match of this value in other news, as well as the match of this particular field. For example, if earlier you created the field \"Year of release\", and set the value to 2015, and at the same time you had another field in which, for example, a picture was loaded, the path of which also had 2015, then the old system displayed both news , because the search was carried out exclusively based on the occurrence of the search word. Which led to the fact that news that was not quite expected was shown. Now only those news will be shown for which the \"Year of issue\" field will have the value 2015. No other fields and their values will be taken into account anymore, which allows for a more extensive use of additional fields to organize cross-linking with each other. For example, by year of release, actors, directors, etc. The new search type is automatically applied only to newly added news. If you want old existing news to participate in this search, then you will need to start rebuilding news in the admin panel, in the section \"Rebuilding publications\", and thereby an index of field values will be created for old existing news.
8. For the main template (main.tpl), the ability to display additional news fields in it when viewing the full news on the site has been added. To do this, in this template you can use the same tags as for displaying additional fields in the short and full news templates. These tags are: text, text and
9. For templates that support the display of additional news fields, support has been added for new Text tags, which display the text contained in them if the value of the additional field matches the specified one. And also added the ability to use Text tags, which will display text if the field value does not match the specified one. Where tagname is the name of the additional field, and tagvalue is its value. For example, Male gender, this tag will display the text \"Male\" if the value of the test field is set to \"m\" when writing the publication. This opens up great opportunities for creating different template designs depending on the field values set when writing these publications. For example, by creating a field with the \"list\" type, you can apply different designs depending on the selected item.
10. The display of additional fields when quickly editing publications on the site has been improved; for this purpose, additional auxiliary CSS classes have been added for the editing form, which can be used to design fields during quick editing.
11. When using authorization on the site using social networks, the ability has been added for users to set their personal login for the site, which will be used in the future. The login request is carried out only at the time of the first authorization on the site using a social network and will be used automatically in the future. This innovation will be useful for visitors to your website who do not want to use data received automatically from a social network, for example, when the user’s first and last name is used as a login.
12. Added support for emoticons for HiDPI (Retina) monitors. To do this, two copies of emoticons are used, in normal resolution and in high quality. If the monitor has a normal pixel density, then a regular smiley is displayed on it; if the monitor has a HiDPI (Retina) density, then a high-quality copy of it is displayed. The detection and use of emoticons occurs automatically. To do this, you need to place two copies of the emoticon in the folder with emoticons, for example, with the name smile.gif for a regular emoticon and [email protected] for HiDPI (Retina) emoticon. If there is no high-resolution copy of the smiley, then the output of a regular smiley will be used in all cases.
13. The distribution includes 60 new emoticons. All of them have support for HiDPI (Retina) displays.
14. Added automatic support for emoticons in .png format. Support is also provided automatically. To do this, you just need to copy the files to the folder with emoticons with the extension .png and specify the name of the emoticon in the script settings.
15. Added a new global tag:
(customcomments id=\»1,2,5-8\» category=\»2,3,5-8\» author=\»x\» days=\»x\» template=\»custom\» available =\"global\" from=\"0\" limit=\"10\" order=\"date\" sort=\"desc\" cache=\"yes\")
Which allows you to display comments anywhere on the site in a custom format. This tag is an auxiliary additional output of comments, and can, for example, be used to display the latest comments on the main page of the site in a block, etc.
This tag can accept the following parameters:
id - a list of comment IDs you want to display, separated by commas without spaces. You can also indicate a range of comment IDs using a dash. For example, 1,4-8,11 will display comments with ID 1, comments with ID 4 to 8, and also with ID 11.
category — list of news category IDs from which to select comments, separated by commas without spaces. You can also indicate a range of categories using a dash. For example, 1,4-8,11 will display comments from category 1, categories with id 4 to 8, and also from category 11.
categoryexclude - completely opposite to the category=\"list of categories\" parameter and allows you to display comments whose news does not belong to the categories specified in the parameter. For example, (customcomments categoryexclude=\»2,7\") will display all comments on news items that do not belong to categories and id 2 and 7.
author — specifies the login of the comment author; when this parameter is specified, only comments from the specified author will be displayed. It is allowed to list several authors separated by commas. For example, the tag (customcomments author=\"admin\" limit=\"5\") will display 5 comments by the author with the login \"admin\".
authorexclude - specifies the author logins that need to be excluded from display. Author logins in this parameter can also be listed separated by commas. For example, when using (customcomments authorexclude=\"admin,test\"), comments from all authors will be displayed, except for authors with login \"admin\" and login \"test\".
days - specifies the time period, where x is the number of days for which comments should be displayed. For example, the tag (customcomments days=\"2\" limit=\"5\") will display 5 comments for the last 2 days.
template — template file that will be used when displaying comments; in this case, it will be custom.tpl; if you use several templates on the site, then this file must be present in each template. This template uses tags similar to those you use in the comments display template (comments.tpl).
available - indicates the section of the site in which the requested comments will be displayed. You can combine sections using \"|\", for example, available=\"userinfo|register|main\" will display your comments on the main page, when registering and when viewing the user profile.
from — indicates the number of the comment from which output will begin. The numbering of comments starts from zero. For example, if you want to skip the first comment that matches your conditions, then you need to specify from=\»1\»
limit — specifies how many comments will be displayed.
order — specifies the comment sorting criterion, can take the following values:
date—sorting comments by date, for example, the tag (customcomments order=\"date\" limit=\"5\") will display the five most recent comments.
rating - sorting comments by rating, for example, the tag (customcomments order=\"rating\" limit=\"5\") will display the five most rated comments.
rand - sorting comments in random order, for example, the tag (customcomments order=\"rand\" limit=\"5\") will display five comments in random order.
sort - specifies the sort order of comments. When using the desc value, publications are sorted in descending order, and when using asc, they are sorted in ascending order.
cache - accepts the value yes or no and indicates whether to cache output or not, we recommend caching blocks this conclusion to reduce the load on the server.
All parameters of this tag are optional. It is enough to specify any one parameter. You can also combine various parameters of this tag as you wish.
16. For comment output templates (comments.tpl), support for a new tag has been added (comment limit=\"X\"), which displays the comment text without HTML formatting, while the comment text itself is reduced to the specified \"x\" number of characters. In this case, the text is shortened to the last logical word, and does not break off the text in the middle of the word. This tag will be useful when using custom comments output, using the tag (customcomments...), when you need to display not the entire comment, but only its announcement.
17. For comment display templates (comments.tpl), support for a new tag (news-link) has been added, which displays the URL of the news that belongs to this comment. This tag will be useful when using custom comment display and when showing the latest comments.
18. For comment display templates (comments.tpl), support for a new tag (news-title) has been added, which displays HTML safe title of the news to which this comment belongs. This tag will be useful when using custom comment display and when showing the latest comments.
19. In group settings, the ability to specify which categories are prohibited for viewing by a given user group has been added. This new setting is in addition to the existing one, where you list the categories allowed for viewing. If earlier, in order to prohibit, for example, just one category from a large list of categories, you had to select all available categories, with the exception of just one prohibited category, now you can simply select one prohibited category from the list, and that’s it. The previous setting in the admin panel has also been saved, so you can choose what is more convenient for you, you can select either a list of available categories or simply specify a list of unavailable ones.
20. Added the ability to promote users from one group to another after a certain number of days have passed since registration on the site. To do this, a corresponding setting has been added to the group settings, where you can specify how many days and to which group to transfer the user after his registration. This opens up new opportunities for granting users any rights or privileges on the site.
21. Added the ability to promote users from one group to another when they receive a certain number of news items on the site. To do this, a corresponding setting has been added to the group settings, where you can specify how many news items you need to have and which group to move the user to when he collects a given number of publications. Publications under moderation are not taken into account. Thus, you can provide users who have earned a certain trust with any additional rights and preferences.
22. Added the ability to promote users from one group to another when they type a certain number of comments on the site. To do this, a corresponding setting has been added to the group settings, where you can specify how many comments you need to have and to which group to move the user for a given number of comments. Comments undergoing moderation are not taken into account. Thus, you can provide users who have earned a certain trust with any additional rights and preferences.
23. Added the ability to promote users from one group to another when they reach a certain rating for their publications on the site. To do this, a corresponding setting has been added to the group settings, where you can specify what total rating they need to score, and which group to move the user to when they receive this rating.
24. For templates for displaying comments and personal messages (comments.tpl and pm.tpl), support for formatted display of the number of user comments and publications has been added. For example, when displaying the number of comments 252501, 252,501 will be displayed. This makes large numbers easier to understand.
25. Support for formatted output of numeric ratings has been added for user profile display templates (userinfo.tpl and profile_popup.tpl). For example, when displaying the overall user rating +252501, +252,501 will be displayed. This makes large numbers easier to understand.
26. Added support for a new global template tag: (*Commented code*). This tag is intended for commenting the code; everything enclosed between \"(*\" and \"*)\" will be removed from the template. And it will be absent when displayed on the site. These tags will be useful to template developers for debugging this or that functionality, when you need to temporarily comment out this or that functionality. This tag is global and can be used in all templates.
27. Added automatic reset of the index of similar news when changing the number of displayed similar news in the script settings. Thus, after changing this setting, there is no longer a need to go to rebuild publications and rebuild the cache of similar news there.
28. The ability to specify whether his publications awaiting moderation should be displayed in the user’s profile or not has been added to the script settings. If this setting is enabled, the user can see news in their profile that is awaiting moderation and edit them. If this setting is disabled, then these news will not be displayed in his profile, and the message that he has no publications awaiting moderation will also not be displayed.
29. Changes have been made to the work feedback on the site, if an unregistered user writes on the site. If the user is not registered, then no check is made to check whether the login he entered matches those already registered on the site. Instead, the prefix \"Unregistered user\" is added to his entered name. Thus, the administration or recipient of a letter from the site will easily see that the letter was sent to him by an unregistered visitor to the site. And for the site visitor himself there will be no inconvenient obligation to come up with another name if the name he wrote is occupied by a registered user.
30. Changes have been made to the operation of adding comments on the site, if the comment is written by an unregistered site visitor. If the name he entered matches the registered login, then the prefix \"Guest\" is added to his name. For example, a visitor wrote the name \"Tatyana\", and the site already has a registered login \"Tatyana\", then the comment will be added on behalf of \"Guest Tatyana\". Thereby, there is a visual difference that this user is not registered on the site, and the site visitor also gets rid of the inconvenient obligation to come up with another name. If there is no such name among the registered ones, then the prefix will not be added.
31. Added support for notifications about new comments, for comments that are sent for moderation. Previously, notifications were sent only if a comment was published immediately on the site without being moderated by the site administration. Now notifications will also be sent after the site administration has checked the comment and published it on the site.
32. The ability to search for keywords by a given word has been added to the tag cloud management section in the admin panel. Which makes searching and editing much easier the right word, with a large volume of given words.
34. For the module \"Cross references\" the ability to set a new option has been added: \"Open link in a new window\". Thus, you can set where you open the link you need in the same browser window, or in a new browser window.
35. For mass actions in the \"Cross-References\" module, the ability to assign links to how to open these links, in a new browser window or in the current browser window, has also been added.
36. In the admin panel, in the user management section, a new option \"Exact login match\" has been added when searching for users by login. If this option is checked, the search will be based on an exact match of the login with the one specified in the search. This makes the search easier the desired user with a short login, if a large number of users are registered on the site.
37. Playback of flash video files in .flv format has been reduced to a single player. Now, to play this video, the same player is used as for playing HTML5 video. Thus, all videos on the site have a single visual appearance.
38. For better and higher-quality promotion of publications in search engines, when viewing full news, automatic use of keywords from the tag cloud has been added in a specially generated meta tag for search engines. You can read more about this meta tag on the page https://support.google.com/news/publisher/answer/68297?hl=ru
39. Improved processing of text published in code tags in the news parser. Any intersection of the published code with DLE tags and filters was excluded, which makes it possible to publish the source code in it, without any intervention in the text on the part of DLE.
40. Added support for copying avatars when logging into a website using the social network Odnoklassniki.
41. TinyMCE visual editor has been updated to the latest version. In addition to fixing previously discovered errors, many other changes have been added to this editor. The appearance of the editor has been changed to a more classic one for websites (all functions are presented in the form of buttons, without menus), and the insertion of BB tags for videos and Youtube and others has been improved. In the editor, the insertion and processing of source code examples (tag) has been improved, highlighting of this code has been added directly in the editor, and a convenient window has been added for inserting code examples. The editor has added HTML syntax highlighting when editing HTML source code.
42. Changes have been made to the mechanisms for generating a site map. If any categories are prohibited for unregistered users to view, then these categories and publications from these categories are also excluded from the map.
43. Changes have been made to the code for displaying keywords for the tag cloud, thanks to which there are more opportunities for different design of these tags on the site.
44.Added support for utf8mb4 encoding for MySQL servers version 5.7.x
45. Fixed an issue where Text tags did not work correctly when used together with numbers for which formatted output was applied.
46. Fixed a problem where news was incorrectly displayed using the tag (custom...) with the author and catalog parameters, if several tags were used on the page simultaneously with these parameters, with caching enabled.
47. Fixed a problem with quoting comments that contain HTML tags when using the standard comment editor. Now, when quoting in the editor field, these HTML tags are also inserted, and not their HTML entities.
48. Fixed a problem with receiving letters in UTF-8 encoding for some types of mail services.
49. Fixed a problem where the name of the authors for files uploaded to news was incorrectly renamed if the user login was renamed in the user control panel.
50. Fixed a problem where the news cache was not cleared if it was under moderation and edited by the author of this news on the site.
51. Previously discovered and reported minor errors in the script have been corrected.
The following changes have been prepared and implemented:
1. Control Panel has been completely redesigned. We made it modern, readable and contrasting. Besides visual changes the new design also has a number of functional features. The new control panel has ten color schemes to choose from, not just one, and a special night template designed in dark colors for comfortable work in the dark. You can adjust the width of the sections side bar and width of the whole control panel. You also can enable a full-screen mode when working on devices with small screen sizes, hiding the browser bar and tabs to increase the working space of the panel. Each user of the Administration Panel can configure its custom look, its parameters and the color scheme. A special dual system for storage settings is used to save parameters of the panel. The settings are saved both on the server and locally in a browser providing unique features when using the control panel settings. Server-based saving of settings allows to avoid the "flickering" effect when applying the user's custom design, and also to automatically apply selected settings when using another browser. Whereas storing the settings locally allows you to restore the selected settings after a parameters reset on the server, for example, in case of engine re-installation or after its global update. We hope that you will enjoy the new control panel. You can see a small demo of the new panel in the video above.
5. Now you can enable a function in Static Pages section of Control Panel which allows you to save the location of a user on a website before editing or adding the page. It allows to return user back to the previous location. This feature is useful when there is a large number of pages or setting any search parameters. After editing the user will not have to search or go back to the needed page manually.
6. This feature allows you to choose the action right after you saved a page. You can choose between: "Add another page", "Edit page", "Go to list of pages". It allows you to go to the most frequently used actions in one click.
7. This feature allows you to choose the action during the editing right after the page is saved. You can choose between: "Back to page edit" and "Go to pages list." Thus, users who frequently save text of the page during editing can quickly go on edit after saving.
15. You can exclude certain static pages from the site search results. When adding or editing a page in Administration Panel, you can check "Exclude from search results" option for each static page separately.
16. Now you assign a password or a list of passwords for each static page to view it. If a password is set for a static page, then password will be asked to open the page and it will be opened only if the correct password is entered. The entered password will remain in effect until the user closes the browser, and the password will not be requested again within the same session on the site.
17. Autosuggestion for extra fields which have the type of "cross-references" when adding and editing publications is added. Words list for autosuggestion is obtained from the database. It makes it easier to fill these fields in, and also reduces the probability of an error in words.
18. You can use masks to specify a template for redirects in Redirects module. When specifying URL to perform redirect from, you can specify the "*" character which means that any set of symbols may be instead of "*". E.g., you can specify /page/*/ to set redirect from pages like /page/1/, /page/2/, /page/any text/, etc.
20. For static page templates (static.tpl and other assigned pages), the new tag text is added, which displays the enclosed text as a link to edit the static page for user groups who are allowed to edit static pages. This allows to quickly move to editing the needed page, when there is a large number of static pages.
21. A new parameter "id_as_list" is added for custom articles tag (custom...) that works in conjunction with the "id" parameter, and sorts the publications as they appear in the list. For example, the tag (custom id = "3,4,1,2" order = "id_as_list") will display articles first with ID 3, then 4, then 1, and 2. This feature is useful when you want to display the required articles in a strictly defined order.
22. A new parameter "id_as_list" is added for custom comments tag (customcomments...) that works in conjunction with the "id" parameter, and sorts the comments as they appear in the list. For example, the tag (customcomments id = "3,4,1,2" order = "id_as_list") will display comments with ID 3, then 4, then 1, and then 2. This feature is useful when you want to display the required comments in a strictly defined order.
24. You can allow to attach media widgets in comments using the tags in user group settings. This option is used to allow or deny certain user groups to attach media widgets in comments.
25. Changes have been made to quick editing of articles. Now in quick editing mode only those fields are shown that were previously filled in during article adding or full editing mode. This applies to both the article annotation and full article fields. If the article annotation and full article fields have not been filled in, they will not be displayed in quick edit mode. This feature is useful for those who use only extra fields in articles. They will not see unnecessary fields.
26. You can remove such fields as "article annotation" and "full article" from the article addition template, while retaining all other functionality of editors. This feature will be useful for those who use just extra fields to add articles.
27. A new global tag for the (category-id) templates is added which allows to display the ID of the category viewed by the visitor. This tag will be useful when organizing the menu on the site and when you need to quickly reassign any CSS classes or the names of template files, when you edit articles display templates.
28. A new global tag (category-title) is added for templates, which allows to display the name of the category viewed by the visitor. This tag will be useful when you need to display the name of the category you are viewing.
(category-description) You can limit the output of this information using additional tags , for example, only on the first page of the category.
30. You can use a new "only" value for the "subcat" parameter of the output tag (catmenu ...) of the category menu, which allows to display only subcategories of the specified category. For example, if you use the (catmenu id = "1" subcat = "only") tag, only the subcategories of the category with ID "1" will be displayed. This feature is useful to display only subcategories of a certain category. For example, you can automatically display a list of subcategories from the viewed category using the simple expression (catmenu id = "(category-id)" subcat = "only").
32. Now you can display the uploaded images separately for extra fields of "Image Gallery" type. For this the tag is used in templates, where "X" is the name of the extra field, and "Nr" is the number of image from the gallery. For example, if you apply , then image number two will be displayed and loaded into an additional field named "test". Thus, you can use one field, and at the same time display a preview from the gallery in one picture in article annotation, and full gallery when viewing the full article.
33. Now you can safely use (title) tag in HTML attributes when displaying articles. For example, you can use alt="(title)" !} and the text will preserve the validity of the document if the header contains quotation marks.
34. Support for attaching videos and posts from Facebook has been added for tag.
35. Gzip compression for CSS files used by the engine is added, which allows to significantly reduce the size of CSS files, and therefore to speed up the loading of pages. Compression can be enabled together with the compression of JS files in the engine settings. When you enable compression, only DLE engine’s own CSS files are compressed. To compress your own CSS files of your template, see our article https://dle-news.ru/tips/917-szhatie-css-fajlov-shablona.html
36. Now you can enable automatic reset of the browser cache for CSS and JS files used by the engine after its update. This feature allows the browser to use the newest files after the engine update, not use the old ones from the browser cache.
37. Tag (THEME) is now supported in promotional materials preview in the engine control panel.
39. If the protocol of your site is not specified in the engine settings, DLE will use a secure SSL connection and will generate links to HTTPS protocol starting from this engine version.
40. Preventive measures are added to protect the site from "endless" redirects if only HTTPS protocol is enabled in the engine settings and the server is not configured properly and does not transmit information about the used protocol.
41. Preventive measures are added for the word filter section to protect against accidental deletion of words from the word filter in Administration Panel. Now this action requires confirmation.
42. 403 HTTP code (access is denied) is sent to the browser for personal article bookmarks pages if an unregistered user goes to the bookmark address. Thus the page’s data will not be indexed by the search engines. Search engines are not indexing a page with just one access error.
43. The database load has been significantly reduced when displaying the latest comments on websites with a large number of comments.
44. The display of the tag cloud block is optimized for databases with a large number of articles on the site. The database query is improved and speeded-up.
45. Support for curly braces "(" and ")" in the "Word Filter" module is added and now you can use words containing these symbols in the filter.
46. Articles from the site map are automatically hidden from search engines if access to the article is denied for guests in "Access" tab of the article.
47. Froala and TinyMCE editors have been updated. Previously found issues are fixed in both of them.
48. HTML code parser for published articles is updated.
49. An issue with the incorrect CRON notification of search engines about the site map updates is fixed when the site name was specified without a protocol in the engine settings.
50. An issue is fixed where visual editors could not be displayed on the article publication page if there were "custom" tags on the page.
51. An issue is fixed where the visual editor could not load during quick editing if articles display was done only by (custom ...) tag, without using the main (content) tag.
52. An issue is fixed where the merged text was sent without line breaks in e-mail notifications about new comments or personal messages.
53. An issue is fixed where line breaks were lost in empty lines when using the TinyMCE editor for articles.
54. An issue is fixed where some template tags for static pages were displayed incorrectly when displaying static pages in search results.
55. All previously declared and found small errors are fixed.
Information on the engine installation for clients:
Attention! This information is only available to users with a valid license for DataLife Engine. If you have already purchased the script, you must log in with your account.
If you are not a customer, you can on our website.
“Dark horses” come across not only among people, but also among CMS. One of these “horses” is DLE.
While there is a lot of information about other PHP engines on the Internet, you can only find a few decent materials about this CMS. Let's make this article worthy by telling readers how to install a template on DLE:
Known about unknown CMS
This engine is not as popular on the world Internet as WordPress or Joomla. It is the creation of Russian programmers. Therefore, you can most often stumble upon a site running on this CMS and template for DLE in RuNet.
CMS DLE is positioned by its creators as the basis for the deployment of information portals and blogs. The internal engine system is adapted for heavy loads and has a high degree of fault tolerance:
Like most engines, DLE (DataLife Engine) runs on php and MySQL. The main disadvantage of this content management system is that it is paid. Despite this, DLE ranks fourth in terms of prevalence among resources located in the ru zone. Although most of them (59 thousand sites) use pirated versions engine.
A license for a basic CMS package for a period of 1 year costs RUB 2,190. Its extension for the second year (and subsequent ones) will cost 1,490 rubles. The price of the extended version is 2790 rubles.
In addition to paid versions, there is also a free version. This version of CMS is presented by the manufacturer as trial version engine and basis for creating your first website:
The main disadvantage of DLE is its poor security. Back in 2008, experts criticized CMS for the poor security of its internal system when handling requests. Most likely, this problem has not been eliminated today.
According to Yandex analytical data for 2011, sites that work specifically on the basis of CMS DLE are most often infected. The latest release of the engine at the moment is version 10.3. It was released in September 2014.
Features of the template for DLE
Templates for DLE websites have a number of features that fundamentally distinguish this CMS from other content management systems:
- The engine template structure is built on the basis of TPL files. This greatly simplifies the process of layout and adaptation of the template design;
- The main structure file is main.tpl. All additional template elements ( menu, sidebar) are also specified using TPL files;
- Style decisions are written in two files: styles for the software part are specified in engine.css, and everything else is specified in style.css:
Before installing the DLE template, download its installation package and place it in the templates folder:
Then you need to go to the site’s control panel (file admin.php). After that, in the menu on the left side, select “ Script settings», « System settings»:
At the bottom, in the “General settings” section, go to “ Default site template" Select from the drop-down list required template. After making changes, do not forget to click the “Save" button:
After this, the new template will be activated and the site will change its appearance. But before you put the template on DLE, do not forget to unzip it.
IN CMS DLE unlike others popular systems content management, the installation of the template does not occur from the archive.
Unfortunately, most of the templates for DLE, like the engine itself, are paid. But if you search hard, you can find a couple of decent resources on the RuNet where you can download templates for free. Here are a few of them:
- dle-shablony.net – about 50 different templates are available here for free download. But they are all “lumped” in one general section without sorting by category. Although among them you can find very “strawberry” specimens:
- newtemplates.ru – the site presents a large collection of paid and free templates. All of them are conveniently sorted by thematic headings. But even among the paid ones you can find samples costing $5-10 and with a circulation of only 5 copies. And this will provide the resource with a design with a fairly high degree of uniqueness!
- 10.dle-shabloni.ru is a cool resource with a huge collection of templates for DLE websites. Tags will help you find the ones you need by topic or even color. You can see how the template works using the built-in demo version or in the video played in the Youtube video player window:
Don't forget that each template was developed for a specific version of CMS DLE. Their compliance must be checked before downloading the selected sample.
How to edit a DLE template
Unlike other popular content management systems, DLE has a simpler template design. Thanks to this, editing them is much faster and easier. The administrative part of the engine includes an integrated code editor.
To access this tool you need:
- Go to the site admin panel;
- In the menu on the left, select “ Template management", "Site templates";
- In the drop-down list located in the " Selected template for editing"Install the desired instance and click on the "Run" button:
- After this, the built-in code editor window will appear below. But before you edit the template, you need to select a file to edit. The template file tree is located on the left. After clicking the cursor on the desired source, its contents will be displayed in the editor window:
As you can see from the figure, the tpl file is a regular html, the structure of which is easy to understand. But before editing this code, it is strongly recommended that you familiarize yourself with the design features of the DLE engine.
Technical documentation for CMS DLE is available for review at official website manufacturer.
You can read about all the new features of DLE 12.1 in this article.
DataLife Engine v.12.1 Press Release will tell you about the addition to the advertising module, now the module supports the category function, in this version you can keep track of the number of views of advertising materials and other additions related to advertising management.
It is good that using canonical links is added in the code for all pages of the site, including navigation through sections, viewing the full news, etc. This is a trick to improve SEO optimization of projects, it will eliminate duplicate pages if incorrect links to your site are published somewhere on the Internet, or if for some reason it is necessary to disable control of incorrect CNCs.
For security reasons, a function has been added automatic protection site from uploading code or inserting frames on third-party sites. When you enable this setting, display of your resource will be automatically blocked if it is embedded in an iframe on someone else's site. This way you can protect your website from attacks such as clickjacking.
Another interesting feature for SEO website optimization is the expanded capabilities of the “Metatags” module; now you can set not only meta tags for pages, but also any separate title for the page and page description, which you can later display anywhere in your template.
(Recommended)
Hosting with free SSL certificate for the site, modern equipment on SSD - one of the leaders in quality and low price. In this article we read.
For example about free hosting Without advertising and conditions under DataLife management Engine 12-9.x or any other CMS - this service will help you understand within a month whether hosting is suitable for you or not.
We offer download DLE different versions on http://www.site in the section for everyone without registering (licensed versions UTF 8 and Win 1251).
The main stage of development of version 12.1 has been completed, the release is in testing and pre-release preparation, but in the meantime we invite you to familiarize yourself with the information about what awaits you with the release of the new version.
The following changes were prepared and implemented:
1. Added support for categories in the advertising management module. You can create categories in this module and place your advertising materials in these categories. Headings are displayed at the very top, in front of the list of added advertising materials, in the form of folders. Within the categories themselves, you can also create additional subcategories in an unlimited number. Thus, if you have a large number of advertising materials, you can place them for ease of navigation through them in various sections and subsections.
2. Added the ability to count the number of views for advertising materials, added to the script control panel. Views are recorded only for real users who accessed the site using a browser. Bots crawling the site are not counted. View counting is enabled directly for each banner, so you can count views only for the advertising materials you need. You also have the opportunity to specify whether you want to count all banner views, or only count views from unique users.
3. For advertising materials in the admin panel, the ability to limit banner display has been added based on the number of views it has, and you can disable the banner when it reaches a specified maximum number of views.
4. Added the ability to count the number of clicks for advertising materials added to the script control panel. DataLife Engine automatically intercepts HTML tags published using the tags and automatically records clicks on them. These links do not require any special design; they can lead to any addresses you need. You also have the option to specify whether you want to count all clicks on a link, or only count clicks from unique users.
5. For advertising materials, the admin panel has added the ability to limit banner display based on the number of clicks on your banner, and you can disable banner display when the specified maximum number of clicks on it is reached.
7. Added use of canonical links, in the page code, for all pages of the site including navigation through sections, viewing the full news, etc. This opportunity allows you to increase SEO optimization of sites, and also allows you to avoid duplicate pages if incorrect links to your site are published somewhere on the Internet, or if for some reason it is necessary to disable control of incorrect CNCs.
8. In the category settings in the control panel, added the ability to set by default for a category whether it is allowed to publish news from this category on the main page of the site. These settings are in effect at the time of adding or editing a publication, and if publication on the main page is prohibited for a category, then the corresponding option is removed at the time of adding or editing a publication.
9. In the category settings in the control panel, added the ability to set by default for a category whether comments are allowed for posts from this category. These settings are in effect at the time of adding or editing a publication, and if comments are disabled for a category, then the corresponding option is removed at the time of adding or editing a publication.
10. In the category settings in the control panel, added the ability to set by default for a category whether ratings are allowed for publications from this category. These settings are in effect at the time of adding or editing a publication, and if the use of ratings is disabled for a category, then the corresponding option is removed at the time of adding or editing a publication.
11. In the script settings in the control panel, in the security settings section, the ability to enable automatic site protection from embedding into frames on third-party sites has been added. When you enable this setting, your site will be automatically blocked if it is embedded in an iframe on someone else's site. This way you can protect your website from attacks such as clickjacking.
12. The capabilities of the "Metatags" module have been expanded, This module has been renamed to "Titles, Descriptions, Meta Tags". Now in this module you can set not only meta tags for pages, but also a separate title for the page and a description of the page, which you can later display anywhere in your template. For this purpose, new global tags for templates have been added: (page-title) - displays the title you specify for the page, (page-description) - displays the description you specify for the page. It is also possible to use BB and HTML tags in the page description. Thus, using this module, you can, for example, create and display titles and descriptions for the tag cloud for each tag personally, etc.
13. Added new global template text tags, which display the text enclosed in them if a title for the page being viewed was specified in the “Titles, Descriptions, Meta Tags” module. And also added opposite text tags that display the text enclosed in them if the title for the page being viewed has not been set. Similar tags were also added for the description: text , which display the text enclosed in them if a description for the page being viewed was specified in the "Titles, Descriptions, Meta Tags" module, text , which display the text enclosed in them if there was no description for the page being viewed given.
14. Support for new text tags has been added for the category menu template (categorymenu.tpl), which display the text enclosed in them if the category or news being viewed on the site does not belong to the category from the menu. This tag can only be used inside tags and is used, for example, to display some information (for example links) only for inactive categories from the menu.
15. Expanded capabilities for displaying publications based on the values of additional fields in publications. When accessing the address http://yoursite/xfsearch/field name/field value/, publications will be displayed, as before, containing the specified value in this particular field, if the “use as cross-references” option is set for the field. When you access http://yoursite/xfsearch/field value/, publications containing this value for all additional fields will be displayed. When you access http://yoursite/xfsearch/field name/, all publications in which this specified field is filled in will be displayed.
16. Added the ability to assign to the script settings separate page named 404.html at the root of your site, to display pages for which there is no content. If you enable this setting, instead of the standard system message “Unfortunately, this page is not available to you, its address may have changed or it has been deleted.”, you can display a separate, specially prepared page with a completely separate design. This innovation will be useful for webmasters who want to create a separate design for the 404 pages of their website.
17. The ability to assign an HTTP header has been added to the script settings, from where it is necessary to obtain user IP addresses. This innovation will be useful for sites that use various external proxy servers and do not have the ability to correctly reconfigure the server for them in order to obtain the correct real IP addresses of visitors. For example, when using the cloudflare service and others to protect against DDOS attacks and using a regular hosting plan without access to server settings. Now you can, in the script settings in the admin panel, tell the script where to get the IP address of site visitors from.
18. When deleting a category in the script control panel, the ability to choose what to do with publications that are in this category has been added. You can: “Remove this category from publications”, “Replace the category with another or other categories”, and also “Delete all publications in this category”. Moreover, if a category is deleted or replaced from a publication, only the category being deleted will be removed or replaced. For example, your publication is in the categories “In the world”, “News”, “Popular”, and you, for example, delete the category “In the world”, then for publications located in this category only the category “In the world” will be deleted or replaced, all other categories in the list of these publications will remain in place.
19. A new type of additional field has been added for publications: "Pure HTML and JS." When using this field, DataLife Engine will not interfere with the text written in it and will not filter the HTML code of this text, and also allows pure javascript code to be written in it. This field will be useful when you need to insert some code into the news that does not require a security check, for example, your own player, etc. Attention, given that the script will not filter the text from this field, when creating it, be sure to set restrictions on which groups are allowed to use it. Do not allow its use by ordinary users whom you do not trust, otherwise it may pose a security risk to your site. 
20. For additional publication fields, which have the "Use as cross-references" option, the ability to specify a separator for link data has been added. You can specify either individual characters or HTML code as a delimiter. Previously, a comma was used as a list separator; now you can set your own personal separator for each field, which allows you to create your own unique output design for each field in the template.
21. Added support for Yandex Turbo technology for regular RSS channels, without using the inclusion in the settings of the RSS stream type as "Yandex news", for this, support has been added for displaying the full news tag (full-story) for any type of RSS stream. The standard template /templates/rss.xml has also been updated, which demonstrates what a template with full Yandex Turbo support should look like. Similarly, the ability to customize an RSS template for Yandex Zen technology is fully supported.
22. Added the ability to reply to comments when viewing all the latest comments on the site, if support for tree comments is enabled in the script settings. Thus, you can, for example, quickly respond to comments received on the site without going into each news item, due to the fact that some heavy scripts have been transferred to delayed loading and independent of page rendering. These scripts are loaded into the browser in parallel with page rendering and are launched only after the page is completed in the browser. Which visually ensures faster page display.
24. Added an option for users who are not registered on the site, send complaints to the site administration about news and comments, just as such an opportunity existed previously only for registered users.
25. Added the use of schema org micro markup to display ratings with the "Evaluation" type. The use of this micro-markup allows for full news, when displayed in search results on Google, to also display the publication rating.
26. Added automatic detection of the orientation of photos when uploading them to the server, based on meta-information contained in graphic files. If the original photo was upside down, then when it is uploaded to the server, the script will also automatically rotate it to the desired position. This eliminates the need to additionally edit pictures on a computer if the camera was rotated when taking photographs.
27. Added the ability to automatically notify the site administration about the arrival of new news from users, which is under moderation (if this is enabled in the script settings), if the news was added from the script control panel. Previously, a notification was sent only if a post was added directly from the site.
28. If the user edits a publication in the control panel, which was previously published on the site, but according to the settings of his group, he is prohibited from publishing without moderation, or is not allowed to publish in all categories, then the site administration will also be sent a corresponding e-mail notification that this news is awaiting moderation.
29. Changes have been made to the operation of the module bread crumbs(Breadcrumbs) on the website. If news from a certain category is viewed, then for the category in which the user is directly located, this category will be displayed in the form of plain text and not a link. Only categories higher in the hierarchy will be displayed as a link, or a link to this category will appear if, for example, the user has gone further in navigating pages in this category. Thus, this innovation allows you to avoid cyclic links of pages to themselves.
30. For the "Cross-references" module in the control panel, added two new replacement areas for links. You can optionally specify a replacement only in static pages, and you can also select a replacement in static pages, news and comments.
31. For the "Search and Replace" module in the control panel, the ability to mass replace text in surveys for publications and in voting on the site has been added.
32. Added the ability to delete all publications, awaiting moderation from a specific user. To do this, in the user management section, click on the number of his publications and select the appropriate menu item.
33. Added the ability to delete all comments, awaiting moderation from a specific user. To do this, in the user management section, click on the number of his comments and select the appropriate menu item.
34. A formatted output of the number of different counters (views, publications, comments) has been added to the script's admin panel. The output of these counters is carried out in formatted form, separated by a space of hundreds, thousands, millions, etc. Which gives a more visual representation and perception of these numbers.
35. For templates for displaying comments and adding comments (addcomments.tpl and comments.tpl), support has been added for new tags text - displays text in the tag if the news belongs to the specified categories, as well as tags: text - displays text in the tag if the news does not belong the specified categories. This way you can set different design displaying comments and adding comments for publications from different categories.
36. Added support for word declinations for the tag displaying the number of votes, which were exposed for rating publications. For example, you can use (vote-num) review||a|s. Previously, this was not available for this tag, because... it contains HTML code, not just a number.
37. If the script settings enable the use of the site only by HTTPS protocol , then cookies will also be sent to the server by the browser only via the HTTPS protocol and will be automatically blocked if the regular HTTP protocol is used.
38. Added control of incorrect CNC for static pages, the publication text of which is divided into several pages. If specified incorrect number page, an automatic 301 redirect will be made to the starting address of this page.
39. For RSS import of publications, support has been added for importing pictures from the enclosure tag containing the image for the publication. If the short description in the RSS stream is just text, and the picture is given in it as a separate tag, then when importing the short news, the picture for this publication will also be added to the very beginning.
40. Added support for redirects to receive full news when using RSS import of publications. If the link from the RSS feed is a redirect for further transition to the full text of the news on the source site, then DataLife Engine will automatically follow this redirect and take content from the final source. Thus, receiving complete news will be of higher quality than before.
41. Changes have been made to the operation of tags and. In case for specific publication It is prohibited to use and add comments, then these tags will also hide the content in them.
42. If comments are allowed for publication, but at the same time, according to other settings, the user or group of users was prohibited from publishing comments, then a message about this will not be displayed at the end of all comments, but in the place where in your template you define the display of the form for adding a comment with the tag (addcomments), thereby you can determine the location of this message on your site.
43. For authorization using the Odnoklassniki social network, the ability to automatically receive the user’s E-mail has been added, provided that the application itself has received the appropriate rights from Odnoklassniki. Attention, by default Odnoklassniki does not provide rights to receive E-mail, and to obtain appropriate access you must additionally contact social media. network to allow receiving e-mail. If permission is received, DLE will also automatically import the e-mail address.
44. Improved system for calculating image proportions when creating small copies. This creates a more correct and high-quality reduced copy.
45. Improved search system for publications when enabled in the script settings, a simple search type. The new algorithm allows you to more accurately and correctly find publications.
46. Improved system for controlling the appearance of duplicate pages, when viewing all the latest comments on the site.
47. Optimized processing of additional publication fields when displaying short publications, as well as during the operation of the module for displaying popular publications.
48. Visual editors TinyMCE and Froala have been updated to the latest versions. A number of identified errors in these editors have been corrected.
49. Added support for inserting hidden text tags for the TinyMCE editor, using the corresponding button in the editor.
50. When using the Floara editor for comments, added the ability to quickly download and insert images into comments. You can either click on the insert picture icon and select a file to upload, or simply drag the picture file from your computer into the editor field with the mouse, after which the picture will be automatically loaded and inserted at the cursor position in the editor.
51. Small changes have been made to the layout of the script control panel, aimed at eliminating some layout errors and improving interaction with the control panel.
52. The library for sending mail from the site has been updated to the latest versions, as well as a mobile device detection library.
53. Fixed an issue where the and tags were not processed in the post preview.
54. Fixed an issue where meta tags for social media were generated incorrectly. video and audio networks, if the video was published in additional. fields and consisted of playlists and descriptions of video and audio files.
55. Fixed a problem where, under certain situations and server settings, previewing publications might not work when adding publications from the site.
56. Fixed an issue where dynamic loading of comments did not work, if this is enabled in the script settings, and the tag (jsfiles) is placed at the very bottom of the site.
57. Fixed an issue where displaying the latest comments did not work, in case viewing of certain categories was prohibited for a certain group.
58. Previously discovered and reported minor errors in the script have been corrected.