The following changes have been prepared and implemented:

1. Automatic engine update within the same major version of the engine is added in the admin panel for cases where update contain patches related to vulnerabilities or other bugfixes. If there is an update within the same major engine version, for example, when fixes related to vulnerabilities are released, or other problems with the script are detected and solved, it will be possible to perform this update in the admin panel of the engine.

2. Automatic plugins update is added. You need to specify URL to check updates from. Plugin developer’s resource specified in this URL should give the array in JSON format, which contains information about the current plugin version, and download link for the current plugin version. For example, this URL should return the value {"version":"2.0","url":"https://dle-news.ru/test/test.zip"}. After that, site administrator will be able check for updates and to get info about new plugin versions and update it in the admin panel in one click.

3. Now in the plugin management system you can specify the number of replacements to be performed for each search in the file. For example, if you need to find and replace some code that occurs in this file several times, you can specify how many times it is necessary to replace this code. To replace all occurrences of this code, you can leave this parameter blank, thus all the code occurrences will be replaced.

4. Now in the plugin management system there is the option that allows to automatically remove extra files loaded within the plugin archive when the plugin is removed from the site. This option is added in plugin parameters. It allows you decide whether you need to clean up extra files from the server when you delete a plugin from the site.

5. For the plugin management system, the option was added which allows to use the {THEME} tag in the names of folders in the ZIP archives. When downloading the archive through the plugin system, this tag will be replaced with the name of the template being used. For example, by placing the file /templates/{THEME}/test.tpl in the archive, your template file will be placed in the template used on the site. Thus, when using complex plugins that contain examples of template files, they can be immediately loaded into the desired folder containing the user's template.

6. In the plugin management system the ability to use the control characters of the preg_replace function, such as \\1, is used in the "Find and replace" action of the replacement line, which removes the restrictions on finding and replacing some code in the DLE.

7. Now for extra fields of "Image" and "Image Gallery" type you can individually assign description for each image, which will be converted to the HTML alt attribute.

8. Now for extra fields of "Image Gallery" type you can change the sorting order of the uploaded images simply by drag and drop. After uploading images you can swap images as you want. Also uploaded images can be moved to other extra fields.

9. For articles and comments a new type of rating is added - "Like and Dislike». This type of rating allows to keep count of likes and dislikes separately. New tags have been added for articles and comments templates: {likes} and {dislikes} to display number of likes and dislikes correspondingly, and [rating-type-4] text [/rating-type-4] tag to display the text inside of it if this rating type is enabled.

10. Now in user profile settings of Administration panel you can set a list of trusted categories where a corresponding user is allowed to publish. This will allow a user to manage specific categories where other users will not have the permission to publish. Or vice versa - you can exclude a user from a specific news category where you do not want him to publish.

11. In user profile settings of Administration panel you can set a list of trusted categories where a corresponding user is allowed to publish without moderation. Such settings will allow for more flexible rights distribution without creating a bunch of user groups, or even groups for each particular user.

12. Now in the articles edit section in advanced article search of Administration panel you can choose where to search. You can search in all content or only in title, short description, full description or extra fields. Algorithms of search has also been significantly improved.

13. Now for advanced article search in article edit section of Administration panel you can search in several categories.

14. Now you can use "&" and "#" characters in tag cloud, which allows to use names of various brands in the cloud, e.g. "H&M".

15. Now in Administration panel you can allow Administrators to authorize with social networks. When this option is enabled, users who are in the Administrators group can authorize with their social network accounts.

16. Now in comment edit section of Administration panel you can search for comments by string. In this section you can search for comments by any keywords. It makes comments editing more convenient.

17. Now in cross-reference control section of Administration panel you can replace using "In static pages only" and "In static pages, articles and comments" for mass actions on links.

18. Now you can use styles of your template from preview.css file to preview banners in the ad management section in the Administration panel. Thus, you can see a more accurate appearance of your ads if they use classes from your template.

19. Now you can use [not-news] tags [/not-news] in template of short articles description (shortstory.tpl). It allows to show the enclosed text if there are no articles by the given criteria. Thus, you can use your own message instead of the standard one if there are no articles in a given section of the site. You can make unique messages for every section. Also, these tags can be used in custom article display templates with {custom ...} tag.

