|
<< Click to Display Table of Contents >> Navigation: General Information > List of changes |
List of changes of 18.1 version:
❑Support for authorization in the social network VKontakte has been added using the new VK ID Oauth 2.1 protocol. This adds support for new applications being created on this network. Support for older applications will also continue to operate automatically, without any additional changes.
❑In the script settings of the admin panel, we have added the ability to specify user groups that are exempt from country-based blocking. If you have blocked access to the site for certain countries, you can now assign groups of users who are located in those countries and will still be able to access the site. The blocking will not apply to these users.
❑We have added the ability to use the max_completion_token parameter in the AI assistant settings in the script. This allows users to customize the maximum number of tokens generated by the assistant. Additionally, we have added the option to disable the max_tokens and temperature parameters if they are not needed. This makes it easier to integrate with new reasoning language models such as o1, o3-mini, etc.
❑We have added a completely new code editor with automatic highlighting when writing articles, instead of the previous CodeMirror. The main advantage of this new editor is that it renders highlights on large amounts of content much faster than CodeMirror. Whereas CodeMirror can take a long time to render highlights or even freeze, the new editor works instantly. This is especially important for working with long articles or articles that use a lot of HTML formatting. In addition to the faster rendering, the new editor also has more advanced search features and new autocomplete functions. These functions can automatically add tags and parameter values, as well as existing words in the article text. If there is an error in the HTML code, the line with the error is highlighted to indicate the problem.. It also adds automatic scrolling to the location of the cursor when moving between the source code editor and the visual editor, and vice versa.
❑The new source code editor also includes modules for editing templates, promotional materials, and plugins. Now, with a large amount of edited content, it is easier and faster to edit them. There are also additional features for automatic code completion, depending on the language used (HTML, CSS, jаvascript, PHP, SQL), as well as plain text.
❑When displaying user quotes in comments and personal messages, we have added a link to the author's profile in the quote. This allows users to quickly access the user's profile page, send them a personal message, or for administrators to perform actions related to the user's profile more easily.
❑To make it easier for users to access full context of a comment they've quoted, we've added a quick link for them to navigate directly to the original message. When they click on the link, visitors can easily find the page and location of the comment in question.
❑The keyword search algorithm has been completely rewritten in the "Cross-references" module. The replacement algorithms also work in real-time, with the ability to manage them on the fly. Regular expressions are no longer used for replacements, and content processing has been optimized, significantly accelerating the operation of this feature and reducing the load on the server for a large volume of keywords and links.
❑The module for processing the output of similar publications when viewing full news has been redesigned. Now, the search for similar news is performed directly when adding or editing publications, rather than when viewing a publication for the first time. Additional support for additional fields has been added when searching for similar publications, so the search will be more accurate if short and full description fields are used. The work with the cache of this block on the site has been improved, so the block will only be processed if the publication has similar news, reducing the load on the server in some cases. Additionally, the block will only be generated if there are appropriate tags for displaying similar news in the template. If similar news is displayed using other tags, such as {custom....}, no database queries will be executed, and there will be no additional load for generating the block.
❑We have added the ability to specify the number of posts and comments to process in one batch in the post sorting section. This allows users to increase or decrease the amount of data processed at once and adjust the processing speed accordingly. It also helps to avoid exceeding server limits when connections to external services take time, such as when processing media tags.
❑When editing publications, if user notifications are enabled, the publication is already being edited by another user, and notifications are added for editing publications on the site. Additionally, we have added control over editing publications directly on the site in the user interface. Therefore, regardless of whether editing starts on the website or the control panel, users will receive notifications everywhere on the website and the control panel. If users don't have access to the dashboard, they will still receive all necessary notifications about the publication being edited by another user.
❑For personal message templates (pm.tpl), support has been added for new tags: [pm-author] text [/pm-author], which display the text contained in them if the user viewing the correspondence is the author of this message, as well as the [not-pm-author] text [/not-pm-author] tags which outputs text if the user is not the author of this message. This allows you to allocate your own messages and those of your interlocutors to users.
❑Added the ability to delete publications on the site for users who are allowed to publish without moderation, edit their publications, but at the same time access to the DataLife Engine control panel is disabled. Thus, these users will be able to delete their publications directly on the site.
❑For short and full news output templates (shortstory.tpl and fullstory.tpl), support has been added for new [del] text [/del] tags that display a link to delete a publication from the site for users who are allowed to delete this publication. This allows you to add the option to delete a post for users, without providing the option to edit the post.
❑Added the ability to send a personal message to the user directly in the DataLife Engine control panel in the user management section, without having to go to the website to send a message. The message is sent in a pop-up window using AJAX technology without reloading the site page.
❑Support for HiDPI images has been added to the DataLife Engine download manager to preview uploaded images. If the uploaded image is a high-definition image, then a high-definition image will also be used in the preview.
❑In the user management section of the admin panel, the ability to quickly navigate to the list of users from any subsection of this section through the breadcrumbs menu has been added. And also, after editing the profile, you can choose either to continue editing or go to the list of users.
❑When reviewing all the latest comments on the site, we have removed the display of comments added to posts that are currently in moderation. As a result, users only see comments on recent and published news on the site.
❑The user management system in the control panel has been redesigned and improved. When you set any search parameters for users, after performing any actions in this section, if you click the "return" button, you will be returned to the exact page where you left off, with the same search parameters you specified previously. This makes it more convenient and quicker to work in the control panel in this area.
❑We have improved and redesigned the way blocks with information, warnings, or errors are inserted into the editor, as well as other formatting blocks. Now, you can delete blocks with one click after selecting them, and move them around the text by selecting the block.
❑For the editor, when adding and editing comments and personal messages, a button has been added to quickly delete a clickable link if links are allowed for them.
❑Added support and use of additional fields for the automatic generation of description and keyword meta tags. Thus, if the short and full description fields are not used on the site, then meta tags will be automatically generated only from additional fields.
❑Added support for nesting into each other for global template tags [country=X] Text [/country]. Thus, you can nest blocks into each other in the template, first defining a common block, and then dividing it by country. For example, you can use constructions like: [country=RU,BY,DE] Content for three countries [country=BY]Only for Belarus[/country][country=RU]Only for Russia[/country] continuation of the general block [/country]. This simplifies the layout of complex template designs. Similar nesting support has been added for reverse tags [not-country=X] ... [/not-country].
❑Added support for nesting into each other for global template tags [tags=X] Text [/tags]. Thus, you can nest blocks into each other in the template by first defining a common block and dividing it by tags inside. For example, you can use constructions like: [tags=test1,test2] The general header of the block [tags=test1] only the tag test1 [/tags][tags=test2]only the tag test2[/tags] the continuation of the general block [/tags]. This simplifies the layout of complex template designs. Similar nesting support has been added for reverse tags [not-tags=X] ... [/not-tags].
❑Added support for nesting into each other for global template tags [news=X] Text [/news]. Thus, you can nest blocks into each other in the template, first defining a common block, and then dividing it by news. For example, you can use constructions like: [news=1,2] Total block header [news=1] only news 1 [/news][news=2] news 2 only [/news] continuation of the general block [/news]. This simplifies the layout of complex template designs. Similar nesting support has been added for reverse tags [not-news=X] ... [/not-news].
❑For the general template (main.tpl), support has been added for new tags [changeskin] text [/changeskin], which display the text enclosed in them if users are allowed to change the site's themes. This allows you to automatically enable and disable individual blocks in the template, which are designed to display the design of changing templates on the site.
❑The template editor in the admin panel has been adapted to different text scaling set in the control panel design settings.
❑Due to the fact that Yandex stopped supporting the Yandex Turbo technology https://webmaster.yandex.ru/blog/yandex-stops-supporting-turbo-technology this technology has also been completely removed from the DataLife Engine.
❑Improved algorithms for copying and pasting content in the editor for publications.
❑Numerous additional optimizations have been performed in the processing of DLE templates, aimed at speeding up tag processing, as well as reducing memory consumption.
❑For additional fields with the type "Pure HTML or JS code", as well as for other fields, automatic height adjustment has been added when adding publications to the admin panels. Automatic height adjustment for text fields has also been added when adding publications on the site and when quickly editing publications on the site. This makes adding and editing posts even more convenient.
❑Added the ability to use apostrophes and quotation marks in place names and full names of users.
❑Added the ability to use the value "0" in additional fields of publications with the "List" type. Previously, when using such values, the field was considered empty and the value was not saved when re-editing the publication.
❑Formatted output of the number of downloads uploaded via DataLife Engine files has been added. Now the number of downloads will be displayed in the format for example: 23 532 234, instead of the combined number 23532234, which significantly improves the user's perception of the number of downloads.
❑Changes have been made to the display of the editor on the site when using a dark theme, and some errors related to its incorrect display in dark themes have been fixed.
❑The user's notifications about receiving new personal messages since they were not on the site have been switched to using more compact DLEPush notifications, which allows the user not to be distracted by them immediately after visiting the site, while having the necessary information about it. The consumption of server resources during user notifications is also reduced by reducing database accesses.
❑The dependence of downloading the necessary libraries for working with AI on external services has been removed. Now all the necessary libraries are located directly on your server.
❑For comments and personal messages, support has been added for additional field verification tags ([xfgiven_x] text [/xfgiven_x], [xfnotgiven_x] text [/xfnotgiven_x], separately and independently of the use of an additional field output tag in the template. In other words, these tags can be used in a template without using the [xfvalue_X] tag in this template.
❑Improved the system of copying and pasting content in the editor for publications. Added the preservation of CSS classes, which uses the DataLife Engine when forming its content. For example, if you copy quotes, thumbnail images, and other information from one field to another through the editor, their design will be preserved.
❑Queries to the MySQL database have been optimized for faster website operation and reduced server load.
❑Improved the system of inserting quotations based on selected text in the editor for publications and comments.
❑Added automatic deletion of outdated and unused DataLife Engine files when upgrading to new versions. Automatic deletion occurs if the DataLife Engine has access rights to delete these files.
❑Fixed an issue where when searching through settings, hidden fields were displayed that should not be displayed because they were disabled by other switches and settings.
❑Fixed an issue where keywords from the cross-reference module could be incorrectly replaced in structured data markup. schema.org in cases where these links are assigned a global replacement across the entire page.
❑Fixed an issue where invalid HTML layout occurred when displaying a survey on the site.
❑Fixed an issue where text insertion did not work when editing comments in the control panel.
❑Fixed an issue where category names were incorrectly displayed when adding or editing publications if they contained quotation marks or ampersands.
❑Fixed an issue when registering users using API functions.
❑Fixed an issue where the [xfnotgiven_x] text [/xfnotgiven_x] tags in the personal message output template did not work.
❑Fixed an issue where MySQL errors about searching for similar news could occur in some cases.
❑Fixed an issue where the template tags [add-favorites] ... [/add-favorites] and [del-favorites] ... [/del-favorite] did not take into account the template names that are assigned in the category settings, but used only standard template names.
❑Fixed an issue where the restriction on output in various categories for advertising materials, set in the banner settings in the control panel, did not work when viewing full publications.
List of changes of 18.0 version:
❑A completely new personal messaging system has been added to the site. The entire personal messaging system on the site has been completely rewritten. It is now not just about sending a single personal message and only being able to respond to a separate message with a full quote, but it is a full-fledged conversation where users see all messages in one combined thread, and the conversation takes place in a chat format. Upon receiving a message, users can repeatedly reply and send messages to each other within one topic. Users can leave the conversation at any time if they consider it finished or want to maintain order in their personal messages, but if another participant sends a new message in the same thread, the entire conversation will be automatically restored for the participant who left, and they can again see the entire conversation and understand its context. Additionally, users now have the ability to edit messages in the conversation if the other participant has not yet read it. Messages can also be deleted from the conversation if necessary. Messages can be quoted in full or partially, and much more.
❑Added support and use of artificial intelligence in creating and editing publications. Artificial intelligence will help you quickly create the necessary text or rewrite or change the writing style, or make translations and much more according to your wishes. The use of artificial intelligence based on the ChatGPT API is supported. In the settings, you can specify an entry point for communicating with ChatGPT, thereby allowing you to use not only OpenAI's direct ChatGPT but also any service that supports this API. In addition to this, you can flexibly configure in the settings how ChatGPT should be used, which language model to employ, which user groups are allowed to use artificial intelligence, the style of response, maximum limits, and restrictions on response length.
❑Added the ability to assign the same names to categories for URLs if they are in different parent categories. For example, you can create a category structure like "games/rpg/news/", "games/shooters/news/", and so on. Additionally, the algorithms for generating various links on the site involving categories have been optimized, significantly improving performance and reducing server resource consumption with a large number of categories.
❑In the DataLife Engine control panel, in the "Performance Analysis" section, the ability has been added to immediately disable a specific script feature to reduce load and increase performance. Now you don't need to go into the script settings and look for the relevant settings to disable a particular feature. You can disable it directly by clicking the corresponding button next to the desired setting. The disabling occurs instantly using AJAX technology.
❑For user output of publications using the tag {custom ….} support has been added for a new parameter unique="yes", which indicates that publications in this block should not be repeated if they have already been displayed on the site, i.e., unique publications should be displayed in this block. This will help avoid repetition of the same news in user output blocks if they fall under the same output criteria. For example, two tags {custom category="1" unique="yes" limit="1"} and {custom category="1" unique="yes" limit="1"} will display different publications, despite having the same parameters; the first tag will display the first news item from the category, and the second will display the second, skipping the first. Also, if a publication was displayed in the {content} block, it will not be displayed if this option is present in the tag {custom ….}.
❑More extensive support for various icons has been added for uploaded files in the download manager, making it easier to identify different documents, and file extension display has been added.
❑Added the ability to download files uploaded to publications directly in the download manager when adding and editing publications.
❑Support for OGG, FLAC, AAC formats has been added for uploading and playing music and music playlists using the DLE player.
❑For site access restrictions by country, support for IPv6 addresses has been added. Additionally, the database provider used to determine the visitor's country has been changed to use databases from IP2location, resulting in a much more accurate and extensive database.
❑A feature has been added to the script settings in the admin panel to enable the determination of a visitor's country based on data from the Cloudflare service, in case your site is connected and proxied through this service. In this instance, the server load is reduced, as DataLife Engine will not have to search for it in the local database on its own. If there is no data about the country, an automatic search will be carried out in the local database.
❑The script settings in the admin panel have been updated to allow or deny access to the site for bots if the site is restricted to certain countries, in case the bot is located in a restricted country. For example, if access to the site is restricted for certain countries, you can still allow search engines to index the site if they are located in the restricted country.
❑In the script settings in the admin panel, the ability to enable blocking circumvention using VPNs has been added for countries. If a user is located in a prohibited country and accesses the site, they will be blocked, and if they attempt to access the site again using a VPN from an allowed country, they will also be detected and blocked on the site.
❑For descriptions of settings allowing and denying access to the site by countries, the country in which the user is currently located has been added, as determined by DLE. This is so the site administrator can visually see that everything is working correctly, and their country is identified as needed, ensuring they do not accidentally block themselves.
❑When adding and editing publications in the control panel, the ability has been added in the "Access" tab to specify a list of countries where the display of this publication is allowed. Additionally, the ability to specify a list of prohibited countries for viewing the publication has been added. This way, you can easily configure in which countries the full news can be viewed, and in which it cannot.
❑For advertising materials added to the DataLife Engine control panel, a feature has been added to specify a list of countries where the display of these advertising banners and materials is allowed. Additionally, it is now possible to specify a list of countries where viewing is prohibited. This way, you can easily configure in which countries to display this code and in which not to. Thus, targeting the display by country.
❑Automatic saving of set parameters when uploading images and files to the server in the DataLife Engine download manager has been added. These parameters will be restored when the manager window is opened again. For example, if you chose not to apply watermarks, changed the size of the reduced copy, changed the storage, and for some reason left the page or navigated to another publication, all of this will be saved in the browser's local storage. When you reopen the download manager, all your set parameters will be restored, rather than set to default. This way, you don't need to set the parameters again each time.
❑The script settings in the control panel have been updated to allow specifying user groups, whose users will be displayed by default in the feedback form on the site if the email is not sent to a specific user. Previously, only users from the Administrators and Chief Editors groups were displayed there. Now you can assign your default user groups.
❑For RSS feed imports to the site, an option has been added to the stream settings to specify whether or not to include a link to the source from which the news was obtained. You can enable the addition of the source in the short or full description, or in both fields. Alternatively, you can disable the addition of the source when importing publications to the site.
❑The BBCODES and Floara editors were removed. These editors have become globally and morally obsolete, and their support was completely stopped a long time ago. No new features were added to them. Yes, we know that removing these editors is not the most popular measure, and users have asked us not to delete these editors. However, maintaining unsupported editors cannot continue indefinitely, as these editors significantly hindered the development of the script as a whole. The generation of different codes requires additional checks and text filtering, and the execution of a large amount of redundant code when processing publications. Therefore, a decision was made to completely abandon these editors, which significantly simplified the code and accelerated its processing when adding publications, as well as reduced the time spent on code testing. Additionally, it allowed us to focus efforts and resources on adding new features and capabilities. Now, a single TinyMCE editor is used for publications, and the processing of publications when they are added and edited has significantly accelerated, and server resource consumption has been reduced. For comments, there is also the option to completely disable the editor for sites that do not want any content formatting in comments and prefer only short, clean text.
❑When adding and editing publications in the admin panel and on the site, the visual editor was changed in such a way that by default it contains a single panel with the most frequently used buttons for content creation. If a full set of buttons is needed, the user can expand the panel while using the editor. Additionally, for each field, the selected collapsed or expanded state of the editor is automatically saved and will remain the same after reloading the page. This way, by default, the editor takes up less space, leaving more room for the editable content, and you can choose and save the editor's state for each field individually.
❑Changes have been made to the enabling and disabling mode of the adapted editor mode for mobile phones in comments on the site. It is no longer necessary to separately enable or disable it in the script settings in the control panel. Now it will automatically turn on when used by visitors on mobile devices.
❑For setting up the control panel design selection of DataLife Engine, the ability has been added to choose the editor's design. Each admin panel user can choose either the classic view of the editor or the lightweight version. The lightweight version offers a minimally cluttered editor interface, allowing the user to focus directly on the content they are writing. Moreover, the user can enable automatic editor height, which will automatically adjust to occupy as much screen space as the content within the field requires. Thus, small content will take up little space on the screen, while larger content allows for a larger editable area to be displayed.
❑Added support for a mobile-adapted editor when writing personal messages on the site.
❑Added support for dark themes for the editor when writing personal messages using AJAX on the site.
❑Improved text cleaning when inserting into the editor for removing "junk code" from the inserted text code.
❑In quick editing of publications, support has been added for pasting text from the browser's clipboard with HTML tags preserved.
❑When banning a user in the user management section in the admin panel, a log of the administrator's account who imposed the ban is added. This allows other administrators to immediately and easily see in the user management panel who exactly issued the block to the user. This speeds up the resolution of any contentious issues when there are a large number of moderators and administrators on the site.
❑For the template displaying information about an account or access being blocked (banned.tpl), support has been added for new tags: [banned-from] text [/banned-from] which display the text enclosed within them if the block was issued by a person, rather than automatically, for example, by country. Additionally, a new tag has been added: {banned-from} which displays the login of the administrator who issued the block to the user. This way, blocked users can immediately see who and why they were blocked on the site.
❑For the global template tag {catmenu …} designed for displaying a list of categories, support has been added for a new parameter idexclude="1,2,3-5" where you can specify the IDs of categories or a range of categories that should not be included in the category list, and all categories except the specified ones will be displayed.
❑Added the ability to restrict users in the user group settings regarding the number of negative ratings and dislikes they can give to news articles. You can specify the maximum number of negative ratings a user can give to news articles per day. For example, by setting it to two, a user will only be able to give two negative ratings within a day. The number of positive ratings is not limited. This way, you can protect the site from any negative visitor who massively gives negative ratings to everything.
❑Added the ability to restrict users in the user group settings regarding the number of negative ratings and dislikes they can give to comments. You can specify the maximum number of negative ratings a user can give to comments per day. For example, by setting it to two, a user will only be able to give two negative ratings to comments within a day. The number of positive ratings is not limited. This way, you can protect the site from any negative visitor who massively gives negative ratings to everything.
❑Added support for new tags [replycount] text [/replycount] in the comments template (commets.tpl) which display the enclosed text if the comment has replies from other users, and also added opposite tags [not-replycount] text [/not-replycount] which display the enclosed text if there are no replies to the comment. This way, you can create a more flexible design for information about comment replies.
❑Improved and optimized the display of the editor for publications on mobile devices in the DataLife Engine control panel.
❑Improved and optimized the display of the editor during quick editing of posts on the site. The editor now has a dynamic height depending on the amount of content in the fields. If there is only a little information written in the field, the editor will take up space proportional to the content. This facilitates editing information when there are many fields.
❑When displaying a user's group in comments on the site, if they have been banned, information is now shown indicating that the user is banned, similar to the display of their group in their profile.
❑When displaying information on the site about whether a user is online or not, a check is added to see if they have also been banned on the site previously. If they are banned, their status will always be offline, even if they attempt to log in successfully.
❑The preview of messages in bulk mailing in the control panel has been revised and improved. The design, fonts were improved, and full support for styling settings in the panel, which the user customizes personally, was added. Full support for the visual design of the control panel and for the message sending window was also added.
❑The ability to use double quotes for keywords that need to be found and replaced in the cross-link management section on the site has been added.
❑The ability to insert live broadcasts from the YouTube service on your site using [mediа=…..] tags has been added.
❑Comment flood protection has been moved from the script's general settings to user group settings. Thus, you can enable and disable this protection for each user group separately, as well as assign your own timeout for repeated comment addition to the site for each group.
❑The system for searching publications by search template during RSS import of publications in the DataLife Engine control panel has been significantly improved and optimized. Now you can specify any complex and multi-line code from the website page as the initial and final code, simply by copying it from the source site's code, without the need to use complex configurations with the {skip} tag.
❑Navigation output for publication and comment pages has been optimized and improved for mobile devices. When a visitor uses a smartphone to view the site, the number of page elements in the navigation is significantly reduced, allowing the navigation to easily fit within a single line without moving navigation links to other lines. This gives the page a more correct visual appearance, while maintaining full navigation convenience.
❑If access to the site has been denied, for example, if a user is banned, or restricted by country, the sending of correct HTTP 503 headers indicating that the page is temporarily unavailable has been added.
❑A check has been added for country-restricted access to the site for all AJAX actions performed on the site, not just for direct site views. This allows automatic bots from prohibited countries to be blocked if they have already been given the necessary parameters and tokens to perform some automatic actions.
❑A check for the plugin name being filled in when adding plugins in the admin panel has been added, before sending data to the server, to avoid errors about mandatory fields not being filled and to prevent data loss after submission.
❑Added correct support for embedding Twitter posts using [mediа=…] tags due to the service changing its domain to x.com
❑Added support for the new PHP 8.4.xx series
❑Improved and accelerated processing of large texts when adding and editing posts, as well as reduced memory usage in some cases.
❑Improved and optimized the algorithms for building category trees when adding posts in the control panel and on the website. This has allowed for a significant increase in page rendering speed in cases with a large number of categories.
❑Optimized and improved the processing of a number of template tags, which in some cases allows for faster rendering of templates and reduces memory usage.
❑Removed support for OpenSearch, due to the fact that the technology is outdated and no longer supported by current browsers.
❑Fixed an issue where it was possible to send an email message from the site through feedback to a user banned on the site.
❑Fixed an issue, where some AJAX functions on the site might not work if script settings disabled site authorization support, while the administrator remained logged into the DataLife Engine control panel.
❑Fixed an issue, where it was impossible to remove all categories from a publication when using mass actions in the control panel when selecting the action "Change categories" for selected publications.
❑Fixed an issue, where some template tags in comment output templates did not work correctly when AJAX navigation through comment pages was enabled.
List of changes of 17.3 version:
❑Added the ability to allow or restrict a user's access to the site based on their country of residence. To do so, we've added settings to the script settings in the control panel that allow you to specify a list of countries where site access is allowed. If the user is located in one of these countries, they be able to access the site, but if not, they will be automatically blocked. Additionally, instead of specifying allowed countries, you can also create a list of prohibited countries. If a user is from one of these prohibwillited countries, their access will be restricted, but if they are not from any of these countries, access will still be allowed.If a user is restricted from accessing the site based on country, you can provide a separate reason for their restriction. This reason can be specified in the settings.
❑We have added the ability to specify a list of countries in the script settings for which authorization is allowed on the DataLife Engine control panel. Additionally, for convenience, users can specify a list of prohibited countries instead of allowed countries. If a user is located in one of theprohibited countries, all attempts to log into the control panel will be automatically blocked, preventing them from even trying to log in.
❑Added the ability to display certain content in templates based on which country the site visitor is located in.To do this, a new global tag has been added to the templates: {country} which outputs the ISO code of the country in which the site visitor is located, for example, outputs RU if the visitor is in Russia, or US if the visitor is in the USA. This tag is useful when you need to add a country-based prefix to a link, for example, display a visitor's flagon the site. New tags added [country=X] text [/country] which will display the text specified in them if the visitor is in the specified X countries, where X is a list of ISO country codes. Countries can be separated by commas. For example, tags [country=RU, BY, KZ] text [/country] the text will be displayed if the visitor is from Russia, Belarus or Kazakhstan. Opposite tags have also been added. [not-country=X] text [/not-country] which will display the text specified in them if the visitor is not in the specified X countries, where X is a list of ISO country codes.
❑Added the ability to allow or prohibit search engine indexing for categories of publications. In the category settings of the control panel, users can choose to allow or disable indexing for a specific category. If indexing is disabled for a category, that category and its publications will be excluded from the sitemap when it is generated and updated.Additionally, a 'robots meta tag' with the content 'noindex, nofollow' will be added to category pages and any publications with in that category, preventing search engines from indexing those pages.
❑For additional fields with the "Uploaded image" and "Image Gallery" types, the ability has been added to specify which side to apply restrictions to the original image and the smaller copy, if restrictions are set in the field settings. You can choose between "By the largest side", "By width", or "By height". Previously, the default script settings for these parameters were used. Now, you can set your own custom values for each field.
❑We have added the ability to display advertising banners and other materials between comments. In the advertising materials management section of the control panel, users can now enable the display of a banner between comments and choose its position. Similar to the output of short news articles, users can choose to display the banner at the top, bottom ,or middle of the page, or combine these options.
❑Added support for the module of advertising materials and banner tags in comment templates when using AJAX navigation of comments and when dynamically automatically loading the comment feed using AJAX.
❑We have added automatic generation of the "keywords" meta tags when displaying short news, based on the content of each page.If a special value has not been set for a page in the control panel, the keywords will be generated automatically. If there are multiple pages for a specific section, the keywords set in the admin panel will only be used for the first page, while the meta tag for subsequent pages will be generated based on the content of that particular page. This ensuresthat the meta tag is not duplicated on different pages, improving the overall SEO of your website. The"description" meta tag will continue to be generated automatically as before.
❑The user search system in the user management section has been redesigned and improved. Instead of having multiple search fields, we now have a single search field that allows users to search by a variety of criteria. This includes the ability to search for users based on their login and email, as well as 5 additional fields that can be used for searching. These additional fields include full name, additional user information, place of residence, signature, and other relevant information about the user. This new system allows for more flexible searching, enabling users to find the exact users they are looking for based on various criteria.
❑The visual design of dialog boxes that prompt users to confirm irreversible actions on our site and in the control panel has been redesigned. The confirmation buttons now have a distinct and prominent color, which helps reduce the chance of users performing an automatic action and, as a result, reduces the likely hood of making an erroneous decision without the ability to cancel it.
❑We have added the ability to immediately close a survey when adding a new publication in the control panel. This means that you can create a publication with a closed survey without the need to edit it.
❑We have added the ability to set an expiration date for surveys in the control panel, so that they automatically close when they are published or edited. To do this, simply select the "Advanced" tab of a publication and choose"Closing the poll for voting" as the action when the specified date has arrived.This will automatically close the survey and only allow viewing of the results.
❑In the script settings of the control panel, we have added the ability to enable a redirect from a domain with a WWW prefix to a domain without the WWW prefix. When this setting is activated, if a user visits the websitewww.example.com,they will be automatically redirected to the domain example.com. Redirects will also occur for search engines, which will improve the indexing and ranking of the website.We recommend that you always have WWW support for your domain as an alias on your server, as users may accidentally enter the URL with the WWW prefix in their browser address bar.However, weal so recommend including a redirect to the non-WWW version of your website to improve indexing and provide a shorter and more familiar URL for users.
❑The script now allows users to customize the number of personal messages displayed on each page. Previously, the default value was 20,butnowusers can set their own preferred number in the settings.
❑For the user output tag of publications {custom …} added the ability to use the new parameter name="X", in which you can assign a name to a block, and later use this name to display or hide another design in the template if there is content in this block or it is missing. For example, writing {custom name="block1" category="6"} it will show publications from the category ID6, and the block itself will be named “block1”. New global tags have been added to operate with this name: [custom=X] Text [/custom] where X is the name of the block, which outputs the text enclosed in them if the block with the given name contains information. And also the opposite tags have been added [not-custom=X] Text [/not-custom] which display the text enclosed in them if the block with the given name does not contain any information and there are no publications.Thus, you can make additional external design of the blocks or, conversely, hide it, depending on whether there are publications in the block or not. For example, [custom=block1] Header {custom name="block1" category="6"} [/custom]. At the same time, the block may be placed anywhere on the page, not necessarily within these tags. Therefore, you can adjust and change other elements in the template based on these tags.
❑Added hiding of publications when viewing a short description, if the publication is in a category that is prohibited for viewing. For example, if a publication is in the categories "News", "Sports", and "Football", but the "Football" category is prohibited, then when viewing the "News" and "Sports" categories, that publication will be hidden.
❑We have added automatic filling of the "Name" and "Email" fields when responding to comments from unregistered users. This is only if they have already written a comment and provided their name and email address on the site beforehand.
❑We have added translation of system messages in case of errors when working with the mail server into different languages based on the installed language files. Now, if there are any errors when sending emails, users will receive messages in their preferred language according to their language package, and not just in English as previously. In total, we have added support for more than 40 different languages.
❑When you add a category to the control panel, additional protection is provided against accidental window closure when you click outside the window with the mouse or press the ESC key on the keyboard. This helps prevent unintentional window closure. You can still close the window by using the appropriate icons or buttons provided on the window for this purpose.
❑When adding categories, a list of categories automatically appears immediately after adding, eliminating the need for the administrator to press any unnecessary buttons in the control panel.This simplifies the process of adding large numbers of categories.
❑In the category management section, we have removed intermediate informational messages about successful category deletion and added an automatic transition to the category list page after deletion. This makes the category management process faster and eliminates the need for users to manually navigate through buttons.
❑When editing comments in the control panel, an additional identifier is added to indicate that the comment was submitted by an unregistered user. Additionally, their email address is displayed if they submitted the comment when publishing it. This allows users to easily identify who has written a particular comment.
❑Added automatic saving of information in the database when you press Enter when adding or editing a publication in the admin panel.If the cursor is in any field that contains a single line, the information will be saved. Previously, pressing Enter would either search for similar news or fill in a meta description, depending on the DLE version.
❑Added caching for custom output blocks of publications, even if they do not contain any publications for output. This helps save some server resources incase there is no content matching the specified parameters for some reason.
❑For user profile output templates (userinfo.tpl and profile_popup.tpl) added support a new tag {user-id} which outputs the user ID. This tag can be used in a number of cases when designing a template, as well as, for example, to form user links, such as links to the user's recent comments, etc.
❑When displaying category names in the RSS feed, they are separated by a comma character, which is the default setting. However, you can also use a different separator by specifying it in the script settings. This allows you to use more complex HTML code to display a list of categories on your site, with out affecting the RSS feed.
❑Changes have been made to how advertising materials are displayed in the admin panel in the advertising management section. When viewing short news, the "Category" setting for a banner takes into account the category of the article that the user is reading. When viewing full news, it considers the category to which the publication belongs. This allows you to set restrictions on displaying banners in full news based on publication categories. Additionally, if necessary, you can also set the rotation of banners with the same name.
❑When viewing full news articles and displaying banners, we have added verification of all categories that the publication belongs to, not just the main category.
❑The content downloaded using AJAX requests has been adapted to download data from the domain where the site is currently running, and not the one specified in the script settings. This innovation allows you to speed up the download if site mirrors are used.And the data remains available if the main domain is unavailable to the browser for some reason.
❑Added the use of HTTP header with code 301 for links that are published using secure link tags [leech=....] in publications and comments.
❑Support for new value comparison condition tags has been added for the user profile popup card output template (profile_popup.tpl). For example, the tag [if field="value"] text [/if] will output the text enclosed in them if the value of the field is equal to the specified value.
❑The animation system on the website has been redesigned and improved based on user feedback. The animations are now faster and more responsive, and the position of elements has been optimized to ensure a better user experience after performing certain actions.
❑We have added an automatic calculation of the size of dialog boxes displayed on the DataLife site, taking into account the base font size of the page. This means that if a user increases the font size in their browser, the window will also enlarge,making it easier for users with limited vision to navigate the site.
❑Added protection against accidental deletion of empty user groups. If a user group does not have any users, it will now require the administrator to confirm their intention before it can be deleted. This is to prevent accidental clicks on the delete button in the user group management section.
❑Added protection against accidental deletion of the RSS feed in the RSS news import section of the DataLife Engine control panel. The user will now need to confirm their intention to delete before proceeding, eliminating the risk of accidental clicks on the delete button in the menu.
❑The information that the publication has been updated using the [updated]....[/updated] tags during the time specified in the script settings is displayed only if the “Display information that the publication has been updated" checkbox has been selected. If it is not marked, then the update bar does not appear. Previously, it appeared during any editing of the publication. Thus, you can display this information not during any editing, but only when necessary.
❑Added control of banned IPs and users for all AJAX actions on the site. If the IP address is blacklisted in the "Filter by IP, Login, or E-mail"section of the control panel, it will be blocked not only from viewing the site but also from performing AJAX actions. This includes blocking IP bots and their subnets that attempt to manipulate ratings, views, and other metrics.
❑When updating the script to newer versions, automatic inclusion of error output from PHP has been added in case of errors occurring, regardless of whether they are enabled or disabled in the script settings in the administration panel. This allows site administrators to see what errors occurred during the update while performing the update. This is useful, for example, if the server software does not meet minimum requirements or if necessary PHP interpreter libraries are missing. Error output is only enabled for the update process; for everything else, settings set in script settings apply.
❑The system for identifying the devices used by users to access the site has been upgraded and improved. We have expanded the database of devices to include smartphones and tablets, and we have also optimized the overall performance of the system.
❑The load on the server is reduced when viewing pop-up user cards in some cases.
❑The formation of meta tags of site pages has been optimized, and possible duplication of content has been removed in some cases.
❑There have been several optimizations and improvements to the user interface in the DataLife Engine control panel. Outdated notifications in the DLEAlert pop-up window have been replaced with notifications using the DLEPush push notification format.These notifications are now closed automatically.
❑The control of the server's software compliance with the minimum required specifications has been improved. If the PHP version installed on the server is below the minimum requirement, DLE will no longer display "unintelligible" PHP errors and crashes. Functions that are not compatible with the current PHP version will be automatically disabled, and an informative message will be displayed to the administrator regarding the need to upgrade the PHP version.
❑All HTML elements with the 'checkbox' and 'radio' types for various forms that the DataLife Engine generates to output on the site have been brought into a single, common output standard. This has made it possible to easily customize them using a CSS template of your choice.
❑For template tags {image-X} intended for displaying image URLs, as well as for meta tags meta property "og:image”, support for svg extensions for images inserted into the publication has been added.
❑Added forced clearing and zeroing of fields containing only the value'<p><br></p>'to an empty value. This innovation is useful if you use the Flora visual editor on the website and in the control panel, in which all empty fields contain this default value, even if you do not write anything in the editor.Thus, there will be no unnecessary code in the fields if nothing was written in them in this editor.
❑Added support for the Rutube service for inserting videos using the [media=...] tag in connection with the addition of support for the oEmbed data exchange protocol by the service.
❑The TinyMCE visual editor has been updated to the current version.
❑The entire DataLife Engine code has been rewritten to remove the $config['charset'] setting. For a long time, DLE only supported the UTF-8 encoding, so this setting had no meaning and could not be changed through the DLE control panel.All DLE code previously used this setting, but in the new version it is no longer used. It is still used in some places to update from older versions of DLE, but this will no longer be necessary. The DLE functions that used this parameter have also retained it for compatibility with older third-party modules. However, it is recommended to update these modules if they use DLE functions with this parameter, as it will no longer make sense to transfer these parameters.
❑Fixed an issue where the tags [image-x] text [/image-x] tags did not work if the {image-x} tag was not used in the template together with them when viewing full news and when displaying news using custom output {custom....}
❑Fixed an issue where an empty sitemap could be created for static pages if there are static pages, but there are no pages that need to be placed in the map. For example, publishing to the map is prohibited for all pages, or indexing is prohibited, or they are password-protected.
❑Fixed an issue where a disabled site broadcast an RSS feed for turbo pages with an error.
❑Fixed an issue where the plugin name was displayed incorrectly if errors occurred in it, in the error display section if the plugin name contained tags[lang=x]...[/lang]
❑Fixed an issue where {custom...} tags could not be used in the attachment.tpl template
❑Fixed an issue where, in some cases, in correct processing of inserting code examples in publications could occur.
❑Fixed an issue where in some cases the extension of files uploaded to the server could not be saved when using very long filenames.
❑Fixed an issue where the function to disable video preloading did not workin the media player settings.
❑Fixed an issue where the option to commit a publication did not work when adding a publication from the site.
List of changes of 17.2 version:
❑A new push notification system has been implemented for site visitors who are automatically transferred between groups. For example, whentheir period of membership in a group expires, or when they reach a certain ranking, etc. In case of an automatic transfer of a user to another group, they will receive a push notification on their site informing them that they have been moved to a new group, along with the reason for thetransfer. This ensures that site visitors are always aware of any changesto their membership status.
❑Added the ability to mark newly published content. To do so, we haveadded an option to the script settings in the administrator panel to specify the duration for which a newly published piece of content shouldbe considered as new. After that, in the output templates for short and long news stories (shortstory.tpl and fullstory.tpl), we can use the [new] text [/new] tags to display the text enclosed within them if the content is considered new. We can also use the [not-new] text [/not-new] tags to show the text enclosed within them after more than the specified timeperiod has elapsed since publication, which is set in hours in the settings. Thus, we can mark publications in the templates using any of these tags to indicate whether a piece of content is new or not.
❑Added the ability to mark published articles as updated. To do so, we have added the ability to specify the amount of time that should be counted as an update in the script settings of the admin panel. After that, in the output templates for short and full articles (shortstory.tpl and fullstory.tpl), we can use the [updated] text [/updated] text tags to indicate whether an article has been updated or not. These tags willdisplay the enclosed text if the article has been marked as updated, orthe text enclosed in the [not-updated] text [/not-updated] tag if more than the specified timehas passed since its last edit. The time is specified in hours in the settings,so you can mark articles in the templates with a clear indication ofwhether they are updated or not.
❑The ability to set the maximum number of complaints that a user can submit from the site has been added to the settings in the DataLife Engine administrator panel. Previously, the number was limited to three for spelling errors. Now, you can set this number and it will apply to all types of complaints, including publications, comments, and spelling mistakes.
❑The ability to allow or restrict this group from submitting complaints about posts from the site has been added to the user group settings. This means that you can prevent certain groups from submitting complaints about posts in order to prevent abuse.
❑The ability to allow or deny this group from submitting complaints about comments on the website has been added to the user settings. Therefore, you can prevent certain groups from submitting complaints in order to prevent abuse.
❑The ability to allow or disallow this group from submitting complaints about spelling errors on the website has been added to the user groupsettings. Therefore, you can choose to block certain groups from submitting these complaints in order to prevent abuse.
❑Added the ability to close polls that are used in news articles. This means that you can close a survey for publication, keeping it on the website. Closed polls will still be displayed on the page, but users will not be able to take part in them anymore, only seeing the results. This feature is useful if a survey has become irrelevant over time, but you don't want to delete it and want to keep the results available on the site. You can alwaysreopen a closed poll if needed.
❑For poll output templates in publications (poll.tpl), support has been added for new tags [closed] text [/closed] that output the text enclosed in them if the poll was closed for voting, as well as reverse tags [not-closed] text [/not-closed] that output the text enclosed in them if the survey is open for voting by site visitors.
❑For poll output templates in publications, support has been added for a new {close-date} tag that outputs the closing date of a poll, if it has been closed.
❑For additional fields of the "One line" and "Several lines" types, the ability has been added to set the minimum number of characters required if the field is filled. This can also be set to have no restrictions.
❑For additional fields with the "One line" and "Several lines" types, the ability has been added to specify, in the field settings, the maximum number of characters that must be entered if this field is completed. This option can also be left unrestricted.
❑We have added support for downloading files from the server or external storage through DLE in multiple streams and added support for resuming downloads in case of network interruptions or other download failures. This new feature will be particularly useful when downloading large files over a slow internet connection.
❑To facilitate quick editing of content on the site, we have added the ability to change a publication's category when editing it.
❑For the plugin management system, we have added the ability to insert action blocks between existing actions in the control panel. To do so, each block now has a button to add a new action that will be insertedimmediately after the selected block. This allows you to edit an existing plugin and add additional blocks directly to the desired location.
❑For the plugin system, the ability to use the tags [lang=X] Text [/lang] in the plugin name, description of the plugin, and notes for the plugin has been added. Which output text depending on the language that the user uses in the admin panel. Where X is the ISO language code from the language pack. This way you can display the title and notes in different languages. For example, the tag [lang=ru]Russian Russian text[/lang] will display this text if the user uses Russian, and the tag [lang=en] English Text [/lang] if the user uses English.
❑Added support for a new global template tag: [active-plugins=X] Text [/active-plugins] which outputs the text enclosed in it if the specified plugin is enabled and used on the site. Where X is the plugin ID or its name. For example, you can specify [active-plugins=1] Text [/activrameters in the tag separated by commas, for example, [active-plugins=1,2,5] Text [/active-plugins].
❑Added support for a new global template tag: [not-active-plugins=X] Text [/not-active-plugins] which outputs the text enclosed in it if the specified plugin is disabled and not used on the site. Where X is the plugin ID or its name. For example, you can specify [not-active-plugins=1] Text [/not-active-plugins] or [not-active-plugins=My plugin] Text [/not-active-plugins], and if the plugin with ID 1 or with the name “My plugin” is disabled in the system and is not used, then the text specified in the tag will be output. You can also list several parameters in the tag separated by commas, for example, [not-active-plugins=1,2,5] Text [/not-active-plugins].
❑For custom output of publications using the {custom ....} tag, the ability to use the new favorites="yes" parameter has been added, which will display publications that are in the visitor's bookmarks. For example, the {custom favorites="yes" order="id_as_list”} tag will display publications from the user's bookmarks in the sort order in which they were bookmarked.
❑The system for setting permissions or prohibitions on comments in category settings for specific categories of the website has been completely redesigned. Previously, when you banned comments in the category settings, this ban only applied to newly added posts in thatcategory, and the ban was specified directly in the post itself. In order for the changes to take effect on older posts, it was necessary to save the post again. Now, the permission or ban for comments in the category applies immediately to all posts in the category, and the ban is not written directly into the post itself. Therefore, you can enable or disable the permission for comments in a category, and this action takes effect immediately on posts in that category.
❑We have added a system of automatic prompts for filling in the author field when adding or editing publications in the DataLife Control Panel. Now, if the author needs to be changed, a list of existing users in the database will be displayed when typing in the field. This will speed up the editing process and minimize possible errors when entering a user's name.
❑A new setting has been added to the script settings in the control panel that allows you to specify how many comments should be displayed on the recent comments page. This means that you can now independently control the number of comments displayed when viewing comments ona specific publication and when viewing all latest comments on the website.
❑When a user clicks on the link in an email notification about a new comment on a publication, they are automatically taken to the relevantcomment on the page, without having to search for it. This ensures thatthe user sees the added comment immediately.
❑For additional fields with the "List" type, the ability to use commas in the list values has been added. Previously, this symbol was used for system purposes in this type of field.
❑For short and full news output templates, support has been added for new tags: [ifxfset fields="X"] text [/ifxfset] that output the text enclosed in them if a field named X has been specified and filled in for the news. At the same time, you can list several field names separated by commas. For example [ifxfset fields="test1,test2"]both fields named test1 and test2 are filled [/ifxfset] will output text if both fields were filled in the news. And also added tags [ifxfnotset fields="X"] text [/ifxfnotset] that output the text enclosed in them if the field named X was not specified and filled in for the news. However, you can also list several field names separated by commas. For example [ifxfnotset fields="test1,test2"] both fields named test1 and test2 were not filled [/ifxfnotset] will output text if both fields were not filled in the news. The main difference from the existing tags [xfgiven_x] and [xfnotgiven_x] is that you can list several fields at the same time and the fullness of all listed fields is checked at the same time, as well as the fullness of fields without values is checked, for example, if the field is set to “0” or the value “no”, this is also a filled field in publications. If you need to check the value yourself, then use the tags [if field = "value"] text [/if] as before.
❑Support for new tags has been added for user profile output templates (userinfo.tpl and profile_popup.tpl): [own-profile] Text [/own-profile] that display the text enclosed in them, if the user is viewing his own profile on the site, as well as tags [not-own-profile] text [/not-own-profile] that display the text enclosed in them, if the user is viewing someone else's profile on the website.
❑For the category menu output template (categorymenu.tpl), the template tags [category-icon] text [/category-icon] and [not-category-icon] text [/not-category-icon] were replaced with the tags [cat-icon] text [/cat-icon] and [not-cat-icon] text [/not-cat-icon] respectively. This is due to the fact that these tags had the same name as the global tags for all templates linked to publications, which led to their incorrect operation when viewing sections and publications.
❑Added support for the "Automatic conversion of links to clickable" setting for all editors, including visual editors. This setting is now applied regardless of the editor used, as well as for additional fields with the "Multiple lines" type, regardless of the editor. Additionally, the setting is also applied to comments. If the user is allowed to publish links and publishes a link in text in a non-clickable form, it will be automatically converted to a clickable link.
❑Added gallery mode to the enlarged image view in the DataLife Engine'scontrol panel, in the section for managing uploaded images.
❑Added the ability to save and display the user's username in the comment template, in case an unregistered user leaves a comment. To do this, the addcomments.tpl template adds support for a new {guest-name} tag, which outputs the login of an unregistered user that he entered during the previous comment addition. Thus, an unregistered user will not need to enter his username every time he adds a comment on the site.
❑Added the ability to save and display the user's E-Mail address in the comment template, in case an unregistered user leaves a comment. To do this, the addcomments.tpl template adds support for a new {guest-mail} tag, which outputs the E-Mail of an unregistered user that he entered during the previous comment addition. Thus, an unregistered user will not need to enter his email address every time he adds a comment on the site.
❑Added the ability to use different editors simultaneously within the same page. For example, you can use the Floara editor for quick editing of publications, and use the adapted editor for mobile TinyMCE for comments.
❑We have added a check for the required additional fields when editing publications on the website.
❑When adding comments on the site, we have made changes to notifications in case a comment needs to be reviewed. Previously, the notification message had an "Error" visual type, which could mislead users and cause them to send comments repeatedly. Now, the notification occurs as a mild warning that the comment has been submitted, but is awaiting review.
❑The system for deleting user comments from the site has been updated. Previously, there were cases where comments that were replies to a deleted comment would remain in the database, leading to unnecessary and unused data in the system.
❑The TinyMCE visual editor has been switched to using the latest 7.xx
❑In case of a site shutdown, as specified in the script settings, it is recommended to send correct HTTP headers, such as 503, to indicate that the page is temporarily unavailable. This will prevent pages with information about the site being disabled from being indexed by search engines if they visit the site during the time of the shutdown.
❑In the event of a MySQL server outage, we have added additional HTTP headers to the response, including a 503 status code, to indicate that the page is temporarily unavailable. This helps prevent pages with site errorsfrom being indexed by search engines if they are visited during the outage.
❑Changes have been made to notify visitors if they are not allowed to leave comments on the website. If commenting is prohibited for theirspecific group, but other groups can leave comments, a message will bedisplayed indicating that commenting is not available for their group. If commenting is disabled for all users, regardless of their group, the message will not be displayed specifically for that group. This way, userswill not be misled into believing that commenting is only disabled forthem and not for others.
❑We have fixed an issue where backup files were not being deleted when automatically creating backups using Crown, if the limit on the number of stored backup files was exceeded.
❑Security fixes when working with the database management section of the DataLife Engine Control Panel.
❑We have fixed an issue where the transition to comments would not work when viewing the latest news if User Friendly URL support was disabled in the script settings.
❑We have fixed an issue where, in some cases, the intended page with a comment may be incorrectly selected when clicking on a link to view recent comments if pre-moderation is enabled for comments before they are published.
❑We have fixed an issue where if a user was assigned to a group that was deleted, they would be transferred to a non-existing group if the group promotion was set in the group settings. Now, if there is no such group, the user will remain in their current group and won't be moved anywhere else.
❑We have fixed an issue that could cause an error when adding or editing RSS feed sources in the DataLife Engine's control panel.
❑We have fixed an issue that could cause an error in the category management section of the control panel in certain cases.
❑We have fixed an issue where the "Hide only the full news from inaccessible sections" setting for user groups did not work correctlywhen using the {custom ...} user output tag.
❑We have fixed an issue where the {news-id} global tag was incorrectly processed when viewing a non-existing publication.
❑We have fixed an issue with the title of a publication being incorrectly displayed when a user adds a comment using the {news-title} tag. This issue was caused by a problem with the custom comments feature.
❑We have fixed an issue with the incorrect definition of the publication date in some cases, where it was being displayed as "yesterday and today".
❑We have fixed an issue that could cause incorrect file counting whensending feedback in some cases.
List of changes of 17.1
❑For additional fields with a list type, we have added the ability to select multiple values from the list. You can configure in the settings for this additional field whether it is possible to select more than one value at a time, or only one value from the list can be selected. You can also specify how to display the values of this field on your site, for example,by using a specific separator. Additionally, you can determine whetherthis field is required or can be left blank.
❑We have added the ability to include links to images uploaded to our publications in the sitemap. This option can be enabled or disabled directly when creating a map in the admin panel. When this option is enabled, all images that have been uploaded for publication will also be included in the map, according to the guidelines of the Google search engine https://developers.google.com/search/docs/crawling-indexing/sitemaps/image-sitemaps?hl=ru. If this option is disabled, the map will be created without any links to images. However, including images in a map can increase the time it takes to create the map and require additional database queries.Therefore, it is up to you to decide whether or not to enable this feature. At the same time, including images on a map can significantly improve the indexing of your images on your website.
❑A new system has been implemented to notify users about successful completion or errors on the site. Previously, users had to manually close a pop-up window with information about the site's actions. The new system sends push notifications in the corner of a user's browser,automatically closing after a certain period of time, without any further action from the user. Developers of templates, modules, and plugins can now also use the built-in functionality to trigger these notifications. The success notification is triggered by the function DLEPush.info (message, title), The push notification is triggered by a function DLEPush.warning (message, title), the notification of an error is sent by the function DLEPush.error (message, title). Different types of notifications have unique designs.
❑In the DataLife Engine's control panel, there is now an option to forcethe addition of a unique prefix to all uploaded images, in the image management section. When this feature is enabled, the prefix will be automatically added to the image's name. This will help users who often change their image upload to avoid browser cache and ensurethat they see the latest version of the image on their site. If this optionis disabled, then the original image name is saved, and only if a file with that name already exists on the server will a unique prefix be applied. The prefix is no longer directly linked to the time of download, as it wasin previous versions, and is now unique and randomly generated.
❑Added the ability to sort external storages according to the specifiedorder. To do so, simply move the desired store to the desired positionand set the sorting order in the control panel under the Storage Management section. This way, you can ensure that the most frequently-used stores are displayed first, if necessary.
❑Added the ability to customize the settings for quick edit mode inpublications on the website. Now, you can choose whether you want to edit only fields that were previously filled out, or display all the fields for editing, including those that weren't filled in earlier. When you select the "edit only filled fields" mode, quick editing will still display only the previously-filled fields when adding new fields. However, if you choose the "all fields" mode, then you can edit not only a short description butalso a full description and any additional fields for your publications,regardless of whether they're empty or not and whether they were previously filled in.
❑Added full saving of the file name uploaded to the server using the DataLife Engine and intended for download. When uploading a file to the server, its name will be saved as it was originally, and accordingly, when downloading it, it will be saved to a computer with the same name. For example, if Cyrillic characters were used in the name (my файл.txt ), then they will also remain when downloading without transliteration: my файл.txt The same applies to other languages.
❑For the plugin system, the DataLife Engine control panel has added the ability to perform all necessary actions with a plugin directly when editing it. For example, on the plugin editing page, users can check for updates, update, download, or delete a plugin without leaving the page.Previously, users could only edit a plugin on the dedicated edit pages. As a result, a total of five new options have been added to the plugin management interface.
❑For the plugin system in the DataLife Engine control panel, we have added a link to edit a plugin to the plugin options menu. This allows you to open the editing window for a plugin in a new browser tab, which is helpful when editing multiple plugins at the same time in the control panel.
❑Added the ability to change the name of the comment author, when editing comments on the website and in the administration panel, if the comment was left by a non-registered user. Now, if a user has written invalid text in the "name" field, an administrator can edit it without having to delete the comment on the website itself.
❑Added automatic dynamic modification of tag content [add-favorites] text [/add-favorites] и [del-favorites] text [/del-favorites] when adding or deleting a publication from bookmarks on the website,it doesn't matter where these tags are located in the template or what their content is. The content will automatically be updated when an AJAX action is performed, without having to reload the page. The user will also automatically see that the publication has been added to or removed from the bookmarks.
❑When displaying the "Complain" button in the comments section of the site, we have added a check to ensure that the user is the author of the comment and, if they are, then the "Complain" button for that comment is not shown, as users cannot complain about their own comments.
❑Added support for a new global tag {lang text="LANG_PARAMETER"}, which is designed to output information from the website.tpl language file, which is currently in use, where LANG_PARAMETER is the value of the parameter to be output. For example, the tag {lang text="attach_images"} will display the inscription “Attach images” from the language pack. This tag will be useful when developing additional modules and plugins, when you can place additional language data directly into the language pack and automatically output the phrases you need when the user changes the language on the site, displaying the values in the template as a tag, rather than directly writing the phrase.
❑For short and full news output templates (shortstory.tpl and fullstory.tpl) added support for a new tag {edit-date=формат даты} which displays the date when the publication was edited in the format specified in the tag. Thus, you can set your own format for the editing date, or output not only the entire date, but also its individual parts. The date format is set according to the format used in PHP. For example, the tag {edit-date=d} displays the day of the month, and the tag {edit-date=F} displays the name of the month, and the tag {edit-date=d-m-Y H:i} displays the full date and time.
❑For the user's pop-up card output template (profile_popup.tpl) added support for a new tag {usertitle}. This feature allows you to display the user's name and username in a specific location within your website's template. Previously, their login information was only displayed in the header of a card, but now it can be displayed in any other location you choose.
❑For additional fields with the “Date and Time” type, support for a new tag has been added [xfvalue_X format="Format"], where X is the name of the additional field, and “Format” this is the output format of the date and time specified in the field. Thus, in different places of the template, you can output this additional field in different date and time formats, and not only in the format specified for the default field in the field settings. For example, the tag [xfvalue_test format="j F Y H:i"] displays the date and time specified in the field in time format j F Y H:i.
❑For user profile output templates (userinfo.tpl and profile_popup.tpl) added support for new template tags: [banned] text [/banned] they display the text enclosed in them if the user is currently banned from the site, [not-banned] text [not-banned] they display the text enclosed in them if the user is not banned from the site, {ban-description} displays the reason why the user is banned, {ban-date} displays the date before which the user was banned from the site. Thus, with the help of new tags, users can display information to other site visitors when they visit a user's profile. This information will include details about why the user was banned, and what the reason for theban was.
❑We've added the ability to specify which provider will be used for search engine notifications in the script settings of the admin panel using the IndexNow protocol. The choice of provider doesn't affect which search engines will be notified. They automatically synchronize the data. However, the choice does affect which provider responds faster and is closest to your site based on location. Therefore, everyone can select the optimal provider for their website.
❑The script settings have added the ability to use a specially adapted mobile device editor when writing comments on the website. When this option is selected, a lightweight editor with a minimum number of buttons will be displayed. This editor doesn't overload the mobile screen with information and also simplifies the process of uploading and managing images.
❑Added automatic support for all time zones supported by the server.You can set the default time zone for the site or the user can choose it in their profile. If time zones are updated on the server, the DataLife Engine will automatically use the latest versions. Therefore, more than 300 new time zones have been added for users to choose from, and they will automatically update if new ones are added. For the ease of selecting a time zone, we have added a time zone search when selecting.
❑We have added a search system for script settings in the admin panel. This will allow you to find the desired setting much more quickly by simply starting to type its name. Additionally, for your convenience, the text of the relevant setting will be highlighted for visual display.
❑An editor with source code highlighting has been added to the Email message template management section. The visual component of thesection has also been improved, making it easier to edit templates for emails.
❑Added automatic rebuilding of the tag cloud when rebuilding publications in the admin panel. This feature will be useful in cases where, during manual independent work with the database, relationships between tables are incorrectly updated. For example, if publications are added bypassing the DLE
❑We have added an automatic redirection feature that redirects users to the home page immediately after they register on the site. This helps reduce the number of clicks that users need to make on the site during registration and reduces the number of steps they need to take to navigate around the site.
❑Added support for IPv6 addresses in the "List of IP addresses for which authorization is allowed in the script administration panel" section ofthe administration panel. Therefore, if the website administrator has an IPv6 address, instead of a non-IPv4 address, they can restrict access to only the IPv6 addresses they need in order to gain access to the website.
❑Improved the visual appearance of selected categories when adding and editing publications in the control panel.
❑For the TinyMCE editor, we have added the ability to specify image sizes directly while editing the properties of an image.
❑Changes have been made to how the user tagging button is operated by a spammer. As a result, this button no longer appears in the comments of users who belong to a protected user group.
❑When selecting external storage during file upload and if allowed, it is shown in a similar manner to the external storage management section.
❑The system for determining the color of the watermark on images has been improved. The DataLife Engine now determines the color areas better and better on which the watermark should be applied, which allows for a more accurate determination of which watermark (light or dark) needs to be used in a particular case.
❑We have improved the system to pre-check the email address when a user registers on our site or changes their address in their profile.
❑When editing the values of additional user fields in the control panel, the rights of the user being edited are added, and not the ones of the editor. For example, if a user is forbidden from adding links in additional fields, then this prohibition will be applied and saved when the user is edited by an administrator.
❑Added the ability to use HTML code in additional fields of user profiles, even if safe mode is disabled for these fields. Previously, BB tags were the only option available.
❑Added the ability to use additional fields of the "Date and Time" type in the full publication view. Previously, these fields were not available inthe full output, as per the field settings.
❑Added automatic cache reset for the admin panel's custom styles file,located in the templates folder, when clearing the cache from the admin panel.
❑For tags [ifxfvalue ….] … [/ifxfvalue], to check the values of additional fields, we have added a check on the list of values if the "Use as cross-reference" option is enabled for the additional field. For example, if a field contains several values, the check will be performed for each value separately, not for the entire field. A similar validation mechanism has been added for tags [if ….] … [/if] дfor these types of additional fields.
❑Added support for PHP version 8.3.x
❑The TinyMCE visual editor has been updated to the latest version. Its rendering speed has been significantly improved.
❑When using the TinyMCE editor, if an image is uploaded not through the file manager but through the "Insert Image" window in the editor, then saving the written description for the image will also save any reduced copies that were created at the same time.
❑Due to the fact that search engines no longer support advanced notifications from websites about changes to their site map sitemap.xml https://developers.google.com/search/blog/2023/06/sitemaps-lastmod-ping, This notification feature has also been removed from DataLife Engine. Now, everything happens automatically on behalf of the search engines. You just need to add your address to the search engine's webmaster panel, and the search engines will automatically check and re-index your site.
❑Improved the system for displaying uploaded images and files in the file upload window. To make it more convenient, the file prefix is hidden from the names of the uploaded files. This makes it easier to orientate yourself in the folder. Also, in some cases, the prefix is more accuratelydefined in the name, thus avoiding accidental deletion of part of the name.
❑Fixed an issue where it was impossible to add replies to comments with anti-spam enabled reCAPTCHA v3.
❑Fixed an issue where some additional fields could take incorrect values when rebuilding publications in the control panel.
❑Fixed an issue where comment templates were incorrectly processed in some cases when a comment was submitted by an unregistered user.
❑Fixed an issue where the list of external repositories did not load when uploading images if several different sites were combined into a single user base.
❑Fixed an issue where the cache was incorrectly cleared when approving a comment that was under moderation.
❑Fixed an issue with a user named "noname" who was unable to rate posts and comments.
❑Fixed an issue where, when rebuilding the publications in the admin panel, publications that were not published on the site are included in the search index of publications based on additional fields.
❑Fixed an issue with the user not being able to select some time zones in their profile.
❑Fixed an issue where the publication dates "Yesterday" and "Today"could be incorrectly displayed, if there was a change in day relative to server time, according to the time zone chosen by the user in their profile on the website.
❑Fixed an issue where when viewing full news, the direct transition to the desired comment in the comment block displayed by the {customcomments .....} tag, if present on the page, might not work.
❑Fixed an issue where the cache for full news pages wasn't cleared when editing a publication in the admin panel if the third type of SEO links was enabled in the script settings.
List of changes of 17.0 version:
❑Added the ability for site users to delete their own account on the site, if they so wish. This permission is enabled in the settings of user groups. And it can be selected from several options. You can allow users to make a completely independent decision to delete an account, or you can only allow sending a request to the site administration to delete an account, or even prohibit self-deletion. The admin group is always protected from self-deletion for security purposes against account theft. An administrator can only be removed by another administrator. If the user is allowed to delete himself, then he can delete his account and all his data from the site in his profile by confirming this decision with an additional input of his account password. If sending a request to the administration is enabled, then the user management section for site administrators will show a list of users who have requested the deletion of data and account from the site, and the administrator will need to decide whether to delete this account or reject this request. After the account is deleted by the administrator, the user will receive a corresponding notification that his deletion request has been completed.
❑For the user profile output template (userinfo.tpl), support for new tags has been added: [delete] Text [/delete] that display the text enclosed in them as a link to delete the user's own profile on the site, if he is allowed to do so by the settings of user groups.
❑Added a new “Storage” section in the DataLife Engine control panel. In this section, you can add various external storage systems to which files will be uploaded using the DataLife Engine in the future. Thus, the site can use not one specific external storage for files, but different ones. Moreover, different storages can be used for different needs. In this section, you can add repositories, disable them, assign any storage, default storage, etc.
❑In the script settings in the admin panel, the ability to specify which repositories to upload certain files has been added. You can set up different repositories for images for posts, comments, static pages, user avatars, etc. For all cases, you can set either the default repository or any other repository created in the storage management section.
❑The ability to allow or prohibit users to select storage immediately before uploading files and images has been added to the user group settings. If this feature is allowed to the user, that he will be able to choose before uploading files to which storage they need to be placed. Thus, different files can optionally be placed in different repositories. And if this is prohibited, then the download will be according to all default settings.
❑For additional fields with the types “Uploaded image”, “Uploaded image Gallery”, “Uploaded audio playlist”, “Uploaded video playlist”, and “Uploaded file”, the ability to specify in the settings of these fields to which storage files need to be uploaded has been added. Thus, you can upload different additional fields to different repositories, which are specified in the storage management section.
❑For additional fields of user profiles, the possibility of assigning the “safe field mode” option has been added, with this type of field, the possibility of using BB tags or HTML tags is completely disabled. And also these fields can be safely used when displaying them in the HTML attributes of template tags.
❑When displaying a list of recent comments on the site, an automatic transition to the selected comment has been added when clicking on the headline of the news to which it refers. At the same time, the page on which he is located is automatically searched, if, for example, a comment is on the second page of the news, then the user will automatically get to the second page, and the browser will automatically scroll to this comment. Thus, the user will see it immediately visually. In order to add automatic search when generating custom links in the template, you need to add the attribute to the links: onclick="findCommentsPage(this, '{id}', '{news-id}'); return false;"
❑Added automatic marking of avatars uploaded by the user with a unique value of the avatar file name. Thus, each time a user uploads an avatar for his account, his name will automatically change, and the new avatar will be visible immediately after downloading, without using the cache from the browser. Thus, it is no longer necessary to clear the browser cache when the user changes the avatar on the site.
❑Added the ability to quickly attach images to comments, while quickly editing comments on the site. If the template for adding a comment uses tags to display a quick upload form and attach images to the comment, then when editing, a quick upload image form will also be automatically added to the comment.
❑Added the ability to quickly attach images to comments when responding to comments. If the template for adding a comment uses tags to display a quick upload form and attach images to the comment, then when responding to comments, a quick upload image form will also be automatically added to the comment. Thus, the possibilities when adding a new comment and when adding a response to a comment will be identical.
❑For custom output of publications using the {custom ...} tag, the possibility of custom assignment of the period for which the block should be cached in the cache parameter has been added. You can specify the period in minutes, hours, or days. Values with the suffixes “m”, “h” and “d” are used to specify the caching time. For example, if you specify {custom cache="30m"....}, the block will be forcibly cached for 30 minutes if you specify {custom cache="2h"....}, then the block will be cached for 2 hours, if you specify {custom cache="1d" ....} then the block will be cached for one day. If you simply specify {custom cache="yes"....}, then as before, automatic cache control will be enabled and it will be updated as the information is updated. Specifying the time of forced caching will save server resources if the block does not need to be updated immediately, for example, when adding new publications or comments.
❑For custom output of comments using the {custom comments ...} tag, the possibility of custom specifying the period for which the block should be cached in the cache parameter has been added. You can specify the period in minutes, hours, or days. Values with the suffixes “m”, “h” and “d” are used to specify the caching time. For example, if you specify {customcomments cache="30m"....}, the comment block will be forcibly cached for 30 minutes if you specify {customcomments cache="2h" ....}, then the block with comments will be cached for 2 hours, if you specify {customcomments cache="1d" ....} then the block with comments will be cached for one day. If you simply specify {customcomments cache="yes"....}, then as before, automatic cache control will be enabled and it will be updated as the information is updated. Specifying the time of forced caching will save server resources if the block does not need to be updated immediately if the information on the site changes.
❑For the DataLife Engine control panel, full support for languages using the right-to-left text writing method has been added. To do this, the “direction” directive has been added to the language packs, which specifies the type of writing text for this language ‘ltr’ or ‘rtl’. At the same time, if the right-to-left writing type is used, then DataLife Engine will connect a specially prepared and adapted CSS file with control panel styles for the control panel, which will correctly mirror the entire control panel. Thus, users can use the panel design necessary for this language.
❑For WYSIWYG visual editors, support for languages using right-to-left text writing has been added. To do this, the value of the “direction” directive is also used, which is set in language packs when creating a translation into the desired language. By specifying the right-to-left spelling of “rtl” in the directive, editors will automatically use this text writing mode.
❑For all the usual text fields that DataLife Engine generates in the control panel and on the site, automatic support for languages using right-to-left spelling has been added. Switching occurs automatically as soon as the user starts writing text in this language. Thus, the integration and creation of websites in these languages has been improved and facilitated.
❑In the user group management section, the ability to enable or disable permission to use the “Headers, descriptions, meta tags” module has been added. Thus, you can allow other user groups to use this section, and not only for administrator groups.
❑In the user group management section, the ability to enable or disable permission to use the “Cross-references” module has been added. Thus, you can allow other user groups to use this section, and not only for administrator groups.
❑In the user group management section, the ability to enable or disable permission to use the Redirects module has been added. Thus, you can allow other user groups to use this section, and not only for administrator groups.
❑For the Redirects module in the control panel, the ability to disable or enable redirects has been added. Thus, if necessary, you can temporarily disable or enable the redirect you need without having to delete and re-add them.
❑For the “Cross-references” module in the control panel, the ability to disable or enable keywords has been added, thus, if necessary, you can temporarily disable or enable the replacement of the words you need without having to delete and re-add them.
❑For the module “Headers, descriptions, meta tags” in the control panel, the ability to disable or enable the specified rules has been added. Thus, if necessary, you can temporarily disable or enable the specified rules for these pages without having to delete and re-add them.
❑In the admin panel in the publication editing section, a visual display of the number of publications found has been added when using advanced search by various parameters.
❑In the script settings, the ability to specify how many found publications to show in the results of a quick search on the site has been added. Previously, only five found results were always displayed, now you can specify your desired value in the settings.
❑Changes have been made to the logic of the quick search. Now the search results, if they do not enter the window in height, do not directly block the search field itself.
❑For the total rating of the user's publications, the use of a new {ratingscore} tag has been added in the output templates of the user profile and the user's quick card (userinfo.tpl and profile_popup.tpl). This tag displays the number of the average rating of all the user's publications, from one to five, while maintaining a fractional value. For example, depending on the rating, it can be 1.6 or 4.2, etc. This tag allows you to set, for example, your own design of rating stars with partial filling, and not just 2 or 4 filled stars.
❑For the total rating of user comments, the use of a new {commentsratingscore} tag has been added in the output templates of the user profile and the user's quick card (userinfo.tpl and profile_popup.tpl). This tag displays the number of the average rating of all user comments, from one to five, while maintaining a fractional value. For example, depending on the rating, it can be 1.6 or 4.2, etc. This tag allows you to set, for example, your own design of rating stars with partial filling, and not just 2 or 4 filled stars.
❑Changes have been made to the operation of the [active] ... [/active] tag for the category menu template. Now this tag displays the text enclosed in them for the parent categories, if the category that the site visitor entered is a nested subcategory of these parent categories. Previously, this tag outputs text only for one category, directly in the one in which the visitor was. Thus, you can highlight, among other things, the active parent categories.
❑Added a correct system for calculating the hash of uploaded files directly by content, in case they are uploaded to external storage.
❑Added support for calculating the digital control signature of files uploaded to external storage, if the file arrives at external storage, bypassing the server where DataLife Engine is installed, for example, if the file is downloaded from an external site by URL, and not from a computer.
❑Changes have been made to the logic of the site search. Now data is transmitted to the server using GET requests, not POST. Thus, site visitors, when navigating through the search results pages, will be able to use the “Back” button in the browser, as well as overload the page without warnings from the browser.
❑For the TinyMCE visual editor, the ability has been added when writing comments to insert images from the clipboard and by transferring images to the editor and automatically upload them to the server, if a simplified form of uploading comments is enabled and used for uploading comments. That is, you can use both a simplified form and insert it into the editor text, or automatically upload it to the text field in the editor itself.
❑For the TinyMCE visual editor, the ability to insert drop-down lists (Accordion) has been added, as well as the ability to manage them. These lists are inserted using HTML5 tags “details” and “summary".
❑When viewing uploaded files online on the site, the ability to view files has been added, and when the file download blocking setting is enabled when accessing from other sites. Previously, viewing became unavailable because access to viewing sites occurred from external Google and Microsoft services.
❑Improved the system of uploading files to the server from external sites. Added the ability to upload files if the URL contains not simple direct links to the file, but using various parameters in the links.
❑Improved selection of parent categories when creating and editing categories. If there are a large number of categories, they can be found using a quick search through the list of categories.
❑The system of logging out and logging out of the user on the site has been improved. If the user leaves the site, then a complete cleaning of all data from the browser is performed, including those that were installed by third-party plugins and scripts on the site.
❑Changes have been made to the logic of processing tags [if field = "value"] text [/if], now they are executed before the connection and processing of tags {custom ....} and {include file=”....”}. Thus, you can use these tags inside these structures without creating an excessive load on the server and executing them only if the conditions of the structure in which they are located are met.
❑After uploading video or audio files to the server, the link to insert the player is now selected by default when selecting the insert. Thus, inserting media files is faster when writing publications.
❑Updated instructions for creating an application on the Google service for using authorization on the site using Google accounts.
❑The system of searching for similar news when editing publications in the control panel has been redesigned. Now the system of this search takes into account which search mode is enabled in the script settings: “Simple” or “Full-text".
❑The speed of the search for similar news in the publication editing section has been increased when using the full-text search mode on large databases with a large amount of content.
❑The work with the cache in the control panel has been optimized, which in some cases allows you to clear the cache of some data more rarely when performing a number of actions. This reduces the load on the server and increases the performance of the site.
❑Improved the performance of the site, in case of execution of any automatic programs on the crown. The cache is now cleared more accurately and only if necessary if any data in the database has been changed. This reduces the load on the server.
❑Improved the system for generating a control signature required to perform various actions for users who are not authorized on the site. This signature no longer depends on the IP of the users, thereby they will not be denied to perform an action on the site if the IP address has unexpectedly changed between the actions.
❑The TinyMCE visual editor has been updated to the current version. Various minor errors in the editor's work have been fixed.
❑Fixed an issue where the {THEME} tag was incorrectly processed when using it in the template for displaying the results of a quick site search.
❑Fixed an issue where information about the tag cloud and cross-references was not updated if the publication was automatically removed from the site by the crown, if the deadline for its publication on the site expired.
❑Fixed an issue where in some cases the name of the button for uploading video files for additional fields with the type “Downloadable video playlist” could be displayed incorrectly.
❑Fixed an issue with incorrect display of the section for editing additional fields of publications and users in the DataLife Engine control panel.
❑Fixed an issue where nested comments were displayed one level less than specified in the setting: “Maximum nesting level of comments" in the script control panel.
❑Fixed an issue where when disabling comments on the site, the user sorting of publications by views on the site stopped working correctly.
List of changes of 16.0 version:
❑Added support for two-factor authorization using one-time passwords from the Google Authenticator application or any other applications that support one-time OTP passwords. The user can choose in his profile which two-factor authorization he wants to use. He can choose to use applications, or a one-time password will be sent by E-Mail. Any applications that support OTP verification can be used for use, including the built-in tools of smartphone operating systems, not just Google Authenticator.
❑Added support for a new type of captcha on the Cloudflare Turnstile Sites website. This type of captcha provides the highest quality protection against spam bots, and also works as comfortably as possible for site visitors who do not need to make a choice of annoying pictures or writing text. Everything is as simple as possible, automatically and quickly.
❑Added the ability to limit the number of downloads for files uploaded to the site. To do this, in the settings of user groups, you can specify for this group how many files per day they are allowed to download. At the same time, downloads of unique files are recorded, and not just download attempts. For example, you have allowed downloading five files a day, a visitor has downloaded five files, and he will be prohibited from downloading any other files after that, but if some file was corrupted or accidentally deleted during downloading, then these files that he has already downloaded, he can also download again without problems. If you do not want to set a download limit, then this restriction can also be disabled.
❑Added a new type of additional fields for publications: “Video playlist". In this field, you can quickly upload video files that will be displayed on the site as a ready-made video player with a list of downloaded files to play them. Thus, you can quickly and conveniently organize the publication of videos on your website. In the properties of the field, you can set the maximum number of uploaded files, as well as the maximum file size allowed for uploading.
❑Added a new type of additional fields for publications: “Audio playlist". In this field, you can quickly upload audio files that will be displayed on the site as a ready-made audio player with a list of downloaded files to play them. Thus, you can quickly and conveniently organize the publication of audio files on your website. In the properties of the field, you can set the maximum number of uploaded files, as well as the maximum file size allowed for uploading.
❑Support for full-text search has been added to the quick search system on the site. Now a quick search on the site, depending on what is enabled in the settings, will also use either full-text or simple search. Thus, the results of a quick search will not differ from the results from the full search section on the site, if the full-text search mode on the site was enabled.
❑For a quick search on the site, support for the template system has been added. Now a new fastsearchresult.tpl template file is used to output search results, in which you can use all tags without exception that the short news output template supports. Thus, you can output additional fields and design the results the way you want without any restrictions.
❑When editing comments on the site, if the uploaded images are displayed using the {images} tag in the comments, a list of uploaded images is added to quickly remove images from the edited comment.
❑Added output of uploaded images for comments in the admin panel in the comments editing section. Thus, you can immediately see the images if a separate output tag is used for them in the template and they are not in the comment text. And you can also quickly delete uploaded images in one click, if necessary.
❑The ability to specify the properties of RSS feeds that are used on the site has been added to the script settings. These properties are used to determine which tags are allowed in the stream, their standards, and so on. You can specify properties for all three streams used on the site. These properties are necessary for various services that use these streams in their work, thus, if some service has changed the requirements for RSS feeds, you can independently specify the necessary parameters in the settings without having to wait for DataLife Engine updates or edit the script files yourself. You can also use streams in general for some other proprietary services, and set the necessary parameters yourself.
❑The ability to hide the short description field when adding and editing publications has been added to the script settings in the admin panel. You can disable this field if you do not use it when writing publications, so that it does not interfere with you. This innovation will be useful for those who use, for example, only additional fields with their own properties.
❑The ability to hide the full description field when adding and editing publications has been added to the script settings in the admin panel. You can disable this field if you do not use it when writing publications, so that it does not interfere with you. This innovation will be useful for those who use, for example, only additional fields with their own properties.
❑Support for new tags has been added for the news addition template (addnews.tpl): [allow-shortstory] text [/allow-shortstory] which output the text enclosed in them if the support for the short description field is enabled in the script settings, and hide the text if this field is disabled. Tags have also been added: [allow-fullstory] text [/allow-fullstory] which output the text enclosed in them if the full description field is enabled in the script settings, and hide the text if this field is disabled.
❑Added the ability to sort publications by the date of their editing. The sorting order can be performed in the script settings in the control panel, on the site by the user himself if allowed, as well as in the settings of each category separately.
❑Added the ability to save database backups to external storage. To do this, you can enable the “Save backups to external storage” setting in the script settings. When this option is enabled, the backup will be automatically transferred to external storage.
❑Added the ability to automatically convert uploaded images to one selected format in the format script settings. Instead of setting up automatic conversion of uploaded images to WebP format, you can choose one of four formats: PNG, JPG, WEBP, AVIF. Or you can disable automatic conversion to another format altogether and the image will remain in the format it was originally in.
❑Added the ability to use not only jаvascript tools for deferred image loading, but also native browser support. Now in the script settings you can choose the type of deferred download: Disabled, enabled using jаvascript, and enabled using native browser support. Native browser support works more accurately and faster, does not require loading additional scripts to the page, but it is supported only by modern browsers. Not all visitors to your site may have such browsers. If the user uses the old browser, he will see the image in any case, but the delayed download will not work for him.
❑For image output tags and embedded frames (img and iframe), the ability to add an attribute has been added loading="lazy" when adding publications. To add native deferred loading of images and frames by browsers that support this attribute.
❑Added support for new global tags: [category-description] text [/category-description], which output the text enclosed in them if the category being viewed has a given category description. And also added tag support: [not-category-description] text [/not-category-description], which output the text enclosed in them if the category has no description. These tags will be useful when designing various template blocks for cases when a description is set, and for cases when there is no description.
❑For users who are in the “Editors-in-Chief” group, the ability to change the author of publications has been added. Previously, only site administrators had such an opportunity.
❑For the plugin system, the ability has been added to specify several plugins that are required to be present in the system for the plugin to be installed to work. To assign multiple plugins, their names are separated by commas. Previously, it was possible to specify only one mandatory plugin.
❑Added automatic switching to a dark theme in the DataLife Engine control panel (if automatic night mode is enabled) depending on the installed operating system theme. Now switching will be not only by time, but also if the theme of the operating system has been switched to dark, then switching will also be performed in the control panel.
❑Added support for a new tag for the RSS output template {full-story limit="X"} which outputs the text of the full news without HTML formatting, while the publication text itself is reduced to the specified X number of characters.
❑When using comparison using tags [if field = "value"] text [/if] for additional fields with the type “date” and “date and time”, automatic verification has been added as date values. When comparing, you can use the date in English format, for example, "2020-09-01" or "10 September 2020" or "next Thursday" or "+1 day" or "next Thursday" or in unix format, and also use not only the equal sign, but also check whether the date is greater or less than the specified value. Previously, this type of fields was compared simply as a text value.
❑Improved comparison system using tags [if field = "value"] text [/if] when using the values of additional fields in comparison. Additional conversion of previously escaped characters into regular characters is performed, which simplifies comparison.
❑Simplified system of extended registration on the site, the visitor will need fewer steps during registration when passing the extended registration on the site.
❑For templates for displaying short and full news, as well as for the main page template (shortstory.tpl, fullstory.tpl, main.tpl) added support for new tags: [xfvalue_X video="Nr"] which outputs the videos uploaded for an additional field with the type "Video playlist" with the selected number separately. Where "X" is the name of the additional field, and "Nr" is the number of the video from the playlist, [xfvalue_X video-url="Nr"] which outputs uploaded URLs for an additional field with the "Video playlist" type, individually. Where "X" is the name of the additional field, and "Nr" is the number of the video from the playlist, [xfvalue_X video-description="Nr"] which outputs the video descriptions uploaded for an additional field with the "Video playlist" type, separately. Where "X" is the name of the additional field, and "Nr" is the number of the video from the playlist. [xfgiven_X video="Nr"] text [/xfgiven_X video="Nr"] which output the text enclosed in them if the video with the specified number is present and uploaded in an additional field, where X is the name of the additional field, and Nr is the number of the video, [xfnotgiven_X video="Nr"] text [/xfnotgiven_X video="Nr"] which output the text enclosed in them if the video with the specified number is not in the additional field, where X is the name of the additional field, and NR is the number of the video. All these tags will be useful when using your own third-party video players to organize video viewing on your site.
❑For templates for displaying short and full news, as well as for the main page template (shortstory.tpl, fullstory.tpl, main.tpl) dded support for new tags: [xfvalue_X audio="Nr"] which outputs the videos uploaded separately for an additional field with the "Audio Playlist" type. Where "X" is the name of the additional field, and "Nr" is the number of the audio file from the playlist, [xfvalue_X audio-url="Nr"] which outputs uploaded URLs for an additional field with the "Audio Playlist" type, individually. Where "X" is the name of the additional field, and "Nr" is the number of the audio file from the playlist, [xfvalue_X audio-description="Nr"] which outputs the descriptions of the audio file uploaded for an additional field with the "Audio Playlist" type, separately. Where "X" is the name of the additional field, and "Nr" is the number of the audio file from the playlist. [xfgiven_X audio="Nr"] text [/xfgiven_X audio="Nr"] which output the text enclosed in them if the audio with the specified number is present and loaded in an additional field, where X is the name of the additional field, and Nr is the number of the audio file, [xfnotgiven_X audio="Nr"] text [/xfnotgiven_X audio="Nr"] which output the text enclosed in them if the audio with the specified number is missing in the additional field, where X is the name of the additional field, and Nr is the number of the audio file. All these tags will be useful when using your own third-party audio players to organize audio on your site.
❑The formation of the meta tag of the title of the page when displaying the main page has been changed if the use of the static main page as the main page is set. Now only the main header specified in the script settings in the control panel is used in the header.
❑The system of quick editing of comments on the website and in the control panel has been improved. In case of any error, an error message will be displayed to the user in a pop-up window, while the possibility of making further changes to the comment will remain to eliminate the errors that have occurred.
❑Improved support for additional fields having the “One line" type with the safe mode option. For these fields, the ability to use URLs as content has been added, and they can be used to insert links in publications.
❑Changes have been made to prevent the occurrence of links to publications whose length exceeds the total URL length limit of 255 characters set by the standards.
❑The system for displaying reduced copies of images has been updated. The appearance has become even more modern, smoother animation has been added, more zoom levels.
❑Added the use of more cryptographically secure algorithms in various random value generators used by various user identification functions.
❑For the TinyMCE visual editor, the ability to set the text size quickly and conveniently in any values, and not just from a list of predefined sizes, has been added.
❑For the Froala visual editor, the ability to use any font icons in texts has been added, not just FontAwesome old versions.
❑Significantly accelerated the work of DLE and reduced the load on the server when generating RSS feeds for Turbo pages and Yandex Zen.
❑Added the ability to assign new keywords to the tag cloud in mass actions on publications, to use special characters in these tags, such as quotation marks and a number of others that are supported by the tag cloud.
❑For the [mediа=...] tag, the ability to insert short videos (shorts), as well as playlists from the Youtube service, has been added. Previously, it was possible to insert only regular videos.
❑The system of automatic transliteration of links for SEO URLs has been improved, so that when forming links, the remnants of HTML entities do not fall into these links.
❑When writing additional fields in a publication with the “Cross-references” option, if the tag was written using a different letter case, then when displaying this field in bread crumbs and meta tags of the title, a word with the same letter case as it was written in the publication will be used, and not in small letters as it was previously. At the same time, the URL remains unchanged as before.
❑When writing words for a tag cloud in a publication, if the tag was written using a different letter case, then when displaying this tag in bread crumbs and title meta tags, a word with the same letter case as it was written in the publication will be used, and not in small letters as it was before. At the same time, the URL remains unchanged as before.
❑The minimum requirement for DLE is the presence of PHP 8.0 and higher on the server. Previously, the minimum version of PHP was 7.4. In addition, the recommended requirements for the PHP version were lowered, now it is also enough to have the PHP 8.0.x line, not 8.1.x, for all DLE functions to work
❑The TinyMCE visual editor has been updated to the current line.
❑Fixed an issue where comments were combined into a single line when using the BBCODES editor for comments.
❑Fixed an issue where extra lines appeared when massively combining comments on the site, in the case of using visual editors for comments.
❑Fixed an issue where when changing the search bar in the search, there was no return to the first page of the search if the user is not on the first page and uses only the keyboard.
❑Fixed an issue where the {related-ids} tag in the full news template worked incorrectly when the publication was first shown on the site.
❑Fixed an issue where checking some fields in the [if field = "value"] text [/if] tag did not work when connecting custom output of publications using the {custom ...} tag
❑Fixed an issue where it was impossible to add new keywords to the tag cloud in some cases when performing mass actions on news.
❑Fixed an issue where some buttons in the BBCODE editor might not be pressed in some cases when quickly editing publications on the site.
❑Fixed a problem in which a non-valid layout was formed in the case of using a tree layout of comments, if the nesting limit of comments was reached.
❑Fixed an issue where the image upload button for additional fields with the “Image Gallery” type could not be unlocked when transferring an image from one gallery to another.