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, for beginners who have just installed this CMS, the question arises: “How to replace the standard menu items in the standard template with your 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 bit. However, there is nothing difficult in adding new items, and I hope you can see this today.
So, let's get down to business. To begin with, we need to create items that 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 it all depends on the situation. If we need to add a link to the site category to the menu, then go to the “Categories” item, and if we need to create a page that the menu item will direct the user to, then go to the “Static Pages” item. There is no fundamental difference between them, so we will choose one of the two options, for example, "Categories".
A form for creating a new category on the site will appear. Everything is simple there. What each form field is used for, see image.
Not all fields that are described in the figure are mandatory, but only the first and second fields. And the points that I did not touch on the image do not relate to categories at all, but to global engine settings, such as dle news output settings, and also provide the ability to assign a unique template for each category separately.
After filling in 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 register an alternative name for the category, which will be the address at which 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 "Website Templates" section.
And then you need to select one of the two files, if a standard template is used, in which the menus on the site are registered. There are two types of menus in the standard template: this, and both 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 will appear in the right column.
After opening the file, we need to fix any existing item on 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 site” item, then the menu code will look like this:
By analogy, you can change the rest of the menu items. As for the second, horizontal menu, the situation is exactly the same there. And of course, everything 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 superfluous, then just do it so that in case of unforeseen situations it can be restored.
And that's all for me.
Hello friends. I spend almost all of my time. Since most of my sites are built on CMS DLE, I have to work a lot with this engine. I have said before that developers are not friends with SEO, and in general they have never heard such a word, but it turned out to be even worse than it could be. I even prepared a whole series of posts dedicated to the "ossification" of the national engine (see in the category).
But today I would like to talk about such an important thing as the html sitemap for DLE. No matter how much I searched the Internet for a normal card module, I did not find it. There are, of course, several solutions, but all of them do not give the desired result at all, and sometimes even cause harm. I had to write the module myself, or rather entrust the implementation of my “wishlist” to professionals. I express my deep gratitude to Alexander Fomin for his enthusiasm and incredible speed of work.
The sitemap module for DLE that I am about to introduce to you meets all the requirements of seo and is extremely easy to install.
A complete list of modules for DLE from Alaich "a:
SiteMap - HTML sitemap generation module for DLE
Original name: sitemap
CMS Compatibility: DLE 8.2- 10.6
Spreading: Free, As Is, when distributing a link to the source is required
Current version: 2.2 (from 05/08/2014)
Purpose: Output an unordered list with links to all publications, categories and static pages.
Peculiarities: Visual embed code generator. Detailed settings for the principle of displaying all site elements - news, categories, static pages - the number of displayed elements, sorting principle and sorting order, displaying elements as a link or in plain text, the ability to include / exclude specific elements.
Description and configuration of the HTML sitemap module for DLE
Friends, June 3, 2012 is a big day, a brand new sitemap version 2.0 has been released. We are raising the usability bar of our module to a new level. We (I hope you, too) liked the visual code generation system implemented in the system and we decided to implement it in the sitemap module. Now you do not need to read manuals and descriptions of all functions and their values - just go to the admin panel, specify a few values and that's it - the module is ready to go!
In addition to the above, I would like to list a few more important features:
- the module is fully cached;
- the module uses the DLE API;
- the map does not display publications that have not passed moderation, as well as those planned for the future;
- the presence / absence of CNC, as well as the type of CNC are taken into account;
- such a subtlety is provided - if someone has been working with the DLE engine for a long time, then he remembers that in the early versions there was no CNC at all, and then it appeared, but only of one type (the same as type 3 is now being formed). So this is also provided for in this module - new publications are displayed with a url, the CNC type of which is selected in the admin panel, and old ones, respectively, with the url of the CNC of the old type.
Despite the appearance of a visual generator, I suggest that you familiarize yourself with the mechanics of the module.
The module is inserted into the main.tpl template using the tag:
(include file="engine/modules/sitemap.php?param1=value1¶m2=value2")
param1= — module parameter, value1 — parameter value. Module settings come after the sign? and separated by &.
Insert example (displays a sitemap with a list of static pages and news from categories with id=2,3,4):
(content)
(include file="engine/modules/sitemap.php?show_static=1&need_cats=2,3,4")
In order for the sitemap to be displayed on a separate page, the (include ...) tag must be enclosed in , and the (content) tag must be enclosed in . After that, the module will be available at http://site.ru/sitemap/
After any changes to the parameters and their values, it is necessary to clear the cache in the admin panel.
Module parameters passed via tpl when inserting:
- need_cats - a list of id categories separated by commas for display in the map
- exc_cats - list of id categories separated by commas, excluded from the map
- need_news — comma-separated list of id articles to display in the map
- exc_news - comma-separated list of article ids to be excluded from the map
- it is pointless to specify these parameters at the same time
- need_static — comma-separated list of static page ids to display in the map
- exc_static - list of id static pages, separated by commas, excluded from the map
- it is pointless to specify these parameters at the same time
- cats_as_links - show category names as links (1 or 0)
- show_static - show static pages in the map (1 or 0)
- cats_sort - category list sort field (field from dle_category table)
- cats_msort - category list sorting direction (ASC or DESC)
- news_sort - sorting field for the list of articles (field from the dle_post table)
- news_msort - direction of sorting the list of articles (ASC or DESC)
- static_sort - sort field for the list of static pages (field from the dle_static table)
- static_msort - direction of sorting the list of static pages (ASC or DESC)
- There are 2 sorting options:
- ASC - ascending (alphabetically)
- DESC - descending (in reverse order)
- if the field and sorting order are not specified, the specified category settings or standard DLE parameters are used
- cats_limit - maximum number of subcategories to display
- news_limit - the maximum number of output articles from the category
- static_limit - the maximum number of displayed static pages
Notice none of the above settings are required, you can not specify anything at all - just insert the tag (include file="engine/modules/sitemap.php") - then the default settings will be used.
Sitemap Appearance and Style Classes
Optionally, it is possible to change the appearance of the site map, for this we open the style file (style.css) of our template and prescribe the classes described below.
List of sitemap CSS classes:
Sitemap_categories - element
- category list
- category list
.sitemap_items - element- list of articles
- list of articles
.sitemap_static_pages - element- list of static pages
- list of static pages
Root - a class for the above elements located at the root of the list
Sitemap_categories a - element with category name
.sitemap_categories span - element with category name
.sitemap_items a - the element with article title
.sitemap_static_pages a - element with static page nameInstalling, uninstalling and updating the sitemap module on DLE
Module installation
- Unpack the archive with the module;
- Copy the contents of the uploads folder (except /templates/) to the server;
- Place the contents of the uploads/templates/Default/ folder in your template folder;
- Run the file http://site.ru/sitemap_installer.php and follow the instructions;
- Delete the sitemap_installer.php file from the server;
- Go to the admin panel, select the SiteMap module and generate the code;
- Open your template's main.tpl file and find:
Rewrite Engine On
Add below:
$metatags =<<
Add above:
if ($do == "sitemap" ) ( $nam_e = "Sitemap" ; $metatags [ "title" ] = "Sitemap ($config["home_title"]) "; $metatags["description"] = "Sitemap ($config["description"]) "; $canonical = "" ; ) if ($do == "sitemap") ( $nam_e = "Sitemap"; $metatags["title"] = "Sitemap ($config["home_title"])"; $metatags["description"] = " Sitemap ($config["description"])"; $canonical = ""; )
- The installation process is completed - the sitemap is available at http://site.ru/sitemap/
Removing a module
- Upload the sitemap_uninstaller.php file to the server (to the folder where DLE is installed);
- Run the http://site.ru/sitemap_uninstaller.php file and follow the instructions;
- Delete all module files downloaded during installation;
- Revert all changes to the engine files (main.tpl and .htaccess) made during installation;
- Don't forget to delete the sitemap_uninstaller.php file.
Module update
- Download the new version of the module from the page https://website/blog/post/1974
- Unpack the archive with the module.
- Copy the contents of the upload folder (except for the sitemap_installer.php file and the /templates/ folder) to your server, answering "Yes" to your FTP client's questions about replacing existing files.
Attention! To upgrade from v.1.x to v.2.x:
It is necessary to completely copy the new files from version 2.x to the server, if the names match, confirm the replacement. After that, you need to run http://site.ru/sitemap_installer.php and follow the instructions. This completes the update.Download HTML SiteMap module for DLE
Version history (History Log)
- v.2.2 - 08.05.2014
- Completely redesigned module design for all versions of DLE.
- Minor bugs fixed and improvements made. When updating, be sure to follow the step with editing the engine.php file in the update instructions.
- v.2.1.1 - 17.04.2014
- The module code has been updated to be compatible with the new DLE settings file format version 10.2 and higher.
- v.2.1 - 08.10.2012
- Fixed a bug in the code generator.
- Fixed typos in admin panel.
- v.2.0 - 03.06.2012
- Added installer.
- There was an admin panel with a code generator for inserting into a template.
- v.1.2 - 02.06.2012
- DLE version control introduced.
- The module is now compatible with the DLE 8.2-9.6 line.
- v.1.1 - 02.11.2011
- Fixed bugs with some module functions.
- v.1.0 - 16.03.2011
- Official release.
FAQ - answers to frequently asked questions
Q: Why do I need two sitemaps xml and html? What is their difference? Can they be used at the same time?
A: These are two completely different entities: the xml sitemap is intended only for search engines. The html sitemap is for users to navigate the site. They can and should be used at the same time.Q: What sitemap should be added to the Yandex and Google webmaster panel?
A: Search engines need to “feed” exactly the xml sitemap, and not the sitemap that this module creates.Q: Which sitemap can be linked to on the site (for example, in the footer)?
A: You only need to link to the html sitemap, i.e. the one that is created by this module and is available at http://site.ru/sitemap/Q: I got the following error, what should I do?
Fatal error: Cannot redeclare class Sitemap in /.../engine/modules/sitemap.php on line 55
A: Use the alternative installation of a sitemap through static pages - the method is described hereQ: Does this module work on DLE 10?
A: Yes, everything is working fine. But if you have any difficulties, then there is another alternative. Thanks to the user under the nickname Ryan - the method is described hereQ: I have a lot of publications on the site, and all these links are displayed on one page. This is crap, Yandex swears!
A: Yes, Yandex swears. To reduce the number of links on a page, use the news_limit parameter to limit the number of news output (see the list of parameters for details).Q: How many links on the map page can/should be displayed?
A: From the official response from Yandex support: the recommended number of links in the html sitemap should not exceed 3000 links.Q: But what about dividing the sitemap into pages? Please do.
A: Pagination of the site map is not implied by the database structure and module logic. Pagination is not expected in the near future.So I told you everything, please download, test and write reviews. If you find any errors - write, we will correct everything as quickly as possible. Also, if you have any wishes regarding the functionality, improvements, also write, we will discuss everything and do it!
DISCLAIMER Recently, this module has been distributed on various sites dedicated to DLE, under other names, with changed code, removed / changed copyright, etc. But, nevertheless, signs that this is exactly this module and developed by Alexander Fomin remain. So - I do not bear any responsibility for distributions downloaded from other sites.
"Dark horses" come across not only among people, but also among CMS. One of these "horses" is DLE.
If there is a lot of information about other php engines on the Internet, then only a few worthy materials can be found 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 global Internet as WordPress or Joomla. It is a creation of Russian programmers. Therefore, you can most often stumble upon a site running on this CMS and a template for DLE in Runet.
CMS DLE is positioned by the creators as the basis for the deployment of information portals and blogs. The internal system of the engine is adapted for heavy loads and has a high degree of fault tolerance:
Like most engines, DLE (DataLife Engine) is based on php and MySQL. The main disadvantage of this content management system is its payment. Despite this, DLE occupies the fourth position in terms of prevalence among the resources located in the ru zone. Although most of them (59 thousand sites) use pirated versions of the engine.A license for the basic configuration of CMS for a period of 1 year costs 2190 rubles. Its extension for the second year (and subsequent ones) will cost 1490 rubles. The price of the extended version is 2790 rubles.
In addition to paid versions, there is also a free one. This version of the CMS is presented by the manufacturer as a trial version of the engine and the basis for creating your first site:
The main disadvantage of DLE is the weak security. Back in 2008, experts criticized CMS for the low security of its internal system when dealing with requests. Most likely, this problem has not been fixed today.According to Yandex analytical data for 2011, most often sites that work on the basis of CMS DLE are infected. The latest release of the engine at the moment is version 10.3. She came out in September 2014.
Features of the template for DLE
Templates for DLE sites have a number of features that fundamentally distinguish this CMS from other content management systems:
- The engine's template structure is based on TPL files. This greatly facilitates 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 defined using TPL files ;
- Style decisions are written in two files: styles for the program part are set in engine.css, and everything else is in style.css:
Then you need to go to the site control panel (admin.php file). Then select "" from the menu on the left side. Script settings», « System settings»:
At the bottom, in the section " General settings" go to the item" Default site template". Select the required template from the drop-down list. After making changes, do not forget to click the " Save":
After that, the new template is activated, and the site will change its appearance. But before putting the template on DLE, don't forget to unzip it.V CMS DLE unlike other popular content management systems, the template is not installed from an archive.
Unfortunately, most of the templates for DLE, like the engine itself, are paid. But if you search well, then in Runet you can find a couple of decent resources where you can download templates for free. Here are a few of them:- dle-shablony.net - there are about 50 different templates for free download. But they are all “dumped” in one general section without sorting by category. Although among them you can find absolutely “strawberry” specimens:
- newtemplates.ru - the site presents a large collection of paid and free templates. All of them are conveniently sorted into thematic headings. But even among the paid ones, you can find samples worth $ 5-10 and 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 sites. Tags will help you find among them the ones you need by subject or even by color. You can see how the template works using the built-in demo or in the video playing in the Youtube video player window:
Do not 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 templating scheme. Thanks to this, their editing is much faster and easier. The toolkit of the administrative part of the engine includes an integrated code editor.
To access this tool you need:
- Go to the site admin panel;
- From the menu on the left select " Template Management"," Site templates ";
- In the drop-down list located in the field " Selected template for editing"Install the desired instance and click on the" Run" button:
- After that, the built-in code editor window will be displayed below. But before editing the template, you need to select a file to edit. The template file tree is located on the left. After clicking on the desired source with the cursor, its contents will be displayed in the editor window:
Technical documentation for CMS DLE is available for study 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 rubric function, in this version you can keep track of the number of views of advertising materials and more additions related to advertising management.
A good one, possibly using canonical links, has been added to the code for all pages of the site, including navigation through sections, viewing the full news, etc. This is a feature to improve the SEO optimization of projects, eliminate duplicate pages if incorrect links to your site are published anywhere on the Internet, or if for some reason it is necessary to disable the control of incorrect CNC.
For security reasons, a function has been added to automatically protect the site from uploading code or inserting frames on third-party sites. When this setting is enabled, your resource will be automatically blocked if it is embedded in an iframe on someone else's site. This way you can protect your site from attacks such as clickjacking.
Another interesting feature for SEO site optimization is the expanded capabilities of the "Meta tags" module, now it will be possible to 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. We read in this article.By the way, if you need a high-quality one with a free SSL certificate, a favorable tariff plan and a secure provider, this promo code provides a 5% discount on ordering a domain and / or hosting
A460-09C2-059C-5161
For example about free hosting Without advertising and conditions running DataLife Engine 12-9.x or any other CMS - this service will help you understand within a month whether hosting is right for you or not.
We offer download DLE different versions on http://www.site in the section for everyone without registering (licensed versions of 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 for now, we invite you to familiarize yourself with the information about what awaits you with the release of the new version.
The following changes have been prepared and implemented:
1. Added support for headings in the ad management module. You can create headings in this module and place your advertising materials in these headings. Headings are displayed at the very top, before the list of added advertising materials, in the form of folders. In the rubrics themselves, you can also create additional subheadings in an unlimited number. Thus, with a large number of advertising materials, you can place them for ease of navigation through them, in various headings and subheadings.
2. Added the ability to account for the number of views for promotional materials added in the script control panel. Views are counted only for real users who accessed the site using a browser. Bots crawling the site do not count. View counting is enabled directly for each banner, so you can only count views for the ads you need. You also have the option to specify whether all banner views should be counted, or only views from unique users should be counted.
3. For promotional materials in the admin panel added the ability to limit the display of the banner based on the number of views it has, and you can disable the banner when it reaches the specified maximum number of views.4. Added the ability to account for the number of clicks for advertising materials added in the script control panel. DataLife Engine automatically intercepts HTML tags published using tags and automatically keeps track of clicks on them. No special design of these links is required, they can lead to any address 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 in the admin panel, the ability to limit the display of a banner based on the number of clicks on your banner has been added, and you can disable the display of a banner when the specified maximum number of clicks on it is reached.
7. Added use of canonical links, in the code of the pages, for all pages of the site, including navigation through sections, viewing the full news, etc. This feature allows you to increase the 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 you need to disable the control of incorrect CNC.
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 valid 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 a rating is allowed for publications from this category. These settings are valid at the time of adding or editing a publication, and if the use of a rating 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, added the ability to enable automatic protection of the site from embedding in frames on third-party sites. When this setting is enabled, your site will be automatically blocked if it is embedded in an iframe on someone else's site. This way you can protect your site from attacks such as clickjacking.
12. Expanded the capabilities of the "Metatags" module, this module has been renamed to "Headings, 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. To do this, 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 allowed 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 a tag cloud for each tag individually, etc.
13. Added new global template tags text, which display the text enclosed in them if a title for the page being viewed was set in the "Headings, 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 was not set. Similar tags have also been added for the description: text , which display the text enclosed in them if a description was specified for the page being viewed in the "Headings, descriptions, meta tags" module, text that 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 viewed on the site, or the news, 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 (such as links) only for inactive categories from the menu.
15. Expanded options for displaying publications based on the values of additional fields in publications. When accessed at http://yoursite/xfsearch/fieldname/fieldvalue/, posts will be returned as before containing the specified value in that particular field if the field is set to "use as cross-references". When accessing http://yoursite/xfsearch/field value/, publications containing this value for all additional fields will be displayed. When accessing http://yoursite/xfsearch/field name/, all publications in which this specified field is filled will be displayed.
16. In the script settings, the ability to assign a separate page with the name 404.html in the root of your site has been added to display pages for which there is no content. If this setting is enabled, instead of the standard system message "Unfortunately, this page is not available to you, its address may have been changed or it has been deleted.", you can display a separate page specially prepared in advance, with a completely separate design. This innovation will be useful for webmasters who want to make a separate design of 404 pages of their site.
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, in the script settings in the admin panel, you can tell the script where to get the IP address of site visitors from.
18. When deleting a category in the script control panel, added the ability to choose what to do with publications that are in this category. You can: "Remove this category from publications", "Replace the category with another or other categories", as well as "Delete all publications in this category". In this case, if a category is deleted or replaced from a publication, then only the category being deleted will be removed or replaced. For example, your publication is in the categories "World", "News", "Popular", and you, for example, delete the category "World", then for publications in this category, only the category "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 writing pure javascript code in it. This field will be useful when you need to insert some code into the news that does not need to be checked for security, for example, any of your 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 it to be used by ordinary users whom you do not trust, otherwise it may pose a security risk to your site.
20. For additional fields of publications, which have the "Use as cross-references" option, the ability to specify the delimiter for these references has been added. You can specify both individual characters and HTML code as a separator. 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 in the template for each field.
21. Added support for "Yandex Turbo" technology for regular RSS feeds, without using the inclusion in the settings of the RSS feed type as "Yandex news", for this added support for displaying the full news tag (full-story) for any type of RSS feed. Also, the standard template /templates/rss.xml has been updated, which demonstrates how a template with full support for Yandex Turbo should look like. Similarly, the ability to customize the 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-like comments is enabled in the script settings. Thus, for example, you can quickly respond to incoming comments on the site without going into each news item, due to the fact that some of the heavy scripts have been switched to a delayed and independent of page rendering loading. These scripts are loaded into the browser in parallel with the rendering of the page and run only after the page is rendered in the browser. Which visually provides a faster page display.24. Added the ability for users who are not registered on the site, send complaints to the site administration about news and comments, just like this possibility existed previously only for registered users.
25. Added the use of schema org markup to display a rating with the "Rating" type. The use of this markup allows for full news, when displayed in Google search results, to also display the rating of the publication.
26. Added automatic detection of the orientation of photos when they are uploaded to the server, based on the meta-information contained in the 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 photographing.
27. Added the ability to automatically notify the site administration about new news from users, which is under moderation (if it is enabled in the script settings), if the news was added from the script control panel. Previously, a notification was only sent if a post was added directly from the site.28. If the user edits the publication in the control panel, which was previously published on the site, but according to the settings of his group, he is forbidden to publish 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 Breadcrumbs module on the site. 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, not a link. Only categories that are higher in the hierarchy will be displayed as a link, or a link to this category will be displayed if, for example, the user has gone further in navigating through pages in this category. Thus, this innovation avoids cyclic links of pages to themselves.
30. For the "Cross-references" module in the control panel, two new replacement regions for links have been added. You can optionally specify a replacement for static pages only, as well as select a replacement for static pages, news, and comments.
31. For the "Find and Replace" module in the control panel, added the ability to bulk replace text in polls for publications and in voting on the site.
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 display of the number of different counters (views, publications, comments) has been added to the admin panel of the script. The output of these counters is carried out in a formatted form as a space-separated hundreds, thousands, millions, etc. That 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 for new tags has been added 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. Thus, you can set a different design for displaying comments and adding comments for publications from different categories.
36. Added support for word declensions for the tag for displaying the number of votes, which were exposed for the rating of publications. For example, you can use (vote-num) feedback||a|s. Previously, this was not available for this tag. it contains HTML code, not just a number.
37. If the script settings enable the use of the site only via HTTPS protocol, then cookies by the browser will also be sent to the server 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 text of the publication of which is divided into several pages. If an incorrect page number is specified, an automatic 301 redirect will be made to the starting address of this page.
39. For RSS import of publications, support for importing images from the enclosure tag containing an image for publication has been added. If the short description in the RSS feed is just text, and the picture is given in it as a separate tag, then the picture for this publication will also be added to the short news when imported at the very beginning.
40. Added support for redirects to get 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, the DataLife Engine will automatically follow this redirect and take the content from the final source. Thus, receiving full news will be of better quality than before.
41. Changes have been made to the work of tags and. If the use and addition of comments is prohibited for a particular publication, then these tags will also hide the content in them.
42. In case 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 be displayed not at the end of all comments, but in the place where you define the output of the form for adding a comment with the tag (addcomments) in your template, thereby you can determine the location of this message on your site.
43. For authorization using the social network "Odnoklassniki", added the ability to automatically receive the user's E-mail, provided that the application itself has received the appropriate rights from Odnoklassniki. Attention, by default, Odnoklassniki does not give rights to receive E-mail, and in order to obtain the appropriate access, you must additionally contact the social. network to allow receiving e-mail. If permission is granted, DLE will automatically import the e-mail address as well.
44. Improved system for calculating image proportions when creating small copies. This creates a more correct and high-quality reduced copy.
45. Improved publication search system when enabled in the script settings, a simple search type. The new algorithm allows you to more accurately and correctly find publications.
46. Improved control system for the appearance of duplicate pages, when viewing all the latest comments on the site.
47. Optimized processing of additional fields of publications when displaying brief publications, as well as when the module for displaying popular publications is running.
48. Updated visual editors TinyMCE and Froala to current versions. Fixed a number of identified errors in these editors.
49. TinyMCE editor added support for inserting hidden text tags, using the corresponding button in the editor.
50. When using the Floara editor for comments, added the ability to quickly load and insert images into a comment. You can either click on the insert picture icon and select a file to upload, or simply drag and drop the picture file from your computer into the editor field, after which the picture will automatically be loaded and inserted into the cursor position in the editor.
51. Minor 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. Updated to the latest versions of the library for sending mail from the site, as well as a mobile device detection library.
53. An issue where the and tags were not processed in the post preview has been fixed.
54. Fixed a problem where meta tags for social networks were formed incorrectly. networks of video and audio, if the video was published in the add. fields and consisted of playlists and descriptions of video and audio files.
55. A problem has been fixed where, under certain situations and server settings, publication preview might not work when adding publications from the site.
56. Fixed an issue where dynamic loading of comments did not work, if it is enabled in the script settings, and the tag (jsfiles) is placed at the very bottom of the site.
57. Fixed a problem where the display of the latest comments did not work, in case the viewing of certain categories was prohibited for a certain group.
58. Minor bugs in the script that were discovered and announced earlier have been fixed.
This plugin system allows you to modify any functionality of the script at your discretion. Installing plugins on the site, updating plugins, is carried out in one click, directly in the DataLife Engine control panel. If the plugin is developed for a new system, then users no longer have to read installation instructions, edit something directly in the script files, etc. It will be enough for them to simply upload the plugin in the admin panel and that's it.
The plug-in system is built using the virtual file system technology. You describe in the plug-in which file and what actions need to be performed, based on this information, DataLife Engine will create virtual copies of these files, with all the necessary changes and modifications, and will work with the created virtual copies without affecting the original files. At the same time, you can describe changes in almost all files, with the exception of a number of basic ones, such as root files, but they do not carry any functionality, except for connecting other files. The functionality of the files responsible for AJAX functions can also be changed, for this they have been completely rewritten to work through the controller. What benefits does this provide? First, the original files always remain the same, so plugins can easily be changed, removed, updated, etc. Secondly, this system uses the minimum possible load on the sites as a whole, tk. virtual copies of files are created only once, at the time of installing or updating plug-ins, after which the DataLife Engine works with these modified files as with ordinary native files and there is no memory consumption for call points, storage and control of information about where and what functionality needs to be changed etc. The load on the server will increase only by the load that the plugin itself will bring with it, and the plugin management system will not cause any additional load. Thirdly, there are no problems directly with updating the script, the script can be updated to new versions, and your plugins will automatically be applied to new versions. At the same time, different plug-ins can modify the same file without causing conflicts, provided, of course, that different plug-ins do not perform directly opposite actions to each other.
So in the plugin management module itself, you can either create a plugin directly in the control panel, or upload a ready-made plugin. Consider adding a new plugin to the control panel directly:
On the first tab, you set general information about the plugin. Its name, its brief description. To make it easier to distinguish from other plugins, you can give it an icon that it will use in the list of plugins. You also specify the version of the plugin itself, and the version of the DataLife Engine with which it is compatible.
On the next tab, you directly specify the actions on the files that need to be performed. You can add one or more files on which you want to perform actions, as well as assign one or more actions to each file that you need to perform. In files, you can do the following:
1. Find and replace any code.
2. Find and add the desired code above.
3. Find and add any code below.
4. Completely replace the contents of the file with your own.
5. Create a new virtual file that does not exist in the original DLE.
You can also add or delete files, change or delete actions on files at any time. For ease of perception and editing, the entire code is highlighted, and the fields can be dynamically stretched.
Thus, the situation in which you previously manually corrected the script files, and stored the changes somewhere in your notepad, and each time you updated the script, re-entered them into the script files, with the new version completely becomes a thing of the past. You can create your own personal plugin directly in the admin panel, describing the changes you need in the script once, and when you update the script to a new version, you don't have to worry about it anymore, your changes will be automatically applied to new versions.
On the next tab, you can add the necessary actions in the MySQL database that the plugin should perform in certain situations. You can set a list of MySQL queries to be executed when installing the plugin, when updating it, when it is disabled, when it is enabled, when it is removed. At the same time, for each action, you can set either one or a list of several queries to the database.
For an existing plugin, you can do the following: You can disable it, but it remains on the site, but is completely ignored by the script, and all its actions on files are suspended. You can update it to a newer version if there is one. Download the plugin to your computer to install it on another site. In this case, the file itself is downloaded in XML format, and this XML contains a description of all actions. In fact, the plugin is an XML file that can be installed on the site in the admin panel.
Consider uploading a ready-made plugin to the site. You can download and install a ready-made plugin on your site. When you click the appropriate button, you can upload either an XML file with the plugin. Or a ZIP archive with a plugin. This allows you to create very complex plugins containing a large number of other additional files, both graphic and PHP files. For example, in order not to describe all the actions directly in the plugin itself, you can create additional files and pack them into an archive, decomposing them into new places. At the same time, it is important to know that the archive can contain only those PHP files that are not included in the distribution, but only your additional files, if there are files included in the distribution, such downloads will be blocked. Modification of standard files must be described already in the plugin itself. The XML plugin file itself must be located in the root of your archive.
If you are uploading an archive with a plugin, and the DataLife Engine does not have the rights to write the files in your archive. It will automatically request FTP access in order to download your archive. If access is not required, then everything will be copied automatically without them. At the same time, these accesses will not be stored anywhere, but will be automatically deleted after they are no longer needed.
The new plugin management system also has a built-in error logging system in the plugin. If any action on the files cannot be performed, or any errors occur, you can easily see and fix them. For example, this is extremely convenient if your plugin is not compatible with the next version of DLE, you will quickly see this, and you can easily adapt the plugin.
.sitemap_static_pages li - element - list of static pages
.sitemap_items li - element - list of articles
.sitemap_categories li - element