20. Now you can use new tags for password recovery e-mail message: {%losturl%} which displays only the URL to reset a password, and {%ipurl%} which displays only password reset URL to reset the IP block. It allows you to make specific designs of these links in the letter, e.g. as buttons. And also you can hide the link to reset the IP block if you do not use it on your site.

21. The system for removing categories in Administration panel has been improved. If the category to be removed contains subcategories that are also subjected to deletion, then all actions for articles that are related to the category will automatically be distributed to articles that also related to subcategories of this deleted category. And the same actions will be applied to these articles in subcategories.

22. Now in "Filter by: IP, username or e-mail" module you can add blocked addresses, logins, or e-mails as lists rather than one by one. It significantly speeds up the process of adding if you already have a list of users to block.

23. In "Filter by: IP, Login or E-Mail" module you can edit existing rules. You can select and edit any rule, without having to delete it and re-add it again.

24. In "Filter by: IP, Login or E-Mail" module you can select several rules or all of them simultaneously, and unblock these rules in one click.

25. Now "Filter by: IP, Login or E-Mail" module supports IPv6 addresses that you can specify to block access to the site. You also can block IPv6 subnets.

26. Now you can specify IPv6 addresses in the user profile for those who are allowed to authorize. You also can specify not only a separate address, but IPv6 subnet.

27. Now for the custom sorting of articles displayed by {sort} tag you can set sorting for each specific category.

28. Now you can use "p", "div" and other tags in links in articles. Thus DataLife Engine supports more features of HTML5 standard.

29. Now you can add new users in the DataLife Engine control panel when working from a smartphone.

30. Changes have been made to nested comments. When the maximum nesting level for comments responses is reached, then in case of adding another replies they are displayed on the given maximum nested level in the discussion thread. Earlier, when the maximum nesting level was reached it was impossible to answer the comment. Now it is possible to post any number of replies.

31. Now in extra fields that have "Cross-Reference" type you can use double quotes and ampersand characters.

32. If the HTML message format is used for the e-mail recovery letter template, then the links that are generated by {%lostlink%} tag in this template will be generated as a ready HTML code, not just text links.

33. Now in the engine settings there is an option to set articles sorting by the number of comments by default. The same thing was added for sorting criteria when viewing the catalog.

34. Now in category settings there is an option for articles sorting publications to sort by the number of comments by default.

35. Changes have been made to extra fields, if the field is not allowed to be added by certain user groups. If the value of the extra field was added by the user with the corresponding rights, and subsequently the article is edited by a user who does not have the permission to edit this field, then the value of this field is no longer cleared - it comes back to its previous state.

36. The limit on the number of Description meta tag characters for categories is increased up to 300 characters. The maximum length now corresponds to the maximum length set by Google search engine to display this information in search results.

37. Similar articles search has been improved. Similar articles search results are sorted in a more relevant manner.

38. Visitors’ IPv6 addresses support has been improved. In some specific cases, the full address could not be placed in the database. Now the length of the fields is reserved according to RFC 4291 specification.

39. Formation of the og:description meta tag of the Open Graph protocol has been improved for full articles. Formation is more correct when it is used as the main content in extra fields of articles .

40. The work of the DataLife Engine security system has been improved to check the data on subdomains more correctly for some hostings which have subdomain structure of sub-folders of the main domain.

41. Now tel: protocol is supported for links published on the site using BB tags.

42. TinyMCE and Froala visual editors are updated. A number of detected errors is fixed in these editors.

43. An issue is fixed where fields of "List" type were used in extra fields of the user profile where values with the symbol "|" were used.

44. An issue is fixed where some symbols in the field values could incorrectly change in the plugin control section if the action on the file in the menu changed.

45. An issue is fixed where you could not use [lееch] tags for internal pages. It was only possible for external sites.

46. An issue is fixed where the site could not be upgraded if encoding other than UTF-8 was used on the site and Administrator's login or password contained Cyrillic symbols.

47. An issue is fixed where the pop-up block about new personal messages did not appear if the user logged out and then logged in after some time.

48. An issue is fixed where comments editing did not work in the engine control panel if TinyMCE editor was enabled in the engine settings.

49. An issue is fixed where the period in days within which it was allowed to send comments to the article did not show if this period was set in Administration panel.

50. An issue is fixed where an extra field of "Download file" type was not displayed as a file download link but as a usual tag.

51. Previously declared and found minor errors are fixed.

Link to the script downloading for customers:

If you are not a customer, you can purchase the engine on our website.