|
<< Click to Display Table of Contents >> Navigation: General Information > List of changes |
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.
List of changes of 15.3 version:
❑Added automatic support for uploading HiDPI (Retina) images and screenshots for publications and static pages on the site. In the image upload manager, before uploading an image, you can specify that the image is an image with a high pixel density, for example, this is a screenshot taken on a HiDPI (Retina) screen, and DataLife Engine will automatically create two copies of the image when loading, one for normal screens, the second for high-density screens, and when viewing the site by a visitor, in the case of if he has a high-density screen, he will see a high-density pixel image, and if a normal screen, then a normal image. The same thing happens for smaller copies of images. Thus, you can automatically publish high-quality high-definition screenshots on your website. As an example of implementation, you can view the images published in this news. The insertion of high-definition images is supported only when using visual editors when writing a publication.
❑The display of thumbnails copies of images with an increase to the original size has been completely redesigned and transferred to the use of modern JS libraries. The image gallery display has also been redesigned. Now you can easily change the visual appearance with the help of your templates, all elements of the gallery are adapted using vector graphics, and the display of images has become comfortable on any devices, including mobile devices with gesture support for comfortable viewing of enlarged images.
❑Database queries have been redesigned when displaying short news on the site. These queries were optimized when working with large databases containing a large number of publications. When navigating through the pages of short news, sampling from the database is now much faster, and consumes significantly less server resources.
❑The RSS feed generation system of your site has been redesigned. Due to the fact that Yandex and DZen have separated, it is now impossible to form content in a single stream. Therefore, DataLife Engine now broadcasts three different streams simultaneously for different services. At the address http://yoursite/rss.xml RSS is broadcast in a common format for various systems and services and fully complies with RSS 2.0 standards. At http://yoursite/rssturbo.xml RSS feed of publications for Yandex Turbo is broadcast, and at http://yoursite/rssdzen.xml RSS feed of Zen publications is being broadcast. Now the threads are completely independent and do not intersect with each other and work separately. The same applies to the separation for the categories of the site and user publications. You can see in detail all the addresses for RSS feeds in the documentation for the script. Also, in this regard, the template format for RSS feeds has been changed. New tags [rss] ... [/rss] are used for the standard RSS block, [turbo]... [/turbo] tags are used for the turbo news block, the [dzen] ... [/dzen] tags are used for the zen news block. After the update, you need to bring your RSS template in line with the new mode of operation. As an example, you can take the standard template templates/rss.tpl from the distribution archive.
❑Added support for WebDAV external storage for uploading and storing images and files. The type of this storage is selected in the script settings in the control panel. The parameters for connecting and using this storage are also set there.
❑Added the ability to fully edit publications on the site for users who are allowed to edit publications, but access to the DataLife Engine administrative control panel is prohibited. Previously, only quick editing was available to them, but now they can fully edit news with all fields, including blank additional fields. To do this, the module for adding publications on the site is used, the user will edit the news on the add page, while the filled fields will already be filled in, and he can make only the necessary edits or supplement the fields not previously specified in the publication.
❑The ability to set a list of domain names for which the insertion of iframe tags is allowed has been added to the script settings. Thus, you can independently specify a list of secure domains from which you insert content for your publications. You can also completely disable the permission to insert iframe tags in publications on your site.
❑In the script settings in the control panel, the ability to enable and disable the output of PHP errors has been added, if they occur in the code. It is recommended to enable this option for the duration of technical work, for example, before updating the script or before installing plugins, so that in case of errors, you can see them visually. This setting allows you not to change the server settings to enable this feature, and not to view the server error logs to see the problem.
❑Added a system for automatically resetting the cache of static JS and CSS files for browsers for all site visitors. When you click the "Clear Cache" function in the DataLife Engine control panel, a special unique cache ID will be reset, which is used by the script when connecting static CSS and JS files. If you connect styles and scripts in the template using the {include tag...} then the browser cache will be reset for them as well. Thus, when making, for example, changes to template styles, you can reset the cache, make sure that all visitors to your site, without exception, immediately see the updated information and layout, without waiting for the cache in their browsers to become outdated.
❑A new global tag {cache-id} has been added for all templates, which outputs the current current cache ID, which you can use in templates when connecting your static files, bypassing such internal DLE functions as {include file=....}, and their browser cache will be automatically reset when the site administrator clicks on the button "Clear cache" in the control panel. For example, you can use the <link href="{THEME}/font/style.min.css?v={cache-id}" rel="stylesheet" type="text/css"> construct to a static style file.
❑The exterior design of the TinyMCE visual editor has been redesigned. The display of the menu has been removed, all its functions are displayed immediately in the form of buttons, so that there is a more convenient visual access to the functions of the editor, without the need to search for them in various menus.
❑For the TinyMCE visual editor, the ability to quickly design blocks with preset styles has been added. You can, for example, make the design of an information or warning block in one click, set the boundaries of the block, etc. Which makes the design of publications easier and faster.
❑For the TinyMCE visual editor, the ability to select preset classes for images when inserting and editing them has been added, which you can arrange in your template at your discretion. Thus, you can quickly put the design you need to the images immediately in one click.
❑When writing comments and personal messages on the site using the TinyMCE visual editor, the ability to quickly insert a user's login with a link to his profile has been added. It is enough to type the @ symbol and then start typing the user's login, DataLife Engine will automatically search the user database and offer options for automatic insertion. The inserted content after publication is automatically converted into a link to the user's card, when you click on it, you can see information about the user, write him a message and visit his profile.
❑The online document viewing service on the site has been replaced by a service from Microsoft, instead of the one previously used by Google. This ensures more complete compatibility when viewing, and support for additional new formats available for online viewing has also been added. Full list of supported formats: "doc", "docx", "docm", "dotm", "dotx", "xlsx", "xlsb", "xls", "xlsm", "pptx", "ppsx", "ppt", "pps", "pptm", "potm", "ppam", "potx", "ppsm", "odt", "odx"
❑Added the use of full-fledged editors for the RSS News Import module. Depending on which editor was enabled for publications in the control panel, it will be automatically connected and used when editing a short publication and when receiving a full publication.
❑When importing publications in the control panel from various RSS sources, automatic conversion of links to images has been added if they specify a path without a domain. For example, if there is a link on the source site "/image/file.jpg ", then it will be automatically converted to a link including the source domain "https://domain.com/image/file.jpg ", thus the images will be displayed correctly in publications.
❑Added automatic pre-filtering of incorrect HTML code when receiving full news in the module for importing publications from various RSS sources. After receiving the content according to the HTML template that you set for the RSS source, it will be pre-filtered for unsupported or unclosed tags, will be completely filtered and only then displayed in the editor for further editing.
❑For template parameter files (info.json), which is located in the templates folder, the ability has been added to specify which type the template belongs to, light or dark. To do this, use the parameter "type": "light" to indicate that the template is light and "type": "dark" to indicate that the template is dark. When you enable that the template is dark, all visual editors will automatically switch to the dark color mode and will have the corresponding dark design, without having to make edits to the template styles manually.
❑For full news output templates (fullstory.tpl), the use of a new {related-ids} tag has been added, which outputs a list of similar publication IDs for this news. This tag is useful when used together with the {custom ...} tag, for example, the {custom id="{related-ids}"} tag will display all similar news for this publication with support for all possible template tags, unlike the basic {related-news} tag, in which the supported tags are significantly limited in order to ensure greater performance. Thus, you get more opportunities to design publications on the site.
❑For the personal message output template (pm.tpl), support for a new tag has been added: {login}, which outputs the login of the author of the personal message, without any additional design.
❑For the personal message output template (pm.tpl), support for a new tag has been added: {date=date format}, which outputs the date in the format specified in the tag. Thus, you can output not only the whole date, but also its individual parts. The date format is set according to the format adopted in PHP. For example, the tag {date=d} will display the day of the month of the news or comment publication, and the tag {date=F} will display the name of the month, and the tag {date=d-m-Y H:i} will display the full date and time.
❑For user profile output templates, comments, personal messages (comments.tpl, pm.tpl, userinfo.tpl, profile_popup.tpl), support for a new tag has been added: {lastdate=date format}, which outputs the user's last visit to the site in the format specified in the tag. Thus, you can output not only the whole date, but also its individual parts, or use your own date format, rather than the default one. The date format is set according to the format adopted in PHP. For example, the tag {lastdate=d} will output the day of the month, and the tag {lastdate=F} will output the name of the month, and the tag {lastdate=d-m-Y H:i} will output the full date and time.
❑For user profile output templates, comments, personal messages (comments.tpl, pm.tpl, userinfo.tpl, profile_popup.tpl), support for a new tag has been added: {registration=date format} which outputs the date of user registration in the format specified in the tag. Thus, you can output not only the whole date, but also its individual parts, or use your own date format, rather than the default one. The date format is set according to the format adopted in PHP. For example, the tag {registration=d} will output the day of the month, and the tag {registration=F} will output the name of the month, and the tag {registration=d-m-Y H:i} will output the full date and time.
❑Automatic tag usage has been added for meta tags of your site pages <link rel="preconnect" href="http://yourwebsite.com/" fetchpriority="high">, which allows you to leave the browser connection open, and not open it again when accessing other pages of your site. This allows you to slightly improve and speed up the responsiveness of your site, especially on slow Internet connections.
❑In the script settings, in the file upload settings section, the ability to set which access rights will be set to files when they are written to the server has been added. There are two modes available for selection: "Public" and "Private". When using private mode, full access rights will be set only for the owner of the file on whose behalf the files are uploaded to the server. When using public mode, full rights will be set for all server users. By default, public mode is used, but for some external servers that use the S3 protocol, it is necessary to enable private mode. For example, the Cloudflare S3 service. This provides more extensive support for various cloud services for data storage.
❑The ability to set the size of packages when uploading large files to the server has been added to the script settings. When uploading large files, these files are split into separate packages so as not to exceed the limits set on the server. You can specify the size of the data packet that will be sent to the server at a time, it is specified in megabytes. The fewer packets are sent, the faster the upload to the server will take place. And you can set your own packet sizes, depending on the specific settings of your server limits.
❑Added automatic filtering of adding files to the queue when uploading them for publications. If there is a limit on the number of uploaded images or other files for publication, the user will not be able to add more files to the queue than he is allowed to. Moreover, filtering for images and other files occurs independently of each other, and each limit is taken into account separately. Thus, the user not only clearly sees that he has already exhausted the limit and cannot add more, but also unnecessary data and files are not sent to the server, thereby saving server resources.
❑When uploading images to comments on the site, an automatic restriction on queuing files has also been added, if a maximum limit is set on the number of images that can be uploaded for comments.
❑Added automatic removal of the tag cloud map from the site map, if tag cloud support is disabled in the script settings, or if there are no keywords for the tag cloud.
❑Added automatic removal of the static page map from the site map, if there are no static pages on the site.
❑Added automatic removal of the category map from the site map, if there are no categories on the site.
❑For comments and personal messages, the output of the date of the comment or personal message has been changed when using the {date} tag. When displaying the date, a more extended accounting of how much time has ago since the message, if minutes have, it will indicate how many minutes have ago, if hours, how many hours have ago, if less than a week has, the day of the week and time will be indicated, etc. Thus, it will always be clearly visible how old this comment is.
❑For template tags {registration} and {lastdate} that display the registration date and the date of the user's last visit, the output of this date has been changed throughout the site where they are used. When displaying the date, a more advanced accounting of how much time has passed since this date has been introduced. If minutes have passed, it will indicate how many minutes have passed, if hours, then how many hours have passed, if less than a week has passed, then the day of the week and time will be indicated. Thus, it will always be clearly visible, for example, the last activity of the user on the site. For example, I was on the site 20 minutes ago, or yesterday at 12:20, etc.d.
❑When quoting comments on the site, automatic addition of the date of the quoted message when it was left has been added. At the same time, if a little time has ago, then for ease of reading, it is indicated how much time has ago since the message. For example, 10 minutes ago. Also, as this time passes, this information is automatically updated on the site.
❑In the settings of the Datalife Engine control panel, the ability to set the scaling of the control panel has been added. All panel elements are scaled proportionally, which will allow some users to work more conveniently with the control panel.
❑In the settings of the Datalife Engine control panel, the ability to enable additional font smoothing has been added, which allows you to see more comfortable text on some monitors.
❑All rules are in files.htaccess for managing the Apache server has been rewritten in such a way as to simultaneously support all Apache lines, both the 2.2.x and 2.4.x lines, even if some modules are disabled.
❑Added support for DataLife Engine JS scripts on some types of browsers embedded in TVs.
❑Added support for uploading images and files for additional fields of publications using the "Drag & Drop" method. To start downloading files, it is enough to move the file with the mouse from the computer to the area where the download button of this field is located.
❑The rating for publications on the site was switched to using data-xx attributes instead of using id attributes in HTML. Thus, you can use the rating output in several places at the same time in one publication, for example, at the bottom and at the top of the publication, for more convenient rating on the site. The automatic update will also happen in several places at the same time where it was installed.
❑The rating for comments on the site has been switched to using data-xx attributes instead of using id attributes in HTML. Thus, you can use the rating output in several places at the same time in one comment, for example, at the bottom and at the top of the comment, for more convenient rating. The automatic update will also happen in several places at the same time where it was installed.
❑By persistent numerous requests, the automatic transfer to a new line has been removed after inserting the user's nickname in the comment field, in cases of responses to comments with tree comments disabled. And when using visual editors, a quick insertion of a link to the user's card will be used.
❑When switching themes and operating modes of the control panel, automatic rebuilding and updating of the TinyMCE visual editor has been added to the panel settings window without the need to reload the page. For example, when switching to a dark theme, the editor will also automatically update completely and switch to using a dark theme without overloading the page.
❑The navigation system in the RSS import management module of publications in the DataLife Engine control panel has been improved.
❑Improved the visual design of the Froala and TinyMCE editors when using a dark theme in the DataLife Engine control panel
❑Added a new additional color scheme for the DataLife Engine control panel. It is aimed at a warmer display of the panel, while a more contrasting perception of the content. We hope that users will like the new additional scheme. This scheme is optional, and is enabled in the panel settings, all previously existing schemes are also preserved.
❑Updated internal third-party libraries, as well as jQuery and the TinyMCE visual editor to the latest versions.
❑Added the ability to upload images in AVIF format to the server if the GD2 library is used on the server. This feature is used only if PHP 8.1 and higher is installed on the server, and there is also support for decoding image data from the server.
❑Added support for PHP 8.2.xx
❑Fixed an issue where checking for some fields in the short news output template for the tag [if field = "value"] text [/if] from those described in the template documentation did not work.
❑Fixed a problem where uploaded images to comments that the news has could not be deleted if the news itself was deleted from the site.
❑Fixed problems with possible incorrect operation of inserting emoticons in the TinyMCE editor when using the site on two different http and https protocols at the same time.
❑Fixed an issue where caching of comments output using the {custom comments ....} tag did not work
❑Fixed an issue where the TinyMCE visual editor was displayed incorrectly when editing comments on the site when using a dark theme in the DataLife Engine admin panel.
❑Fixed an issue where there were problems when using uploading images and files in Yandex browser.
❑Minor issues in the script that were detected and stated earlier have been fixed.
List of changes of 15.2 version:
❑Added an automatic notification when going to edit a publication that the publication is already being edited, if it is currently being edited by another user. This feature is enabled in the script settings in the control panel. This innovation will be especially useful if there are a large number of editors and moderators on the site, so that they can see that another person is already engaged in this publication.
❑Added the ability to simplify, quickly and conveniently upload images to comments. Now you can simply place comments in the template (addcomments.tpl) the {image-upload} tag, which will display a special field where the user can drag and drop images to upload, or select them from the computer. At the same time, the user will not need to download anything separately, everything will be downloaded automatically as soon as the user clicks the add comment button. At the same time, having placed the files, if desired, he can remove them even before sending a comment, or change their sorting order. If a quick download tag is placed in the template, the normal file upload button will automatically turn off in the editor, and it will not be displayed. And if the tag is not placed, then loading and inserting images will be as before. You can display all uploaded images in comments in the comments output template in any place convenient for you with specially provided tags.
❑For the comments output template (comments.tpl), support for new tags has been added: [images] text [/images] that show the text enclosed in them, if images were uploaded to the comment, as well as the {images} tag that will output all images uploaded for the comment as an image gallery. This image gallery can enlarge the reduced copies by clicking and flip through the images among themselves.
❑The settings for the permission to insert images into the comment text and the permission to upload images to comments have become completely independent. Now you can prohibit inserting images into the comment text, but at the same time allow uploading images to comments and displaying uploaded images in strictly designated places in the comment output template using the {images} tag.
❑When adding files and images to the server, the ability to preview the files added for uploading has been added in the upload module. After adding files, the download will not start automatically immediately, and the user can view the files that he added, if erroneous files are added, he can delete them from the download queue. Also added a choice for the user how to display a list of files, he can view them as a list or as icons. The user's choice is automatically remembered for subsequent downloads.
❑Added the ability to sort the order of priority of uploading images and files to the server, directly before uploading, after selecting files, the user can change the order by simply transferring files from the list to the desired order.
❑Added the ability to rename the names of uploaded files, for this, after adding files and starting upload, just double-click on the file name and edit the name by specifying a new one.
❑Added the ability to upload files to the server of any size, regardless of the settings and limitations of the server software. Often, the server has small limits on the maximum size of the file transferred to the server, and to download large files, it is necessary to increase the server limits, which is not always possible, and also requires more memory consumption. Now DataLife Engine automatically splits the transferred file into parts and sends the file in parts until it is fully loaded, and already combines it into a single file on the server. Thus, you can upload files to the server regardless of the hosting limits, and only the restrictions set in the DataLife Engine settings apply, for example, you can upload files weighing several gigabytes with hosting limits of only 2 megabytes for downloading files by setting such permission only in the DataLife Engine settings.
❑Changes have been made to the loader of images and files, in case any error occurs during loading. Now the error notification will not be automatically removed from the screen, and the user can remove it by clicking on the corresponding button on the notification. Thus, the user will have enough time to read the error.
❑When selecting files on the computer that the user will upload for publications to the server, file filtering has been added by file extensions that are allowed to upload to the site, and only those files whose extensions are allowed will be available for selection. Thus, the user can immediately select only what is allowed, and prohibited files will not be available for selection. This will allow the user to immediately avoid errors that the file is incorrect and not allowed to download.
❑For extra fields of publications with the type: "Text", "Image" and "Image Gallery", support for a new option has been added: "Use lazy load for image". Thus, you can configure separately for each field whether or not to use deferred loading for this content, and turn it on for some fields and turn it off for others.
❑In the settings of user groups, the ability to transfer a user to another group when a certain rating of comments is set has been added.
❑For the module "Filter by: IP, Login or E-Mail" in the DataLife Engine admin panel, a search system has been added, which allows you to quickly find the desired banned account. Also, the search is conducted for the reason of the ban, thereby you can also quickly sort the banned users.
❑For the module "Filter by: IP, Login or E-Mail" in the DataLife Engine admin panel added a split into several pages in case there is a large number of addresses. Thus, navigation and management of blocked users becomes easier with a large number of them.
❑The TinyMCE visual editor has been switched to using the current 6.xx and updated to the current version. The new line works faster and more reliably with modern browsers, using their internal APIs and functions for parsing content.
❑When using the TinyMCE on the site as the main one for publications, the ability to automatically create a table of contents of the publication with links to the titles when writing a publication has been added. Automatic content is arranged based on the presence of headings in the text (H2 - H6 tags).
❑Added automatic browser cache reset for the TinyMCE editor in case of updating the DataLife Engine to a new version. Thus, the browser will always automatically download up-to-date copies of the editor's JS files, and users will not have to update the browser cache themselves when updating the site to newer versions of the DataLife Engine.
❑The design of the TinyMCE editor on the website has been finalized and improved, and closer integration has also been made with the change of the design themes of the admin panel with the editor.
❑Added the ability to insert fragments of source codes in the comments on the site when using a visual editor.
❑Redesigned the style of displaying and managing uploaded images in additional fields in the admin panel and on the site. Now their display corresponds to what is used in the file loader.
❑Added support for nested include of template files using the {include file="...."} with full retention of tag support in pluggable nested templates. Previously, only a single attachment was supported, after which tag support was automatically disabled to avoid nested endless looping. For example, previously you could connect the template {include file="header.tpl"} in main.tpl by use tags from the main.tpl template, but you could not connect another one from the header.tpl template, for example, menu.tpl with use tags from main.tpl. Now it's possible. You can connect header in main.tpl.tpl from header.tpl will connect menu.tpl, and from menu.tpl connect category.tpl, etc. and the functionality of the template tags of the parent template will be preserved everywhere. In order to avoid layout errors and endless looping, the maximum nesting level is limited to 200 sub-templates, which is enough for templates of any complexity.
❑For the template system, the ability to connect CSS and JS files using the {include file=...} tag has been added. At the same time, files connected in this way will be connected in the corresponding sections, where other service JS and CSS files of the Datalife Engine are, regardless of the location of the {include ...} tag in the template. Also, if CSS and JS compression is enabled in the script settings, these files will also be merged and compressed automatically along with other files. An example of using this tag in a template: {include file="{THEME}/css/styles.css"} will indicate that you need to connect this file to the main block with CSS files. You can also connect external files that are located on other sites and domains in this way
❑Added new global tags for templates: [script] code [/script] in which you can place use executable jаvascript code. In this case, the data code will be placed directly in the executable block of other DataLife Engine JS codes, it will be launched immediately after loading other JS scripts that are used when included. Thus, you can organize all the JS codes in the template, standardize their execution order, and avoid any conflicts in the future.
❑ Support for new tags has been added for the full news template (fullstory.tpl): [allow-comments-subscribe] text [/allow-comments-subscribe], which show the text enclosed in them, if the user is allowed to subscribe to comments. Thus, you can make a link to subscribe to comments in the block you need and hide it if the subscription is prohibited.
❑For the comment adding template (addcomments.tpl) added support new tags: [allow-comments-subscribe] text [/allow-comments-subscribe], which show the text enclosed in them, if the user is allowed to subscribe to comments. Thus, you can make a link to subscribe to comments in the block you need and hide it if the subscription is prohibited.
❑For the comment adding template (addcomments.tpl) added support new tags {comments-subscribe} which outputs a checkbox for subscribing to comments in the form of adding a comment. Now this checkbox will not be forcibly displayed together with the editor, but you can place it in the template in the block you need and in the visual design you need.
❑For templates for displaying the full news and adding a comment (fullstory.tpl and addcomments.tpl) added support for new tags [comments-unsubscribe] text [/comments-unsubscribe] which show the text enclosed in them as a link to unsubscribe from comments to this publication. Thus, users can unsubscribe from only one specific news on the site, previously they had to unsubscribe from all publications.
❑For user profile templates (userinfo.tpl) added support new tags for comparing values. For example, the tag [if field = "value"] text [/if] outputs the text enclosed in them if the field values are equal to the specified value.
❑For the "Redirects" module, support for redirecting to external sites has been added. Previously, the redirect was carried out only once for the user, then it was blocked. Now, when visiting a link on your site, from which there is a redirect to an external site, such a transition will always be carried out, regardless of how many times the visitor visits this link.
❑In the script settings in the admin panel, the ability to set permission or prohibition to change the sorting order of categories assigned for publication has been added. If this setting is enabled, the categories will be in the order in which they were selected by the user when adding the news (the first selected category will be the first, the second the second, etc.), and if the settings are disabled, the categories will be sorted in the order in which they are sorted in the category management section, regardless of how they are adds the author when adding a publication.
❑Added the ability to use the output tags of additional fields of publications [xfvalue_X] as parameters for the user output tag of publications {custom ...}, if it is used in a common template main.tpl. For example, you can use such constructions as {custom tags="[xfvalue_test]" template="test"} to display publications by a specific tag specified in the additional news field.
❑Added the ability to add a user to the ignored list directly when viewing his profile on the site. To do this, for the user profile view template (userinfo.tpl) added tag support: [ignore] text [/ignore] which show the text enclosed in them as a link to add the user to the ignored list.
❑For the user card output template (profile_popup.tpl) added support for new tags [ignore] text [/ignore] which show the text enclosed in them as a link to add the user to the ignored list..
❑Expanded the ability to ignore users on the site. Namely, a ban on sending e-mail messages from the user has been added if the recipient has it in the ignored list. Thus, if one user has added another to the ignored ones, then he will not receive not only personal letters, but also e-mail through feedback on the site.
❑The system of counting publication views has been redesigned and improved. Now the views of the publication are counted only from real visitors using the browser to view the publication. Any robots scanning pages, bots, parsers, etc. will not be taken into account. Thus, the counter of views of publications will become more logical and objective.
❑In the script settings, has been added to specify after which period of time the user is on the page read the full news, it is necessary to count the page view. If the user has been on the page for less than the specified amount of time, the viewing from him will not be counted. Thus, you can ignore visitors who are on the page clearly less than necessary to read your publications.
❑Changes have been made to the operation of the "Trusted Categories" setting in the group settings, for users who are allowed to edit any news. Now, if a list of trusted categories is set, the user will not be able to edit the publication data of other users at all, even if they are being moderated and not published. Thus, you can create your own moderators directly for certain sections of the site, and they will not have access to other categories of the site.
❑Added a display of the number of publications for a category in the category management section in the control panel, if counting the number of publications for categories was enabled in the script settings.
❑Added preventive measures to protect against accidental deletion of personal messages when performing mass actions on personal messages. Now, if deleting messages is selected, then this action will need to be confirmed.
❑New methods have been added to optimize the calculation of the number of publications in categories, if previously such calculations were already performed by other DLE functions, as a result of which, in some cases, the number of requests in the database is reduced and the load on the server is reduced.
❑Added the use of script settings: "Set the NOREFERRER parameter for external links" for publications and comments also on links that are published using the link encryption tag [lееch=...] ... [/lееch]. Previously, referral transfer was always blocked for such links, now depending on the script settings in the admin panel.
❑For publications that are divided into several pages, added correct formation of meta tags for social networks that maintain these pages. Now each page will lead exactly to the page that it corresponds to. For example, if the user shares the second page, then the link will lead to the second page and not to the start page of the publication.
❑For publications that are divided into several pages, added correct formation of links for micro markup Schema.org . Now each page will also lead to exactly the page that it corresponds to.
❑The formation of description meta tags and keywords has been redesigned, for publications that are divided into several pages. Now the description that was set in the admin panel when adding the news will be used only for the first start page, and for subsequent pages, these meta tags will be generated based on the content of these pages. Thus, the meta tags of different pages will not be duplicated, which has a positive effect on the overall SEO of your site.
❑Changes have been made to the system of notifying users by e-mail about new comments on the site, if they have subscribed to receive such notifications. Now, if tree comments are used on the site, and this is a response to any comment, then only the author of the comment that was answered will receive a notification (if he is subscribed to such notifications), while other users subscribed to this news will not receive it for comments, but will receive notifications only if it is a new comment that is not a response to another previously added comment. Thus, sending notifications will be more logical, users will not receive notifications when commenting on discussions in which they do not participate.
❑Changes have been made to internal links to various sections located inside the main index file of the Sitemap. Links are now formed in such a way that maps are always hierarchically higher than internal links on the pages of your site. Which theoretically has a more positive effect on the SEO of the site. This is an internal optimization, no action is needed to change any links to maps in search engines.
❑The system of highlighting the published source code on the site has been redesigned and improved. The definition of languages is now more correct, and eliminates errors in the definition with the code type already selected. The source code highlighting library has also been updated to the current version.
❑The use of control panel fonts has been redesigned and improved, thereby improving the readability of text when using various devices. The use of the control panel using smartphones has also been improved and optimized. Font sizes in the control panel have been converted to relative scalable values, and are now tied to the operating system and browser settings. Thus, if you have increased the size of the base font in the browser settings, it will automatically work in the control panel on your site, which is convenient for users with disabilities.
❑Due to the need to support new functions and features, as well as optimize the script on the server for higher performance, the PHP 7.xx line has been declared obsolete and it is recommended to update the server software to version 8.1 and higher.
❑Fixed an issue related to incorrect text validity when inserting video and audio content using a standard DLE player into the publication text.
❑Fixed an issue where some site functions might not work if different groups have different settings for using captcha Google Recaptcha v.3
❑Fixed an issue where when loading an icon for a category, directly when creating a category, the icon was loaded to an external server if it was connected for other functions.
❑Fixed an issue where the publicly available file option was displayed when uploading images to comments.
❑Fixed an issue where information about uploaded images in the shared image and file loader could not be updated if the image was loaded during direct transfer to the TinyMCE editor.
❑Fixed an issue where errors could occur when updating from very old versions of the DataLife Engine.
List of changes of 15.1 version:
❑Added the formation of a site map designed for the Google News service, this map is formed automatically when forming a map of your site in the corresponding section of the control panel.
❑ The format of creating a Sitemap for Google and Yandex search engines has been completely rethought. Now a separate file with a map will be created for different sections of the site, which in turn will be combined into a single index file. For example, a map of static pages will be in one separate file, links to categories in another, etc. At the same time, for search engines, you specify a link, as before, only one to your site, for example, http://вашсайт.ru/sitemap.xml and it will automatically combine all the created maps of your site.
❑ In the admin panel, in the site map management section, the ability to save the installed map settings for further use has been added. For example, you can set up the necessary priorities once and save them, and they will always be used, including when automatically creating a map through the server's crown.
❑When forming the site map, the possibility of adding a parameter of the probable frequency of page changes to it has been added. You can set not only the priority for pages with publications, categories or static pages, but also how often such pages are expected to change, which allows a more optimized approach to the search indexing of your site's pages.
❑When forming the site map, the ability to set the number of links to publications in one file has been added. You can assign how many links you need to put in one file as much as possible, and if there are more links to the map, it will be divided into more files. Reducing the number of links reduces the memory consumption for creating a site map. You can put no more than 40,000 links in one file, so as not to exceed the limits already on the part of search engines.
❑When forming the site map, the date of the last update of the news pages is now set in full format, when the last update was, including also the time and time zone, and not just the day of the last update. Which also has a positive effect on the search indexing of the site and faster updates by search engines.
❑In the admin panel in the image management section, the use of paginated navigation has been added if there are a large number of images in the folder. This significantly speeds up the loading of the image management page and improves image management capabilities.
❑Added a search engine for plugins in the plugin management section in the control panel. You can quickly find the plugin you need by any key value. At the same time, the search is conducted throughout the plugin system and values. For example, you can specify part of the name or description, or you can also specify the name or part of the name of the file being modified or part of the code in the file, the search will be carried out everywhere and you will be shown a list of plugins that fall under the search query.
❑In the script settings in the admin panel, the ability has been added to set where to use a shared folder for images, if external storage is also used. You can specify separately whether to use a shared folder from an external storage or from a local one.
❑If there is a limit on the number of uploaded images for a publication or comment, then when uploading images, a convenient output of information is added for the user how many images in total he can upload, how many he has already uploaded for publication and what limit is still left. Thus, the user understands even before uploading how much he can still upload for publication.
❑If a limit on the number of uploaded files is set for publication, then when downloading, a convenient output of information is added for the user how many files in total he can download, how many have already uploaded for publication and what limit is still left. Thus, the user understands even before uploading how much he can still upload for publication.
❑For mass actions on publications, in the publication editing section, the ability to assign additional new keywords for the tag cloud to existing ones has been added. Thus, you can choose either to completely massively reassign all the words, or simply add new additional ones to the existing publications.
❑In the admin panel in the "Tag Cloud Management" section, the ability to specify the sorting of output tags has been added. You can sort the output both by tag name in alphabetical order and by the number of publications. At the same time, sorting can be specified both in descending and ascending order. This way you can quickly find the necessary tags to edit or delete. For example, display the most unpopular tags first, or vice versa, frequently used, etc.
❑Added support for structured data schema.org for static pages on the site.
❑In the category settings in the admin panel, the ability has been added to specify for each category, if necessary, which type of structured data schema.org use it when displaying publications from this category. You can set both global settings and change them separately for the desired categories. For example, in some categories there may be news, in others software or books, etc.
❑Added the ability to specify in the script settings whether or not to transliterate characters when generating the URLs of publications, categories, and static pages. For example, if you enable this option in the script settings, when generating the publication URL, it will look like: http://yoursite.com/id-imja-novosti.html , and when disabled, it will have the form: http://yoursite.com/id-имя-новости .html, also by analogy and when forming categories and static pages. This innovation will be especially useful for SEO optimization of sites in national languages other than English.
❑For the IndexNow protocol, which is used to automatically notify search engines, support for notifications when adding and editing static pages on the site has been added.
❑Added the ability to insert posts from Telegram channels into your publications on the site using the tag [mediа=....]. In this tag, just a copied link from the browser is indicated, and then all the necessary code will be generated automatically by DataLife Engine. For example, to insert a post, you can use: [mediа=https://t.me/vamtlgrm/185]
❑Added support for the HCaptcha service (hcaptcha.com ) to check whether the visitor is a bot or not. This service is enabled in the script settings in the admin panel, as well as Recaptcha and acts on all sections where verification is enabled and required.
❑Added support for a new global tag {page-count} that displays the number of the page the user is on. This tag is global, and can be used in any tpl template files. This tag will be especially useful in using various advertising, for example from Yandex, where you can specify additional parameters for the page number where the site visitor is located, for a more correct advertising display on the site.
❑Added support for lazy loading of images when displaying the content of publications from additional fields directly in the main template main.tpl
❑Added the formation of links from the tag cloud when forming the sitemap. In addition to links to categories, publications and static pages, links to all words existing in the tag cloud will now also be added to the sitemap.
❑Added support for notification of changes in the site map for the Yandex search engine.
❑Changes have been made to search engine notifications about updating the site map. Links to search engine notifications have been updated to current ones.
❑Added the ability to use the symbol: "|" when writing descriptions to images in additional fields of publications. Previously, this symbol was a reserved service symbol and could not be used in the description of images.
❑The display of publications on the tag cloud has become completely case-insensitive, for example, the search for "News" and "News" will be the same regardless of the case in the URL. At the same time, in order to avoid duplicates in search engines, DataLife Engine generates links using only lowercase letters, and when using a different register, the control of incorrect NC will produce 301 redirects to the correct single address.
❑The display of publications when using additional fields with the "cross-references" type has also become completely case-insensitive, for example, the search for "News" and "News" will be the same regardless of the case in the URL. At the same time, in order to avoid duplicates in search engines, DataLife Engine generates links using only lowercase letters, and when using a different register, the control of incorrect NC will produce 301 redirects to the correct single address.
❑For short and full news output templates (shortstory.tpl and fullstory.tpl), has been added new tags for displaying data from additional fields with the image gallery type: [xfgiven_X image="NR"] text [/xfgiven_X image="NR"], where X is the name of the additional field, and NR is the number of images that display the text enclosed in them if an image with the specified number is present and loaded in an additional field. And also added support for opposite tags: [xfnotgiven_X image="NR"] Text [/xfnotgiven_X image="NR"], which output the text enclosed in them if the image with the specified number is missing in the additional field. Thus, you can very flexibly organize the format and design of uploaded galleries for publications.
❑In the script settings in the admin panel, the ability to specify the Score value when using reCAPTCHA v3 has been added. This value is used to check the probability with which the user can be a robot when using the reCAPTCHA v.3. This field can take a value from 0 to 1, where, for example, 0.1 means that it is most likely a robot, and 0.9 is most likely a person. Since the degree of probability may vary on different sites, you can assign a probability based on Recaptcha statistics directly for your site. Recommended default value: 0.5.
❑Redesigned and improved verification using Recaptcha v.3 whether a visitor is a bot or not. The number of false locks has been reduced, especially if a person writes a text for a long time or fills out forms for a long time.
❑The system of protection against resending data when adding a publication to the site has been redesigned and improved. Protection triggers were eliminated when opening a large number of tabs, even in an interval of less than a second, and protection triggers were also eliminated in case of problems with PHP sessions, for example, if they expired if the user writes a publication in the browser for a long enough time.
❑For static pages, the limit on the template file name that can be assigned for use by this page has been significantly increased. This innovation is especially useful if subfolders are used in the template structure, and now the name of the assigned template will not be truncated.
❑When uploading a new plugin to the site in the script admin panel, if there is no information in the plugin file about which of the sections should be enabled or disabled (for example, old plugins created on old versions of the script), then these sections will be enabled by default. Previously, when adding such plugins to the site, all actions were disabled by default.
❑In the script settings in the admin panel, a setting has been added to specify the parameters by which the original image should be cropped, if its maximum dimensions are set, and only the value of one side is specified. You can choose "By the largest side", "By width" and "By height".
❑For the module for managing comments awaiting moderation, support for splitting into several pages has been added, if there are a large number of comments. This simplifies the loading of the list of comments and their moderation with a large number of comments on moderation.
❑For the IndexNow protocol, which is used to automatically notify search engines of new publications, the use of a single notification point has been added, which in turn will notify all other search engines connected to this protocol. Using a single point allows you to reduce the time for notification of all systems, and as a result, faster news saving.
❑For the IndexNow protocol, in case of any error when notifying search engines, instead of an error code, a text transcript of this error is immediately displayed, which allows you to immediately determine the cause of the problem, instead of having to read the documentation of search engines, for what this error code means.
❑When forming a file for RSS export, the correct removal of unsupported content has been added, in cases where it is necessary. For example, descriptions of images used in <figcaption> when exporting to Yandex News.
❑Внесены изменения в работу функции включения и отключения комментариев для каждой публикации в отдельности. В случае если отключаются комментарии для публикации, но при этом у данной публикации уже есть добавленные комментарии, то уже существующие комментарии будут продолжать отображаться на сайте (ранее они выключались и не отображались), но при этом будет запрещено добавление новых комментариев, а также ответы на существующие комментарии.
❑Changes have been made to the automatic notification of search engines about the appearance of new content, for more correct recognition of script users' errors, and their automatic correction, which could allow writing domain names of their sites in the script settings in violation of the requirements of URL standards, for example, using different letter case, which in turn led to the fact that search engines the systems did not accept the sites.
❑The behavior of dynamic loading of comments when displaying the full news as comments are viewed has been redesigned, if the order of sorting comments is selected in descending order (i.e. if new comments are shown first). Previously, comments were loaded incorrectly, only when scrolling up to the beginning of comments. Now they load correctly when scrolling down the page.
❑The Jquery UI library has been updated to the current version, when used on the Jquery 3.xx website. A number of errors in the operation of this library have been fixed.
❑Updated typographic text processing. A number of errors have been fixed and the placement of quotation marks for text has been improved.
❑The graphics driver for image processing has been updated to the current version, which has improved support for PHP 8.1 and higher.
❑The TinyMCE visual editor has been updated to the current version.
❑The DLE video player has been updated to the current version
❑Fixed an issue where when selecting any S3 compatible storage, the settings were not displayed: "Path to files on an external server" and "HTTP address for external storage".
❑Fixed an issue where in some cases incorrect processing of the contents of the [mediа=...] tag could occur.
❑Fixed an issue where when adding the first bookmark on the site, the profile displayed that two publications had already been added to bookmarks.
❑Fixed an issue where inserting data from some services using the [mediа=...] tag might not work.
❑Fixed an issue where OpenGraph meta tags for static pages were duplicated.
❑Fixed an issue where when using the TinyMCE editor, additional <p></p> tags were inserted at the end of the content if, when editing the source code, the cursor was placed at the very end of the text.
List of changes of 14.3 version:
❑We have added a completely new system for managing files and images uploaded to the server. As a result, external storages for images and files uploaded to the website are now supported. You can specify where to store the uploaded files in the script settings on the admin panel. You can store the files locally on your server, or choose an external FTP or SFTP server. You can also select cloud services like Amazon S3 or Yandex.Cloud. The new system for storing and managing uploaded files is based on the Flysystem 2.0 unified file system. This enables you to avoid any troubles when employing a custom external storage of your choice, because now you can rely upon the plugin system and do not need to customize a lot of DataLife Engine files. Upon adding a new adapter, DataLife Engine will be able to use it automatically when needed.
❑We have completely redesigned the upload manager for images and files meant for publications. The new manager makes it easier to view uploaded images, their size in preview has been increased, and it has become easier to select uploaded files. It has become much easier to remove a required file or image. Reopening the manager is carried out instantly, because now it is rendered on the page only once and then keeps its state in the background so that all further actions are performed using AJAX technology. The options you select for uploading images will persist for as long as you work with a publication and will not be reset every time you open the image upload manager.
❑The image upload manager has been provided with a capability to preview full-size images directly in the upload manager.
❑The shared folder previously used by the upload manager for locating images meant for publication has been moved to a separate folder named "shared" and located in /uploads/. As a result, shared images are now located in a separate folder. In addition, in this shared folder, you can create your own subfolders with any nesting level. You can also switch to these subfolders and insert images into publications directly in the upload manager. This way you can easily create and organize your library of shared images.
❑In the admin panel section enabling you to manage uploaded images, we have provided a capability to choose the storage that you wish to manage. Depending on your requirements, you can upload images to a local or external storage.
❑In the admin panel section enabling you to manage uploaded images, we have provided a capability to create and remove folders and their nested subfolders. As a result, you can manage your images directly on the DataLife Engine admin panel without having to access your file storage via FTP or by other means.
❑In the admin panel section enabling you to customize the script settings, we have provided a capability to enable or disable the external storage option for uploading images meant for publications. As a result, you can distribute the uploaded images meant for a particular content type among different storage locations. With this option enabled, you do not need to save all the images meant for publications to an external storage.
❑In the admin panel section enabling you to customize the script settings, we have provided a capability to enable or disable the external storage option for uploading images meant for comments. As a result, you can enable the external storage option for uploading images meant for news and disable it for images meant for comments. With this option enabled, you do not need to save all the images meant for comments to an external storage.
❑In the admin panel section enabling you to customize the script settings, we have provided a capability to enable or disable the external storage option for uploading images meant for static pages. As a result, you can enable the external storage option for uploading images meant for news and disable it for images meant for static pages. With this option enabled, you do not need to save all the images meant for static pages to an external storage.
❑In the admin panel section enabling you to customize the script settings, we have provided a capability to enable or disable the external storage option for uploading files meant for downloading. As a result, you can enable the external storage option for uploading images and disable it for other files. With this option enabled, you do not need to save all the files meant for downloading to an external storage.
❑In the admin panel section enabling you to customize the script settings, we have provided a capability to enable or disable the external storage option for uploading user avatars. As a result, you can enable the external storage option for uploading images and disable it for user avatars (or the other way around).
❑We have added automatic detection of MIME file types (for all file types) upon downloading files uploaded to the server via DataLife Engine. This ensures correct downloading and opening of various files on different types of devices, and, as a result, the correct behavior of devices with the file types they support.
❑We have added support for the PHP Imagick library for processing images uploaded to the server. In the admin panel section enabling you to customize the script settings, you can choose whether you wish to use Imagick or GD2; alternatively, you can allow DataLife Engine to choose the library automatically. In general, there are not many differences between GD2 and Imagick. However, Imagick performs some operations with images faster and creates image thumbnails of a better quality, as well as consumes less memory when processing large images.
❑We have added a capability to automatically convert all images uploaded to the server into the WebP format. You can enable or disable this feature in the admin panel section enabling you to customize the script settings. When this option is enabled, all images uploaded to the server, regardless of their format or extension, will be automatically converted into the WebP image format. This format is more advanced and allows you to create higher quality images of a smaller size. However, displaying images in this format requires that a user has a modern browser.
❑We have added a capability to load images in the BMP format. Upon loading images of this type, they will be automatically converted to the JPG format to reduce the file size and speed up the loading of site pages.
❑We have provided automatic file extension correction for image files uploaded to the server if their specified extension does not match their format. For example, if an image actually supports the PNG format but the image file features the JPG extension, the uploaded file name will be automatically changed by specifying the appropriate PNG extension, and a similar logic applies to all other formats.
❑Upon uploading images to the server using the TinyPNG service for image processing, the number of requests to the service has been significantly reduced as well as reliance on its API. As a result, when the number of processed images is limited, you can process more images using the service.
❑We have added a capability to process images in the WebP format using the TinyPNG service. As a result, you can also compress these images as much as possible without reducing their quality.
❑We have added correct handling of possible errors that might occur when users upload avatars for their profiles on the website and the uploaded images feature invalid format or content. For example, if a file content is not recognized as an image, the user will only be notified about an incorrect format of the uploaded avatar instead of throwing a system error due to an incorrect action followed by an emergency shutdown of the website.
❑The "Watermark overlay area" option in the admin panel section enabling you to customize the script settings has been provided with an additional setting that allows you to locate a watermark at the center of an image.
❑A new option has been added to the script settings enabling you to specify the watermark type. You can either choose an image from a template, as was the case in the earlier versions, or apply a text watermark based on text specified in the script settings. Among other settings in this section, you can specify the required text, as well as the font size and color. In this case, the text specified in the settings will be used as a watermark, and you no longer need to create unnecessary watermark images.
❑The script settings have been extended by providing a capability to specify the rotation angle for a watermark applied to an image. The rotation angle is applied both to the image watermark and the text, if its display is enabled.
❑The script settings have been extended by providing a capability to specify the transparency degree for a watermark applied to an image. The transparency degree is applied both to the image watermark and the text, if its display is enabled.
❑RAM consumption during processing images uploaded to the server has been significantly reduced.
❑We have added support for deferred images located in hidden text spoilers in publications. As a result, when loading deferred images is enabled, the image content is displayed correctly upon showing a spoiler.
❑We have changed the algorithms for uploading images to the server. Upon uploading any images to the server, a UNIX prefix bearing a timestamp is no longer added to an image name and original names are preserved in all cases, except for transliteration which is applied only to Cyrillic names. However, if an image with a specified name already exists on the server, a timestamp is added to the name of the newly uploaded image to avoid overwriting the existing file. As a result, DataLife Engine will preserve original names of uploaded images as long as this is possible and will automatically add the necessary prefix only if duplicate names occur.
❑We have introduced automatic removal of a previous user avatar from the server after the user specifies a new avatar with a different image format. This enables saving space on the server.
❑We have provided a capability to display the complete data from a user profile upon viewing results of a search performed across site publications. The same template tags are used for the display as for the output of publications in a short and full format.
❑We have added a capability to display advertising materials to be shown between news displayed in a short format upon viewing results of a search performed across site publications.
❑Templates used for displaying news in a short and full format (shortstory.tpl and fullstory.tpl) now support the following tags: [has-category] text [/has-category]. Text enclosed within these tags will be displayed if the publication belongs to any of specified categories. We have also added support for tags working in the opposite way: [not-has-category] text [/not-has-category]. Text enclosed within these tags will be displayed if the publication does not belong to any category. This enables flexible customization of the template appearance both for publications that have been assigned categories, and for publications not belonging to any category.
❑We have added an automatic check performed upon removing a publication from the site and a subsequent removal of images uploaded for this publication to find out whether these images are used in other publications, in which case they are not removed from the server.
❑The load on the server upon viewing short publications on the website has been significantly reduced. At present, upon viewing short publications, regardless of the website section to which they belong, the total number of pages in a corresponding section is calculated only once, after which the information about the number of pages in this section is cached, so that upon visiting other pages or repeated visits, this information is retrieved from the cache and not from the database for each page as before. This way the number of requests made to the MySQL database is significantly reduced.
❑The load on the server upon viewing last comments on the website has been significantly reduced. At present, the total number of pages featuring comments is calculated only once, after which the information about the number of pages in a corresponding section is cached, so that upon visiting other pages via standard navigation routes or repeated visits to the same page, the information is retrieved from the cache and not from the database for each page as before. This way the number of requests made to the MySQL database is significantly reduced.
❑We have managed to reduce the load on the server upon viewing website pages featuring no content while viewing short publications. In this scenario, some unnecessary requests to the MySQL server will be avoided.
❑For the TinyMCE visual editor, we have introduced automatic creation of an image thumbnail upon loading the image in the editor using drag and drop operation. Following this, both the image and a code for enlarging it will be displayed in the editor if script settings indicate that thumbnails should be created for such images.
❑In the admin panel section enabling you to view and edit user information, we have provided shortcuts for sending a personal message to a user and viewing all publications and comments belonging to a particular user. At present, upon viewing a user profile, you can quickly perform the aforementioned actions without having to switch to other website sections.
❑Changes have been made to the "Share interesting content" feature implementation. At present, to enable users to share text from a particular item, you should specify a class named "share-content" for this item. To exclude any part of this item content, use the "ignore-select" class. This way for any item on the website you can specify which part of its content users can share upon highlighting a text. You can specify multiple items for which content sharing is allowed. When using this feature with regard to viewing short publications, we recommend that you assign to items a unique ID derived from the news ID: for example, by adding id="news-{news-id}" to a template. This will enable you to properly maintain how the publications moves down the line as new ones are added.
❑The following option has been removed from the script settings: "Allow users to share interesting content". This option is now enabled and disabled automatically if the "share-content" CSS class is specified in the item template.
❑Changes have been made to the website main page operation affecting the scenario when a static page or a publication using the {custom ...} tag is assigned to display content on this page. Previously, a website main page could be specified in this way only if its URL displayed in the browser did not contain any parameters. With the new version, the parameters that are not related to DLE will be ignored and the assigned content will be displayed correctly even if the URL contains extraneous parameters. As a result, upon navigating to your website following various advertising campaigns or opening it with additional markers added to its URL indicating advertising campaigns, its content will be displayed correctly without returning a 404 error. For example, this will be the case for visits via Yandex.Direct or other similar services. In addition, to prevent duplicate pages from appearing, search engines employ the system of canonical links inserted in the code of your website pages.
❑The display of publications using the {content} tag and the script logic have been changed so that the additional tag <div id="dle-content"> ... </div> is no longer displayed or used for wrapping external content. This enables easier integration of templates with some HTML frameworks. If you your layout depends on this tag, you should make changes to the CSS layout of your template.
❑In the admin panel section enabling you to edit templates, we have introduced highlighting of the edited template file in the file list. This makes the edited file appear more distinctly and enables an easier navigation through the list of template files.
❑We have ensured the correct removal of special characters from a plugin name upon specifying the name for a created plugin before saving it to your computer. This ensures a more accurate and efficient transliteration of plugin names.
❑For mass assignment of the current date to publications, the publication editing section has been extended to include a one second offset interval for the date assigned to each previous news item. As a result, consecutive news items are indexed correctly when displayed on the website.
❑In the image management section of the admin panel, we have added an automatic overwriting protection system for uploaded images meant for publication. If an image is already present on the server, the user will be informed about this and prompted to change the name of the uploaded image.
❑Changes have been made to the behavior of the "Minimum image size for upload" setting. At present, this setting affects only the uploaded images meant for website publications. It no longer affects uploaded avatars and the image management module on the admin panel.
❑We have improved background loading of JS scripts for some of the website operation scenarios. At present, if these JS scripts have already been cached by the browser, it will use the scripts from the cache instead of repeatedly downloading them from the server.
❑We have updated the TinyMCE visual editor to the current version. This version features new and improved tools for working with tables along with a number of bug fixes. Support for browser context menu has also been added.
❑We have updated the HTML Purifier incoming data parser in the DataLife Engine to the current version. Some new HTML attributes have been supported for text publications.
❑The PHPMailer library included in the DataLife Engine for sending e-mails from website has been updated to the current version.
❑Minimum PHP requirements have been raised to support all new features. PHP 7.2 or higher is now required for correct operation.
❑We have fixed a bug which, upon displaying news in the full format, caused incorrect turnover of advertising materials specified in the admin panel.
❑We have fixed a bug due to which debug information was not returned by the GzipOut function when using PHP 8.xx.
❑We have fixed a bug due to which a MySQL error could occur in some cases when executing cron jobs.
❑We have also fixed some minor script issues detected and reported earlier.
List of changes of 14.2 version:
❑The DataLife Engine installer has been completely redesigned. It is made simpler and more versatile. When installing, you can now choose which language the installation will take place in, as well as which language will be the main language for the site. Depending on the selected language, the corresponding templates will be installed, in the selected language, and the corresponding entries will be made in the database. The entire installation also takes place using AJAX technology in fully automatic mode.
❑ For language packs located in the /language / folder, the ability to specify additional information about the language has been added, which can later be used when displaying a list of languages. For example, the output of the name in the national language, for a more convenient perception of the desired language by a person. Not just the name of the folder where the language pack is located.
❑For templates located in the /templates / folder, the ability to specify additional information about the template has been added, which can later be used when displaying a list of templates. For example, the output of the template name, in the list of templates on the site, for a more convenient perception of the desired template name. And not just the name of the folder where the template is located.
❑Added Ukrainian localization of the Datalife Engine script. The Ukrainian language is now also included in the standard distribution, and will be supported in the future when updating.
❑Added the ability to change the language of the DataLife Engine control panel on the fly, being on any page in the control panel, without the need to log out, and re-enter the control panel. The user of the admin panel can choose any of the languages available in the system.
❑Added the ability to set the order of categories for publications, if the news is allowed to add a publication to several categories. The order of the categories will be set in the order in which they were selected by the user when adding or editing the publication, and not in the order in which they are sorted in the admin panel. For example, if the first category in the list is "In the World", and the second is "Sports", and the user first selected "Sports" and only then "In the world", then their sorting and output from the news will also be observed in this order.
❑Added the ability to view a thumbnail image inserted in a comment immediately after adding a comment, without having to reload the page. If a comment was added that contains a smaller copy of the original image, then viewing the enlarged copy will be available by clicking, immediately after the comment appears on the page.
❑Added the ability to view the original image from a smaller copy of the images for comments, if AJAX navigation or dynamic loading of comments is enabled on the site.
❑Added support for sending the Last-Modified HTTP header for all pages of the site that display short publications, not just full news as previously. In this case, the date of addition or editing is recorded for all publications placed on the page, and the correct date of the last added or edited publication on the page is given.
❑For all pages of the site that display short publications, added support for the return of the HTTP header "304 Not Modified", in case of sending a corresponding request from search engines to the server. This takes into account the dates of adding or editing all publications published on the page, both using the {content} tag and the {custom} tags. This will reduce the consumption of traffic on the server, and significantly speed up the indexing and reindexing of the site by search engines.
❑Added support for displaying advertising materials that are set in the ad management section in the admin panel for templates and publications that are output using the custom output tag {custom ...}. Now you can use the banner tags set in the admin panel in the templates that you assign when displaying publications.
❑For custom output of publications {custom ...} added support for the new banners="yes" parameter, which enables or disables the output of advertising materials that are assigned for output between publications. This parameter can take two values: "yes" to enable output, and "no" to disable output. By default, if this parameter is not included in tags, the display of advertising materials between publications will be disabled.
❑The logic and principles of creating a description meta tag for site pages that displaying short publications have been completely redesigned. Now the description specified in the script settings is used only for the main page of your site, and the description specified in the category parameters is used only for the first page of the category, for all other pages, this meta tag is generated automatically, based on the content of publications that are displayed on this page. Thus, all pages have their own unique description meta tag, which will positively affect the SEO optimization of your site.
❑For the Memcache caching system, a new system for finding keys stored in the cache has been added, which leads to more correct clearing of cache elements and updating the content on the page. This is especially true for loaded projects
❑In the script settings, you can now choose how the form of responses to comments should be displayed, if support for tree comments is enabled. There are three options to choose from: "After comment without editor", "After comment with editor", "In pop-up window".
❑The module "Share interesting materials" has been fully integrated into the DataLife Engine language system and uses language script files to generate information. Thus, when using other languages, switching will be automatic and does not require editing files. Also in this module, checksums are checked for changes to the content, and if it is changed, the text will not be highlighted if the checksum does not match, so that the text that the site user shared with is not highlighted.
❑Updated to the current version of the system for highlighting the source code published in the [cоde] tags ... [/cоde] up to date. In addition, it has been significantly redesigned for better and better automatic recognition of the language of the published code. And also added support for a large number of languages, and various configurations. Now high-quality highlighting is provided not only for HTML or JS, but also for other languages and codes.
❑Redesigned and improved the system for displaying the addition of publications to bookmarks and deleting them, as well as displaying information about whether the news is in bookmarks or not. Now, regardless of whether caching is enabled or disabled on the site, a site visitor will always see up-to-date information when viewing short news, whether his publication is in bookmarks or not, even if caching is enabled. At the same time, the caching functions are not lost in any way and are used.
❑For typographic text processing in editors, the ability to exclude the processing of published content in the BB tags of the source code [cоde] has been added ... [/cоde], as well as in the corresponding HTML tags that are used to publish the source code.
❑The TinyMCE editor has been updated to the current 5.7.x line, and it has also been significantly redesigned for a more comfortable experience. This editor was assigned by default when installing DataLife Engine on the server.
❑For the TinyMCE editor, the ability to upload images to the server is added by simply transferring image files using the "Drag and Drop" method to the editor, as well as uploading images to the server from the browser's clipboard.
❑For the editor TinyMCE added protection against possible accidental data loss when writing publications. For example, if when writing a post and not saving it, you accidentally click on a link that leads to the user leaving the page, then you will receive a warning that the data may be lost and you will need to additionally confirm the action. Also, if the browser freezes or the user leaves the page anyway, the editor can restore the last content saved in the local storage. Auto-save occurs every 20 seconds, and the data for recovery is stored for 10 minutes.
❑Added the ability to edit uploaded or inserted images for the TinyMCE editor. The editing functions contain features such as resizing, changing orientation, mirroring, changing brightness and contrast, etc. The modified image in the editor will be automatically uploaded to the server.
❑For the TinyMCE editor, the ability to control the visual design of the editor's content through templates, when writing a post or comments, has been added. To do this, just place the editor.css file with the design styles you need in the root of your template. This innovation will be useful to ensure that the text that users write is as close as possible to the design of the content that is used in the template. The placement of this file in the template is optional, if it is not available, the standard content design will be used.
❑For the editors TinyMCE and Froala, used on the site for comments, the system for quoting the text of other users comments highlighted on the site has been redesigned and improved. Visual quotes are now used instead of BBCODES tags, and line breaks are added if they are present in the selected text.
❑Changes have been made to the system for uploading images to the server using the DataLife Engine. If the name does not contain a temporary download prefix, it will be added to the name, and if the name already contains this prefix, it will not be added additionally. Temporary prefixes are added to the name to avoid duplicating the names of uploaded files to the server, and thus protect other images that were previously uploaded with the same name to the server from being overwritten. This innovation will be useful in the case of copying images from other sites to DLE or using a similar name tagging system, as it allows you to avoid multiple duplication of the prefix in the image name when copying.
❑For static page templates (static.tpl), support for new tags has been added: {full-link} which outputs the URL for this static page, and {print-link} which outputs the URL of the printable version for this page. These tags will be useful when you need your own design for links on a page, or their special output, for example, for displaying a QR code for mobile devices, etc.
❑Significantly improved the work of the crown on the site. If the crown needs to perform any heavy operations, such as multiple deletion of a large number of users, and the server resources do not allow you to perform everything at once, according to some limits, then the crown will be performed every two minutes until all the necessary actions are performed.
❑Redesigned and improved the AJAX system for adding comments on the site. If the script settings include the merging of comments on the site, and the user adds another comment in addition to his own, then the page will be updated and supplemented with the text of his previous comment. And if the association is disabled, its additional comments will be added sequentially one after another and will all be visible immediately without reloading the page.
❑Significantly redesigned and improved the AJAX response system for comments if tree comments are enabled. The changes have improved the positioning of the added responses, as well as the formation of the DOM structure of elements that no longer use intermediate layers and elements, which allows you to better adapt to the layout of the template.
❑For micro-markup of the rating of publications, the use of the fractional value of the parameter itemprop="ratingValue" has been added, now in this value, instead of an integer value, for example, 4, a more accurate value will be used, for example, 4.3. This will allow search engines to display a more accurate rating scale in the search results.
❑Changes have been made to the system for automatically deleting users if they have not visited the site at the time specified in the settings. If automatic user deletion is enabled in the site settings, users will be deleted from all groups, except for the administrators group. Previously, the deletion was only performed from the standard "Visitors" group, and other groups were not affected.
❑Improved synchronization of the post view counter cache data with the data displayed on the site, preventing uncontrolled accumulation of data in the table, on high-loaded and visited sites.
❑Improved the system of mass mailing of emails in the script control panel in the module "Sending messages". Redesigned the system for handling possible errors when sending emails. If your server did not respond correctly, or any errors or restrictions occurred, then all server responses will be processed correctly. The administrator will receive a detailed response from the server, and will also be given the opportunity to continue sending messages without reloading the page. There are no possible hangups of sending messages without explaining the reasons for mass mailing.
❑Redesigned and improved the site search system, if the search is conducted by keywords containing special characters. For example, quotation marks and other characters. The search, according to these words, is now more correct and relevant.
❑Optimized the display of some control panel elements on mobile devices. Fixed the detected shortcomings in the display of some elements of the control panel pages.
❑The DLE video player has been updated to the actual version, a number of optimizations and bug fixes have been made, and in the case of using videos with adaptive bitrate on the site, the size of the downloaded player code has been significantly reduced, which speeds up the loading of pages where this video is located.
❑Improved the formation of the Open Graph protocol's og:description meta tag when viewing full news. Now, when forming this tag, if there are text links in the text, without generating the code, they are also deleted and not used. For example, if the text contains a link https://site.ru, then it is deleted. This innovation allows you not to participate in the formation of the description of the link, which is simply published in the text additional and other fields. Which makes the description more correct and correct.
❑Improved the system for sending E-mail messages from the site, as well as prevented the possible emergency termination of sending letters if the mailing address of any recipient of the letter is incorrect.
❑Improved DataLife Engine automatic update system. If the automatic update failed due to an unexpected server error, the administrator will be shown full information about the error that the server returned, as well as the response that came from the server, and not just a notification that an error occurred. This information will help the site administrator to eliminate the causes of the problem.
❑Updated the PHPMailer library for sending emails from the site to the actual version.
❑Changes have been made to the system for displaying advertising materials assigned to display "between short news". Now they will always be displayed exactly between the short news, regardless of the number of news items on the page, and will never be displayed before or after the news.
❑Changes have been made to the system of working with template tags [if ..] [/if], in the event that if a shortened output of any information is used, then the search for the specified parameters in these tags will still be carried out by the full value. For example, when displaying abbreviated information on a site with the tag {short-story limit= "200"}, then using [if short_story~ "text"] ... [/if], the search will be performed on the entire short description, and not only on the first 200 characters.
❑Dropped support for PHP line 5. xx. Development and support for PHP 5 was dropped by PHP developers several years ago. We did not make any irreversible and unsupported code changes that would not work on the PHP 5 line, however, this line is no longer supported. DLE testing is not performed on it. The minimum required PHP version is 7.0 or higher.
❑Support for the extended authorization method in the DataLife Engine control panel has been dropped. This method was introduced in DLE version 5.3 and is inherently obsolete. He did not add any additional protection in the current conditions and realities relative to the usual method of protection implemented in the DLE of current versions, and used the same basic password for HTTP authorization. Users who still want to add additional protection to their admin panel can continue to use HTTP authorization, only for this you need to place your file separately .htpasswd and write a path to it in. htaccess. And thus make the authorization independent of the DLE and with an additional password of your own.
❑Fixed an issue where the autofill system did not work for additional fields that have the "cross-references" type, for words that contain some special characters, such as the ampersand character "&" and a number of others.
❑Fixed an issue where the autofill system for the tag cloud did not work if words were used that contained some special characters, such as the ampersand character "&" and a number of others.
❑Fixed an issue where some characters could be displayed incorrectly when quoting comments containing source code insertion tags using the BBCODES editor.
❑Fixed an issue where the "IP Utilities" section in the admin panel did not work correctly when using PHP line 8. xx
❑Fixed an issue where the display of advertising materials with the "between publications" option did not work when using PHP ruler 8. xx
❑Fixed an issue where some tags in the comments output template (comments.tpl) worked incorrectly.
❑Fixed an issue where the cache for RSS feeds from the site was not used and was not used.
❑Fixed an issue where category selection didn't work when using the DLE API in third-party modules on MySQL 8. xx
❑Fixed an issue where additional fields of the "cross-references" type were duplicated when mass removal from moderation of publications that were no longer under moderation, but were previously published.
❑Fixed an issue where the output of additional fields of publications did not work while enabling 3 types of NC and displaying full information from the user profile.
❑Fixed an issue where in the comments editing section in the admin panel, the search keyword was reset when navigating through the pages.
❑Fixed all previously detected and reported minor errors in the script.
List of changes of 14.1 version:
❑Added a feature of displaying user profile data for post's author on the short and full post output templates (shortstory.tpl и fullstory.tpl). As the feature also requires an additional database query, it can be enabled or disabled on the script settings at the optimal performance section. Therefore the feature can be enabled if needed or disabled to improve the script performance and reduce the load on the server. To develop such a feature more than thirty new template tags were added, that contains user profile info, including additional fields data.
❑For comment output templates (comments.tpl) the support of new comparison tags was added. For example, [if field = "value"] text [/if] shows embedded text if field's value is equals to the specified value.
❑Added support of new caching via cache framework Redis. Type of cache framework (File cashing, Memcache или Redis) can be selected on the script settings. If your Redis server requires login and password to connect or password-protected, all necessary authorization data can be specified. To use this type of cache framework a Redis server and a plugin for PHP interpreter php-redis must be installed on the server.
❑Memcache cache was modified. These changes were made to prevent possible issues with auto cash-flush on the high-load projects, because in some cases info about cached keys may be deleted due to lack of cache memory to store it. As a result, caching of other data may take longer than usual.
❑For comparison tags [if field = "value"] text [/if] were added support of other template tags. For example, the following expression: [if autor = "{profile-login}"]Viewed by post's author[/if] shows the specified text, if the post is viewed by its author. This gives more options for template design.
❑To adding and editing static pages in the control panel a viewing feature was added, so a user can see the page right after it was added or modified.
❑To [mеdia=...] tag the support of more than 200 new services and sites was added. In fact, the support of all known sites and services using oEmbed to exchange data and add content to the posts was added.
❑ To template main.tpl support of new tag {cloudstag} was added that shows keyword from the tag cloud, if a user is browsing site category with posts having a specific keyword from the tag cloud. The update may be useful for webmasters who want to display a selected keyword somewhere else, for example, using HTML tags h1 and etc.
❑To categories menu output template (categorymenu.tpl) a feature to show category description on the menu was added. For that purpose new post tags support was added: {description} - shows category description, [description] text [/description] - shows embedded text if description is specified, and reversed tags: [not-description] text [/not-description] - shows embedded text if description is not specified.
❑To categories menu output template (categorymenu.tpl) support of new tags were added: [not-parent] text [/not-parent] - shows embedded text if category is not a parent category and don't have any subcategories. In fact this tag is a reversed tag for [isparent] text [/isparent] tag.
❑To categories menu output template (categorymenu.tpl) added support of new tags: [is-children] text [/is-children] - shows embedded text if a category has a parent category, and support of reversed tags: [not-children] text [/not-children] - shows embedded text if a category has not parent category.
❑Additional field type "Switchbox 'Yes' or 'No'" filling on-site was modified: instead of select HTML tag used input (checkbox) tag. These ensures that a field filling on-site corresponds with field filling on the control panel.
❑To additional fields with "use as cross-link" active property the support of slash "/" symbol was added.
❑For customized comments output {customcomments ....} a new parameter newsid="1,3,5-15" was added to enter ID of posts to select comments from. The parameter can also include template tags from other templates, for example, if a full post contains {customcomments newsid="{news-id}" order="rating"} tag, it shows comments from specified post sorted by rating.
❑For customized comments output {customcomments ....} a new parameter newsidexclude="1,3,5-15" was added to enter ID of posts to exclude from comments display. For example, with tag {customcomments newsidexclude="3-10"} all comments, except from posts with ID 3-10, will be displayed.
❑For customized posts output tag {custom ....} a new parameter subcat="yes" was added. The parameter can be used with options category="list" or categoryexclude="list". The parameter indicates if posts from subcategories should also be included. The parameter can take one of the following values: subcat="yes" indicates that all posts from the category and its subcategories will be selected, subcat="only" indicates that only posts from subcategories will be selected and posts from the category won't. For example, site has only categories with ID 1, 2 and 3. 1 is a category, 2 and 3 are its subcategories. If {custom category="1" subcat="yes"} tag is used then all posts from categories 1, 2 and 3 will be selected. If tag {custom category="1" subcat="only"} is used then only posts from categories 2 and 3 will be selected. This makes the process of entering query parameters more flexible, without listing all categories in the tag. If new subcategories are added on the control panel, posts will be displayed automatically without any need to edit templates.
❑ Keywords from the tag cloud now can contain a slash "/" symbol.
❑Due to Instagram being owned by Facebook, to embed their content on site one must have an application for data exchange registered on their services, so if you add content from Instagram with [mеdia=...] tag to the post, DLE will embed it using the application specified on the script settings for Facebook social network authorization. On application settings on Facebook, access to the content via oEmbed must be allowed. After that adding content from Instagram and Facebook using [mеdia=...] tag will be available.
❑Added a feature to script settings that enable or disable NOREFERRER parameter for all external links in posts. If the setting is enabled, all external links in posts will be marked as NOREFERRER, which does not allow the browser to share with external sites the information of where the user came from.
❑Added a feature to script settings that enable or disable NOREFERRER parameter for all external links in comments. If the setting is enabled, all external links in comments are marked as NOREFERRER, which does not allow the browser to share with external sites the information of where the user came from.
❑After the load of .webm and .m3u8 files they will be auto-processed as video files and can be added to post and auto-played on site using a video player.
❑Added support of sending header "304 Not Modified" for posts, in case of getting the matching request from the search engines. If there were no changes in the post for a given period, DLE sents only short corresponding HTTP with code 304. This allows to reduce bandwidth consumption on the server and subsequently reduce the load on the server.
❑Added more detailed error information for private messages, when an error occurs. For example, if an unauthorized user goes to the private messages section, a notification will be shown, asking to sign in or register to continue. If a user follows a link from a new private message notification email and wants to read it, but is not signed in, the notification will ask to sign in to read the message.
❑Site rules now can be viewed right after being edited via control panel.
❑jQuery library was updated for the latest 3.5.x version, to use it enable jQuery 3 in script settings on the site control panel.
❑Added a feature for Froala visual editor that allows inserting various objects such as sheets, image and video lists.
❑Added Apple music widgets integration for playing music online using iframe tags. Also iframe HTML tags access rights now can be managed using allow attribute.
❑Added new symbols support to the word filter: single quotes (') and ampersand (&). Now you can enter, for example, Jeanne d'Arc or similar words.
❑Added the support of setting "Allow search engines index links posted in comments" for site WYSIWYG visual editors. Before the option was available only if BBCODES editor and BB tagged links were used in comments.
❑For plugins generated posts added the valid source code display, when [cоde] ... [/cоde] tags were used. The highlight of the source code and tags also was added to make the text easy to read.
❑Due to some changes in YouTube algorithms Oembed protocol started to generate code for small videos by default. [mеdia=...] tag logic was also changed, now if you add a YouTube video, DLE video settings will be applied and DLE video height will be calculated automatically. This ensures that video will have the right size comparing to other videos posted on site using DLE player.
❑Page meta-tags such as header, description, keywords and etc. may now contain square brackets and round brackets. Instead of being deleted symbols are converted to valid HTML code in order to be displayed correctly by the browser.
❑Changes had been made to the loaded images display logics for posts. Before the update, only images loaded to the server using the DLE script were displayed in the list and stored on the server. Now, if for some reason the image was completely deleted from the list without DLE script, it will be substituted with a placeholder informing that the image was deleted from the server. It may be useful for sites, where users can add a limited number of images per post, so if an image is missing it can be unlinked from the posts, and the limit for a maximum number of images can be preserved.
❑DLE video player was updated for the latest available version. Several issues with video player availability on various devices and browsers were fixed.
❑Posts inbound HTML code parser was updated for the latest available version. Added support of new HTML parameters attributes for HTML5 support.
❑Changes were made to comments quoting. If a user quotes comment with hidden text and has enough access rights to see hidden text, this hidden text will be included in his own comment with a quotation, including tags of the hidden text. If a user hasn't enough access rights to see hidden text, this hidden text will be excluded from his quote. Before hidden text was always excluded from quotes, even in cases when a user had enough access rights to see it.
❑Added additional check of possible mistakes committed by the site administrator on changing user groups access rights on the control panel. For example, before the administrator could accidentally grant access to all categories and restrict access to some categories at the same time. As a result, some DataLife Engine functions may not work correctly.
❑Added "$" characters support for MySQL server database usernames and passwords.
❑Added PHP 8.xx support
❑The algorithm of canonical link generation was modified for sites using both HTTP and HTTPS protocols. If a user accesses the site via HTTPS or "always use HTTPS" is specified in the settings, then a canonical link will also always be generated using HTTPS protocol, regardless of what preferred protocol was specified for the site in the script settings. Even if no preferences were specified.
❑ Improved meta-tag og:description generation via Open Graph protocol for full post view. Now in cases when additional fields are involved, only text fields will be used for tag generation. It may be one text string or few text strings. All other field types such as images and files will be excluded from the tag generation.
❑Fixed an issue where post links on the control panel and site map were not working, if the post belonged to the category that was disabled on the categories settings.
❑Fixed an issue when on the navigation via control panel some active pages may not be highlighted correctly.
❑Fixed an issue with some private messages preview may not be displayed correctly on the script control panel.
❑Fixed an issue where in some cases after a static page was edited instead of the static pages list user was redirected to the list of posts.
❑Fixed an issue with user unmuting as well as linked social networks deletion for Firefox users.
❑ Fixed an issue with processing categories icons output tags in the short and full post output templates, when other non-standard (shortstory.tpl и fullstory.tpl) file templates were used for category.
❑Fixed an issue with [if ..] ... [/if] tags not working correctly, if a field contains any upper-case characters.
❑Fixed an issue with tags [if ..] ... [/if] not working correctly, if a field contains multiple distinct values (e.g. posts with multiple categories), and the check was performed on the negative value with combined condition. For example, the condition [if category != "1" AND category != "2"] not 1 and not 2[/if] was not working correctly, if the post was published in more than one category.
❑Fixed an issue with tags [not-ios] ... [/not-ios] and [not-android] ... [/not-android] in cases when reversed tags were missing on the template.
❑Fixed an issue where categories were not saved correctly on posts import from RSS feeds to the site.
❑Fixed an issue with canonical link generation failure for post preview containing some additional fields, where CNC was enabled, but a user used a link with disabled CNC. It sometimes occurred, when site settings were modified and the site was indexed by search engines.
List of changes of 14.0 version:
❑We completely redesigned the uploaded image management module in the administration panel. Now you can navigate through all folders in this section, regardless of the nesting level. In addition to standard folders, you can open and manage images in self-created folders. We also added a preview of images – just click on them in full screen.
❑We added support of video with adaptive bit rate (HLS files of .m3u8 format) to the DataLife Engine video player.
❑We added support of new value comparison condition tags to templates for displaying short and full story (shortstory.tpl and fullstory.tpl). For example, the tag [if field = "value"] text [/if] will display the text enclosed in it if the field value is equal to the specified value. This tag can compare not only equality, but also make “more or less” comparisons, find entries.
❑We added the option to temporarily automatically block an account in the website's administration panel when it is inactive. You can specify a time-out in minutes in the script settings, after which, if the user did not do anything in the browser in the administration panel, his/her session will be temporarily suspended until the password is entered. In this case, a user will see a notification and if he continues to do nothing, the session will be suspended. This innovation will be useful for providing additional security, if a user temporarily leaves his computer with an open administration panel tab. To resume the session, it is enough to enter a password without having to enter a login.
❑We added the option to link any available social network account to an account on the website. Website user can link one or several networks to his/her account, and use them in the future to log into his/her own account on the website. In order to link a social network to his/her account, the user must log in on the website, go to his/her profile and make the link there. In this case, you can use any and all accounts on a social network, there are no match requirements, for example, concerning e-mail addresses. To link social networks in the user profile template, the same tags as in the login.tpl template are used for logging in via social networks: {vk_url}, {odnoklassniki_url}, {facebook_url}, {google_url}, {mailru_url}, {yandex_url}
❑We added the option to unlink any of the social networks from the account on the website. Even if it was originally used for the initial login to the website and the first registration. To do this, we added support of the {social-list} tag to the user profile display template, which displays a list of linked social networks and links to disconnect them from this account.
❑In the category settings of the script administration panel, we added the option to assign each category its own rating type for posts. Now each category can have its own type of rating, and not just the common one for the entire website.
❑In the post editing section of the administration panel, we added the option to recount the number of comments for a post. You can recount comments not only for all posts, which is a very long and resource-intensive process, but also recount comments only for a specific post. This function will be useful if you work in the comment database bypassing the DLE, for example, import of information into the database, deleting or incorrect work of third-party plug-ins.
❑In the post edit section of the administration panel, we added the option to recount comments for mass actions for selected posts. Thus, you can recount all comments in one click, only for selected posts.
❑In the post edit section of the administration panel, we added the option to delete all for mass actions for selected posts. Thus, you can delete all comments for selected posts in one click.
❑If any additional field is mandatory, for adding or editing posts we added information display about which field is empty and must be filled in. Previously, a general error indicating an empty mandatory field was displayed, and users had to find which particular field is mandatory on their own.
❑We added the option to load icons for categories directly from the DataLife Engine administration panel. You can load icons in the category management section when adding or editing a category.
❑For the post display templates, as well as for the category menu display template, we added support of new tags: [category-icon] text [/category-icon] show text enclosed in them, if in the category settings an icon was set for the category where the post is located. We also added support of opposite tags: [not-category-icon] text [/not-category-icon] which show text, if no icon is set for the category where the post is located. Thus, you can create the design of your templates more flexibly, depending on whether the category has an icon or not.
❑For the category menu display template, we added a link to the default icon, if there is no link to the category icon for the selected category. Previously, an empty value was displayed as an icon display tag, if an icon was not set in the category settings.
❑We added the option to use the @ and ~ symbols in website search , which served as auxiliary symbols when used for full-text search on tables working with InnoDB.
❑We added support of the Brotli algorithm based data compression for JS, CSS and HTML generated by the DataLife Engine. This method is more efficient and faster than regular zip data compression. To use this compression algorithm, the server must have the appropriate server extensions for PHP. If DLE determines that your server supports this algorithm, it will be used automatically, and if not, then compression will be carried out with available means, for example, zip compression.
❑We added the option to upload and delete images for users who have the right to post stories only after moderation, and at the same time they are allowed to edit posts. For this purpose, changes were made to the image uploading procedure – if the user takes actions to upload or delete images or files, the story is automatically sent back to undergo moderation.
❑We added the option to specify the delimiter character for keywords assigned to the tag cloud in the script settings in the administration panel when they are displayed in posts on the website.
❑We added the option to use the HTML code for category display delimiters and for the breadcrumbs module when they are specified in the script settings. For instance, you can set “</span><span class=”test”>” to create a more flexible and diverse formatting for your template.
❑We added support of lazy loading for Youtube videos posted using the [media = ...] tag, as well as any other content posted using the HTML iframe tag. If you enable lazy loading of images in the script settings, this lazy loading will also be used for the above content. This will also further speed up the loading of your website pages, because the required content will be loaded into the browser only as the user scrolls the page.
❑We added support of lazy loading for images posted in the text of user comments. Previously, lazy loading of images was available only for stories.
❑We also added the account of restrictions in the file upload window appearing when displaying information about the restrictions on the size and volume of uploaded data set in the server settings. For example, if in the script settings for the user it is allowed to upload a file of 5 megabytes in size, and the server settings do not allow uploading more than 2 megabytes, then during upload it will also be indicated that the maximum size is 2 megabytes. This allows you to immediately avoid confusion if there is a discrepancy between the settings of the script and the server.
❑We also added display of the number of files that can be uploaded by the user to the image and files uploading module, if there is a limit on their number in the settings.
❑We added the option to search for posts not allowed for web indexing for advanced search of posts in the administration panel. Thus, you can quickly find posts where you need to change this option.
❑We added the option to search for posts not allowed for web indexing for advanced search of posts in the administration panel. Thus, you can quickly find posts where you need to change this option.
❑We made changes to the behaviour of counting the number of stories for the category menu. Previously, the counting was carried out on the basis of the global settings of whether or not to display stories belonging to subcategories. Now the count is carried out based on the settings assigned individually for each category.
❑We added support of viber://, tg://, skype://, market:// protocols fo links posted on the website. These protocols allow you to open website based links in applications installed on the phone, such as Viber, Telegram, Skype and Android Market.
❑We added compatibility of database transfer from a later version to an older version for the database backup module. For example, the website was originally created on MySQL 8.0 and is transferred to another server where MySQL 5.7 is installed. In this case, the database backup will be created in a format compatible with MySQL 5.7.
❑For instances when the page contains several players with video and audio, we added automatic stop for files played if the user plays video or audio from other players on this page.
❑We made changes to the category menu formation system. If viewing of any categories is not allowed in group settings, and viewing of short stories from these categories is also prohibited, these categories will also be automatically excluded from the display in the menu for this group of users.
❑We updated the DLE video player to the current version, and fixed a number of small bugs and improved video playback on mobile devices.
❑We also added search and replacement in story headlines to the “Search and Replace” module in the administration panel, if search by stories and headlines of static pages is set, as well as search and replacement on static pages.
❑We added automatic verification of logins by keywords specified in the “Word filter” module in the administration panel in the process of user registration on the website. If the filter matches, the user will be denied registration. This feature will be useful if you set a filter for obscene words, there is no need to additionally fill in the names prohibited for registration in the filters intended for registration.
❑We added automatic removal of value display tags of additional fields from the template, in case data for these additional fields are missing. For example, there is an additional “gallery” type field and you display its values not with a single display tag, but separately for each image using the tag [xfvalue_X image =“Nr”], and if any of the images was not uploaded, then its display tag will be automatically hidden. This innovation concerns not only the display of images, but in general the display of any additional fields and their values.
❑We added a ban on sending personal messages to users who are in a group for which the use of personal messages is not allowed. Earlier, messages could be sent, but users could read them only when this ban was lifted.
❑We added automatic saving of sorting of additional user profile fields in the administration panel. Saving is done automatically when the order is changed, you don’t need to press an additional button to save.
❑We added automatic hiding of a comment awaiting moderation in the comment managing section of the administration panel after editing and posting it on the website. Thus, the moderator can quickly move on to processing the next comment.
❑We added automatic recount of statistics in the control panel in case of editing comments awaiting moderation.
❑We made changes to the incoming data filtering system intended for on-site search, in connection with which the search for some keywords has improved.
❑We optimized sorting of additional fields for posts in the administration panel. This adds the option to perform multiple sorting or operations on fields without reloading the page in advance.
❑41. We improved the system for determining the used site protocol http or https preventing incorrect reading of server settings on certain configurations.
❑We improved the incorrect CNC links control system for some sections of the website and links.
❑We updated visual editors TinyMCE and Froala to the latest versions, and fixed a number of identified errors in these editors.
❑We made changes to the vote counting control system concerning post and comment rating that fixed the problem occurring when some users wanted to change their vote and could not do it.
❑We fixed the problem with generation of a link to the full story, if the category was disabled and it was the first category from the list of several categories.
❑We fixed the problem, which caused JS errors when enabling the use of native emoji and disabling the editor for comments.
❑We fixed the problem, which caused interruption of work of additional fields with the uploaded file type in case of rebuilding posts in the administration panel.
❑We fixed the problem, because of which the story options “Publish on homepage”, “Allow comments” and “Allow rating” were not removed automatically when adding or editing posts in the administration panel, if several categories simultaneously had a ban on using these options for the post.
❑We fixed the problem, which caused duplication of the List-Unsubscribe header when sending bulk emails from the website.
❑We fixed the problem, which in some cases caused posted comments to be deleted and incorrect counting of comments when working with comments awaiting moderation.
❑We fixed the problem, because of which the advanced search by comments did not work, if full-text search and comment moderation were enabled in script settings.
❑We fixed the problem, because of which the advanced search did not work, if a time period for comment search was specified.
❑We fixed the problem, because of which the description meta tag was formed incorrectly, if the story was not added or edited in the administration panel, and the content of the post was too small.
List of changes of 13.3 version:
❑We added new video player on the website. The new player is better supported by the relevant browsers and has modern design. Apart from visual improvements the new player has new functional features: it supports "image in image" mode for browsers, and for Apple devices it supports playing videos to other devices through AirPlay. You will also be able to select among colour patterns in player settings on the admin panel.
❑Automatic plugin upgrade is aided by introduction of DLE version transfer to the server, which checks for the availability of new plugin versions. It uses 'version' parameter containing version of DLE script installed in the website. Thus plugin developer's server can check which DLE version is being used, and, depending on that, either provide information on new version availability or not. Besides, it can provide new versions and copies of plugin for different DLE versions. By this we can avoid transfer of new version of plugin to the website with an older DLE version not supported by this plugin. Information on DLE version may be transferred in the form of POST or GET request, depending on availability of certain settings on the website where DLE is enabled; for this reason, it is recommended for plugin developers to check the version using global variable $_REQUEST['version'].
❑We added native emoji smileys in news and comments editors. If you enable this setting, the symbols supported by user's operating system will be used in editor instead of images for smileys. Visual representation of emojis will depend on the device used for content browsing. DataLife Engine supports more than one and a half thousand of emojis. For your convenience we divided emojis into categories and at the top of the list user will find 16 recently used emojis. This way it is no longer necessary to search for frequently used emojis in the full list every time. Native emojis support is enabled in script settings on the admin panel. If this setting is disabled, usual emoji pool based on images, as in the previous version, is used. Native emojis support is added in all three editors of DLE.
❑We added the possibility to enable image processing through TinyPNG for images uploaded to the server. This service provides additional compression of images with no quality loss using advanced algorithms; this allows reducing the image size and consequently accelerate loading of websites. Furthermore, this service will scan images for significant objects (people faces, animals), so the fixed-size copy of this image will automatically contain the most significant information on it. This feature can be enabled in script settings on the admin panel. As this service can be used for free only for certain amount of images per month, you can disable a number of parameters in script settings in order to minimize the use of this service. For example, you can disable using this service for avatars or disable algorithms of smart scanning for significant objects.
❑We introduced new additional field type 'Date and time'. In this field you can insert date and time; you will be able to use pop-up calendar for convenient filling-in. This field has three input types: date and time, only date and only time. In the settings of this field you can also set output type of the specified date to your preference. This field has additional options of date localization, for example, translation to the language used by your website or declension of the chosen date. This field can also be used for cross reference links connecting the news at the website.
❑We have changed colour pattern of the night mode of admin panel. The new colour pattern ensures comfortable use both in the daylight and at night. This was achieved by the use of softer colours.
❑We added the possibility to enable automatic switch to the night mode of control panel through theme settings on the admin panel. Time the panel will align this automatic switch function with change of seasons and consider different time of getting dark. Besides, it will consider user's time zone set in the settings, in case it differs from the website's time zone. These functions will allow better optimization of automatic switch to the night mode of the panel.
❑We added the function of enabling and disabling categories. This function will allow you to temporarily disable a category which you do not need at the moment instead of deleting it. Deleting a category and further adding it back changes ID of the news; as a consequence, the link to previous news disappears. Enabling and disabling is an alternative way of removing a category from the website, by which, when the category is restored, it will resume its initial place and all the previous news will retain their link to this category and appear automatically as soon as the category is enabled.
❑You will be able to specify ID of related news for a post when adding or editing the post. At the same time you will be able to specify order of related news, in which you want them to be displayed. If you leave this field empty, the searched news will be displayed automatically. You will also be able to perform subsequent search of posts related to one certain news, without the need to clear cache of related posts for all the news.
❑Page navigation function was added for short news and for customised news display in a dedicated section separately from the main news section. For this reason we added support of the following tags in the main.tpl template: {navigation} displays page navigation section, [navigation] text [/navigation] displays text at the pages if there is news navigation, [not-navigation] text [/not-navigation] displays text at the pages if there is no news navigation. All these tags are optional; in case of their absence, navigation will be displayed at the news section as before, according to script settings. This way you will be able adjust customised website design in the templates in a more flexible way.
❑If you delete a user , it will be possible to appoint a new author for the user's posts. Or, as an option, you can leave the author unchanged.
❑We added the function to display user's last viewed posts. For this purpose the tag of user's news output with the parameter order="lastviewed", for example, {custom order="lastviewed"} is used. The posts are sorted in a way that the last viewed post is displayed first. For reverse sorting sort="asc" parameter is used. For example, with {custom order="lastviewed" sort="desc"} the posts will be sorted from the last viewed to the earlier ones, and with {custom order="lastviewed" sort="asc"} the posts will be sorted from the earlier viewed to the last. This feature is especially useful for websites posting catalogues, where the visitor can quickly access last viewed posts in a dedicated section. The history of viewed news is enabled and disabled in script settings on the admin panel. DataLife Engine stores 20 last viewed posts.
❑We added the function to display profile information of the user who is browsing the website at the moment in all files of the template. We introduced more than thirty new global tags containing information from user's profile, including information from the optional fields. By this you can display the data of an authorized user not only in login.tpl, but also in main.tpl and other templates, which opens new possibilities to flexible creating of templates. As the data is available for using in any template, please, be careful when using it in the templates subject to caching, for example, template of short news display. In such cases caching has to be disabled.
❑For search template (search.tpl) we added the function of arranging search parameters table at your discretion. For this purpose, apart from general {searchtable} tag, which displays all parameters for the whole search setting, we added 15 new tags, each of them displaying only one input or selection field without reference to visual form. This way you can create customised search design, build it into any HTML-framework, remove the fields and options you do not need, etc.
❑We added the function to enable or disable Yandex Zen use in script settings when exporting RSS feed. If you disable this feature, this option will not be displayed in post adding or editing.
❑We added the function to enable or disable Yandex Turbo use when exporting RSS feed. If you disable this feature, this option will not be displayed in post adding or editing.
❑We added the function of advanced search of the posts by key words from tag cloud, in post editing section on the admin panel. You will be able to choose posts for editing containing required key word from tag cloud.
❑We added the function to perform mass actions with news and enable or disable Yandex Zen for chosen posts in post editing section on the admin panel.
❑We added the function to perform mass actions with news and enable or disable Yandex Turbo for chosen posts in post editing section on the admin panel.
❑We added the function to specify whether Yandex Zen use is enabled for this category by default in category settings. If the feature is disabled, this option will be disabled by default in this category when adding news. Therefore, there is no need to disable this option every time for each news. You can enable this option anytime for any particular news, if necessary.
❑We added the function to specify whether Yandex Turbo use is enabled for this category by default in category settings. If the feature is disabled, this option will be disabled by default in this category when adding news. Therefore, there is no need to disable this option every time for each news. You can enable this option anytime for any particular news, if necessary.
❑We added support of new parameter sortbyuser="yes", which allows using customised sorting for this section of posts, for customised post displaying at the website using {custom ...}tag. If this parameter is enabled, website visitors will be able to set a convenient way of sorting news for this section at their discretion, the same way they do it for {content} tag
❑We added the function of automatic import of user's avatars, if user logs in with their Google or Yandex account.
❑In connection with new version of API 2.0 for logging in through mail.ru, and probable cessation of support of the older version of API, we added new API 2.0. support https://o2.mail.ru. Please, note that new API requires creating new application on the service. Therefore, if you use authorization through mail.ru on your website, you need to create new application https://help.mail.ru/developers/oauth/app, and then set application data in settings on the admin panel.
❑We added function of forming new meta tag og:description of Open Graph protocol in browsing static pages on the website.
❑We added support of new tags [not-image-x] text [/not-image-x], which display text included in them, in case picture under the number X is not in the news, for templates of short and full news (shortstory.tpl и fullstory.tpl) displaying. These tags will be useful when you need to display a customised substitute picture, if there is no suitable picture in text post.
❑We added support of banner tags {banner_X} for comments (comments.tpl template) from the module of advertising materials on the admin panel. You will be able to include advertising tags between comments in certain places.
❑We added support of banner tags {banner_X} in post text in displaying them on print version of the website.
❑We added new tag for post rating {ratingscore} in templates of displaying short and full news (shortstory.tpl и fullstory.tpl). This tag displays average rating figure containing fractional part amounting from one to five. For example, it may be 1.6 or 4.2 depending on evaluation. This tag allows to set customised design of rating stars filled partially, not only two or four fully filled stars.
❑We added new tag for comment rating {ratingscore} in templates of displaying comments (comments.tpl). This tag displays average rating figure containing fractional part amounting from one to five. For example, it may be 1.6 or 4.2 depending on evaluation. This tag allows to set customised design of rating stars filled partially, not only two or four fully filled stars.
❑We added use of recommended heading [b]Precedence:bulk; in letters for mass mailing on the admin panel. This feature is used to avoid directing your letters to spam folder.
❑We added support of automatic prompt search without consideration of letter case in filling tag cloud and optional fields having 'cross-reference' type. The fields themselves remember in database the case of letters as they were entered at fields filling in.
❑We added support of {title limit="X"} and {short-story limit="X"} tags for templates of displaying RSS feed.
❑We adapted prompts displaying on the admin panel, depending on screen size. Now prompts will be arranged in a way that they fit to screen correctly, regardless of screen size and resolution.
❑For optional field having 'cross-reference' type we added support of curly and square brackets and colon.
❑We reduced the time of rearrangement of posts on the admin panel, fixed the problems that could lead to incorrect symbol converting in optional fields.
❑We added case-independent control of usernames and e-mails which are not suitable for registration, written in Cyrillic or other languages; only English letters are applicable
❑We added support of user's avatar export from Vk.com after changes of API of this social network.
❑We adapted the code and added support of PHP 7.4.xx
❑We upgraded HTML Purifier library to the newest version.
❑We added function of the second parameter transfer for GzipOut feature; this parameter will output in debugging data all information on MySQL requests, namely time of request processing and whether it was directed to the database. For example, with GzipOut(true) general debugging information on script will be output; using GzipOut(true, true) it will be possible to output additional information on each MySQL request directed to the database. This new feature will be useful for module developers and performance enhancers for problem detection and diagnostics.
❑In user editing section on the admin panel and on the website we changed type of the date display in the field indicating the date until which a user had been in temporary group, . The output type is adapted to the type used by pop-up calendar in a way, that specified date and time is displayed on the calendar.
❑We fixed the issue of dynamic comment loading failure with Ajax in jQuery 3.xx script settings.
❑We fixed the issue of impossibility to delete a user when editing their profile immediately on the website.
❑We fixed the issue of impossibility to confirm changing of e-mail when both e-mail address is changed and two-factor authorization is enabled at the same time, if the previous e-mail is not available.
❑We fixed the issue of admin panel full screen mode failure in Chrome browser.
❑We fixed the issue where the citing of a selected text could work incorrectly in publications made with Froala rich text editor.
❑The issue of incorrect tags of [sort] ... [/sort] when viewing a full piece of news was fixed.
❑We fixed the issue where the tag {THEME} could be processed incorrectly while news resorting in the admin panel if it was placed in the news texts.
❑We fixed the issue of incorrect adding of IP address blocking in profile settings on the website, when asteriks were used instead of IP address mask.
List of changes of 13.2 version:
❑Notes have been added to the plugin system. You can add notes, reminders or instructions to each plugin in a relevant tab. You can also set whether you want to show these on the main page in the list of plugins or not. The notes themselves can either be in the HTML format or use BB tags.
❑It is now possible to set the sort order of plugins in the control panel.The sort order is done in a convenient way, by simply dragging the elements around on the Admin Panel page. The change in the sort order affects the plugin execution order, too.
❑In case of faults found in the plugin during its editing, a new tag page has been added to contain the list of such faults. This way you can easily see the faults and correct them while editing the plugin in question without leaving the page in the browser.
❑The “Headings, descriptions, meta tags” module has been expanded to offer a possibility to assign the robots meta tag to pages. Now, if needed, you can set separate indexing rules for each page or disable indexing.
❑It is now possible to change the script settings in the Admin Panel to set the minimum number of characters in a website search. Before the limit used to be fixed at 4 characters. Now administrators can set their own values making changes directly in the settings.
❑It is now possible to put in or take out each update in the RSS feed separately. To do so, when adding or editing the post in the Admin Panel, you pick a relevant option. Therefore you can be precise about which update you want to add to the RSS feed, and which not. This option is enabled for user groups that have a status which is no lower than that of the web editor-in-chief.
❑It is now possible to set it up for each publication separately whether it is permitted to use it in Yandex Turbo or not. To do so, a relevant option has been added to the Admin Panel so the choice can be made while adding or editing a publication. Also, to support the option, the rss.tpl template has got new default tags: {allow-turbo} shows “true” or “false” depending on whether the Turbo option is on or off, and [allow-turbo] text [/allow-turbo] that show the text inside if Yandex Turbo is on for the publication.
❑It is now possible to set it for each publication separately whether or not it should be used in Yandex Zen. You can control whether the option is on or off while adding or editing publications in the Admin Panel. To support the option, the rss.tpl template has got new default tags: [allow-dzen] text [/allow-dzen] that show the text in brackets if the Yandex Zen option is on for the publication.
❑As for images uploaded to go with publications, it is now possible to set a limit for the minimum size in the script settings. If an image is smaller than the pre-set minimum, it won’t be uploaded, and the user will be notified correspondingly. This way you can make sure that images added to publications comply with your requirements.
❑The additional fields of “Image” and “Image Gallery” type has got a new opportunity to specify the minimum sizes for uploaded images. If the size is smaller, images won’t be uploaded, and the user will be notified correspondingly. This way you can make sure that images added to publications comply with your requirements.
❑Images added to comments can now also be controlled in terms of their minimum size that is set in the user group settings. If the size is smaller, the image won’t be uploaded, and the user will be notified correspondingly.
❑The script settings in the Admin Panel have got a new possibility to choose which jQuery line shall be used on the website. You can either opt for line 2.xx or 3.xx. This way you can control whether you will be using the latest versions of libraries or libraries compatible with your JS plugins. If line jQuery 3.xx is used, it also goes with the latest version of the jQueryUI library.
❑The script settings in the Admin Panel have got a new possibility to set whether it is necessary to decline the dates of publications when they are posted via a user tag. If this option is on, and the publication date is introduced through the {date=date format} tag, the name of the month will be declined based on the data in the language files.
❑The breadcrumbs Microdata markup has been fully converted to the schema.org standard instead of data-vocabulary.org which is now outdated.
❑HTML support of the map and area tags has been added in text publications. These allow for the images markup by dividing them into sections with links.
❑For e-mails sent out via the Admin Panel in the Message List, the List-Unsubscribe control header has been added to make it easy and convenient for users to unsubscribe from postings directly via the mail service interface.
❑New global template tags have been added: {category-icon} displays the icon of the category viewed by the user, or news category if the full text is viewed; another added tag is {category-url} which displays the URL of the viewed category. Global template tags can be used in any template files, for example, in main.tpl. These template tags will be both useful for additional content formatting on the website pages and generating page Meta tags.
❑As for complaints reported by unregistered users, the reporting system on the website has acquired a possibility for doing so by asking them for their E-mail address so the web admin can follow up on to their complaints. Filling in E-mails is optional for visitors so the field may be left empty at their own discretion.
❑Clean URL name control has been added for publications in case the website uses type 3 clean URLs. If there has been a publication under the same URL name earlier this day, it is impossible to post another one using the same URL. The user will be offered to change the URL name for another one. This addresses the URL conflict for publications headed with the same name or URL made on the same day.
❑New global tags are supported: [ios] text [/ios] that display the text inside the tags if the user’s device operates on the iOS system by Apple; another support has been added for opposite tags: [not-ios] text [/not-ios] that display the text inside the tags if the website user’s device doesn’t operate on the iOS system. This sort of tag support doesn’t only make it possible to identify the user’s device type but also shows where it belongs by applying the relevant website formatting, for example, it can give a link to download a certain app from the Apple app store.
❑New global tags are supported: [android] text [/android] that display the text inside the tags if the user’s device operates on the Android system by Google; another support has been added for opposite tags: [not-android] text [/not-android] that display the text inside the tags if the website user’s device doesn’t operate on the Android system. This sort of tag support doesn’t only make it possible to identify the user’s device type but also shows where it belongs by applying the relevant website formatting, for example, it can give a link to download a certain app from the Google app store.
❑It is now possible to upload and edit images in the WEBP format for comments and pictures in user profiles, as well as in the image management section in the Admin Panel.
❑WEBP format is now supported for image display tags {image-x}. The same format is also supported for OpenGraph Meta tags in social networks.
❑Activities are now logged in the Admin Panel concerning activities regarding postings on the website in case the updates are published straightaway without authorization. Previously logs used to register added publications in the control panel only.
❑It is now possible to save publication parameters if it is edited by a user who is authorized to change only certain parameters. For example, excluding certain publications from a search or indexing can only be available for users that belong to groups that are no lower than editor-in-chief or admin, and if the post is edited by a journalist, those parameters are left as they were set by the website admin.
❑Postponed upload of images is now supported for static pages of the website.
❑Publication headings are now displayed whenever links to the previous or next news pieces are shown. The display template has been extended to support the following tags: {prev-title} which displays the name of the previous item, and {next-title} which displays the name of the next item.
❑The < vidео > and < аudio > HTML tags have been provided with support of all HTML attributes in accordance with the HTML5 specs.
❑Quick editing of website publications has been optimized. It is now automatically set whether automatic soft wrap is required depending of the editor, and when visual editors are used, the “automatic soft wrap” option is no longer displayed or used.
❑The script Admin Panel on the main page now displays information about faults in the performance of installed plugins. It means you can quickly see that a given plugin has signaled to have faults, say, after the script has been updated to the latest version, without the need to visit the plugin control section. The main page can also be used to review the faults straightaway.
❑When queries are viewed on the website, the corresponding pop-up window has changed the display order of the queries. Now the most relevant queries come first.
❑In case publications are added to the website via a user link with references to the pre-set categories, after the publication is posted on the website and if the user wants to add another one, the “Add more” link will take them back to the publication uploading page with the same pre-set categories.
❑To enhance the custom display of publications {custom xfields="..." ...}, the handling search parameter regarding publications has been improved through additional fields xfields=”…”; this parameter can now use single inverted commas for data search, as well as a number of other symbols that were previously unavailable in the search.
❑Full support of the 7.3.x PHP line has been added.
❑Full support of the 8.0.17 MySQL has been added.
❑Changes have been made to the operation of the publication counter as per categories. When postings were previously counted, the only setting that was taken into consideration was whether or not “the news shall be displayed in subcategories”, now personal settings specified for each category in the category control section are considered as well.
❑Changes have been made to the operation of tag [xfvalue_thumb_url_X] for additional fields of the “Image” type. In case a given field hasn’t been attributed with a thumbnail, since the original image is initially smaller, this tag will display a link to the original image. It therefore eliminates cases when this tag on the publication display page displays nothing if there are no thumbnails.
❑We have improved the system to sort categories and additional fields in the Admin Panel. All changes in the sorting are automatically saved immediately after the order has been altered, so there’s no need to save the changes by pressing a separate button.
❑We have improved the formation of the og:description Meta tag of the OpenGraph protocol when the full text of the news is viewed. The tags are formed more correctly with automatic deletion of function tags, for example, tags of ad banners, etc.
❑We have improved and optimized the automatic formation of the Meta tag that describes the Description page. Some of the function tags are now filtered and double spaces have been eliminated as well.
❑We have enhanced the performance and reduced the load on the server when the page display requests are handled for categories that don’t exist on the website.
❑We have updated the TinyMCE and Floara visual editors to their latest versions without changes to the editor line. The editors no longer have previous minor bugs, but the line has remained intact with the usual functionality and interface.
❑We have fixed the issue when the images weren’t shown in the print preview if the image loading was set to be postponed in the script settings.
❑We have fixed the issue with the appearance of doubled pages, for the tag cloud and search by additional fields, when the search entry uses letters of different cases.
❑We have fixed the issue with the incorrect deletion of selected images of the news item, in case a few images were selected for deletion, PHP 7.x is now also used on the server.
❑We have fixed the issue with the occasional failures in the quick image loading in the Froala visual editor when the quick editing function was used on the website.
❑We have fixed the issue with the incorrect navigation page count in the tag cloud control section.
❑We have fixed the issue with the unavailability of inverted commas in descriptions of loaded images in case they were loaded in the visual editors immediately after their uploading to the server.
❑We have fixed the issue with the faulty operation of color schemes in the TinyMCE editor.
❑We have fixed the issue with the occasional display of news protected by passwords without any password request.
List of changes of 13.1 version:
❑Domain transfer wizard is added. Now you can easily change you website domain. The wizard will automatically replace your domain in publications, comments, static pages, banners and user avatars. This wizard is launched from the control panel, in Engine Settings, next to the website address setting.
❑Now in the plugin system you can specify the executable PHP code which hooks to the plugin installation, update, enabling, disabling, and deletion events. It allows you to modify plugin behavior on specific actions.
❑Now in the plugin system you can specify string entries to start performing actions from in a file. For example, if there are several identical lines in the file and you need to perform specific action only starting from the second string entry, then you can specify this in the plugin.
❑Now in the plugin system you can specify that a certain plugin is required for correct work of another plugin. In plugin settings you can specify a name of another plugin that must be installed. In this case, this plugin will be executed after the execution of the main plugin. Thereby you can create add-ons not only for DLE itself, but also for plugins and create plugins for plugins.
❑In the plugin system line breaks are now performed correctly in the replaced code if it is at the very beginning of the code with which it should be replaced or added to.
❑Now you can use the {engine} tag for MySQL queries used in plugins, which indicates which MySQL engine DLE uses to create database tables. Values may be InnoDB or MyISAM.
❑Changes are made to the plugins installation and enabling system for cases when the plugin does not meet the requirements. For example, in cases when a plug-in requires a specific version of DLE, and the installed version of DLE does not match it, the plugin will still be installed but it will not be enabled. It allows a user to edit the plugin in the future, and make the necessary changes to it directly from Administration Panel. The same goes for the rest of plugin requirements. It will be possible to enable the plugin only if non-compatibility has been eliminated.
❑Standardization of the plugins execution order is added in the system. Plugins will be executed strictly according to the principle: the first added to the system is the first executed. Execution of plugins will be made regardless of whether the plugin has been edited in the Administration Panel or not. Also, if a plugin is dependent on another plugin, then the plugin on which it depends will be executed first.
❑Lazy image loading is added for publications. This feature can be enabled in the engine settings in the control panel. When this option is enabled, the images in the news will not be loaded by the browser on the page opening. They will be loaded as they are within browser’s viewport or nearby its borders. This feature allows you to improve the page loading speed and reduce the server load.
❑Now reCAPTCHA v3 is supported. With this type of captcha your users will no longer have to select any pictures and perform any additional actions on the site to verify themselves. The user is checked for being a bot or not in the background, unnoticed by your visitors. Before enabling this type of captcha, be sure to generate a new Google token key specifically for reCAPTCHA v3.
❑Now manual changes to .htaccess file located in the root of the site are kept in case of the engine auto-update. Contents of this file will not be completely replaced after the engine update. Only necessary changes will be made the in the standard functions. Thus, all manual changes made to it by the owner of the site will remain unchanged. The same is done for the cron file, which you configure to perform your actions on the cron.
❑Changes are made to the process of automatic engine update within the same major version. When patches with error corrections within the same version of the script are released, only installation of changes in the form of a patch will occur, updating only the changed files, not all the files as it was before.
❑Now a selected category can be automatically recognized in an article preview, and if a separate template is assigned to it, then a proper preview template will be loaded for this category. Thus, if different templates are assigned to different categories, all of them will be used in the preview.
❑Now you can use hints for links in Cross-Reference module in the control panel of the engine (title attribute). This feature allows you to improve SEO optimization, as well as improve the experience from your site for people with disabilities.
❑Now similar publications are automatically rebuilt when edited. When you edit an article, the engine automatically searches for similar news. Earlier in order to search for similar publications it was necessary to reset the cache of similar articles in the corresponding section of Administration Panel.
❑Now user bookmarks automatically synchronized in case of deletion of a publication from the site. If an article is removed from the site then it also is removed from bookmarks of all users and the user bookmarks counter is synchronized for these users.
❑Now magnet protocol is supported for links published using BB tags and in visual editors.
❑Now loading and processing images in WEBP format is supported. Images in this format can be directly uploaded using the DataLife Engine. The engine will create thumbnails and watermarks if necessary.
❑MySQL 8.x is supported.
❑PHP 7.3.x is supported.
❑Now you can specify several values separated by comma in [ifxfvalue tagname="tagvalue"] Text [/ifxfvalue] tag which shows the enclosed text if the tag value matches the specified value. For example, text within [ifxfvalue city="New York, Paris, London"] Text [/ifxfvalue] tag is shown only if an extra field named city contains one of specified values. It greatly simplifies the template layout for various cases.
❑Now there is a search for advertising materials management system in Administration Panel. You can search by name, description, and by the ad code
❑A more informative visualization of whether a banner is displayed or not has been added in the banner management section of Administration Panel. For example, if a banner has display limitations by time, views or clicks, and the limit has already been reached, then in the banner editing section it will also be shown that the banner is currently off.
❑Now you can search by news and static pages on mobile devices (smartphones, tablets) in the engine control panel.
❑Now you can choose a search area in advanced static pages search. You can search either by all fields, or separately by name, description, and text of a static page.
❑Static pages search algorithms have been significantly improved. Now the search is more accurate, and gives you better results according to the specified search criteria.
❑The performance of DataLife Engine has been significantly improved and database load has been reduced when using multi-categories on the site. Requests to the database were re-implemented in such a way that they no longer use regular expressions when accessing the database, thereby significantly improving the speed of the engine and reducing server load.
❑The performance of DataLife Engine has been significantly improved and database load has been reduced when using multi-categories on the site. Requests to the database were re-implemented in such a way that they no longer use regular expressions when accessing the database, thereby significantly improving the speed of the engine and reducing server load.
❑The performance of DataLife Engine has been significantly improved and database load has been reduced when showing publications found with help of extra fields that have "use as cross-references" property.
❑Now you can quickly reset search parameters to default values for news and static pages advanced search.
❑The limit on the number of characters for Description meta tag for static pages has been increased to 300 characters. This limit now corresponds to the limit set by the Google search engine to display this information in search results.
❑Changes have been made to forming mechanisms of the og:image meta tag used for posting data to social networks. Now, if an article has an annotation, then this tag will form a link to the full original image. Thereby, social networks containing restrictions on the minimum image size will receive the maximum possible original image quality.
❑Control of incorrect friendly URLs when viewing publications based on a directory with the symbol code specified in the publications is added and control of incorrect friendly URLs of a full article is improved.
❑Control of incorrect friendly URLs when viewing publications based on a directory with the symbol code specified in the publications is added and control of incorrect friendly URLs of a full article is improved.
❑Now you can use plus symbol as a value for extra fields of "Cross-references" type. For example, you can use values such as C++.
❑Now such characters as double quotes, plus, and others are supported for keywords intended for a tag cloud of publications. Almost all restrictions are removed on characters in the cloud, leaving only restrictions on the use of HTML code.
❑For the RSS feed template, now you can use HTML code split into several lines, used to generate turbo content for Yandex.
❑Processing of transparent PNG images is improved. Application of watermarks for these images is also improved.
❑Added support for [newscount=X] text [/newscount] and [not-newscount=X] text [/not-newscount] tags for custom output of publications using {custom ...} tag in cases where this output is used in article annotation templates.
❑Added support for [newscount=X] text [/newscount] and [not-newscount=X] text [/not-newscount] tags for custom output of publications using {custom ...} tag in cases where this output is used in article annotation templates.
❑TinyMCE and Froala visual editors are updated. A number of detected errors is fixed in these editors.
❑An issue is fixed with the incorrect work of control system for incorrect friendly URLs for article extra fields of cross-reference type if the values of these fields contained quotes.
❑An issue is fixed where articles sent to moderation could be displayed in bookmarks.
❑An issue is fixed with incorrectly displayed curly brackets in the comments when using the AJAX navigation for comments.
❑An issue is fixed where not all template tags of publication extra fields were correctly processed in the main.tpl template if a user visited a missing article.
❑An issue is fixed where {news-id} tags were incorrectly processed when displaying publications using {custom ...} tag if a user viewed a full article.
❑An issue with operation of [available ...] and [not-available ...] tags is fixed when a user is on a page of article by a symbol code, if the symbol code is not specified or is equal to zero "0".
❑An issue is fixed with the incorrect work of control system for incorrect friendly URLs in full articles if DLE was installed not in the site root directory.
❑An issue is fixed where articles planned for publishing in the future could be displayed when switching to following and previous articles, despite the fact that they set not to be displayed in the engine settings.
❑An issue is fixed where extra fields with gallery and image type could not be displayed when previewing an article if image descriptions were used in these fields.
List of changes of 13.0 version:
❑Automatic engine update within the same major version of the engine is added in the admin panel for cases where update contain patches related to vulnerabilities or other bugfixes. If there is an update within the same major engine version, for example, when fixes related to vulnerabilities are released, or other problems with the script are detected and solved, it will be possible to perform this update in the admin panel of the engine.
❑Automatic plugins update is added. You need to specify URL to check updates from. Plugin developer’s resource specified in this URL should give the array in JSON format, which contains information about the current plugin version, and download link for the current plugin version. For example, this URL should return the value {"version":"2.0","url":"https://dle-news.ru/test/test.zip"}. After that, site administrator will be able check for updates and to get info about new plugin versions and update it in the admin panel in one click.
❑Now in the plugin management system you can specify the number of replacements to be performed for each search in the file. For example, if you need to find and replace some code that occurs in this file several times, you can specify how many times it is necessary to replace this code. To replace all occurrences of this code, you can leave this parameter blank, thus all the code occurrences will be replaced.
❑Now in the plugin management system there is the option that allows to automatically remove extra files loaded within the plugin archive when the plugin is removed from the site. This option is added in plugin parameters. It allows you decide whether you need to clean up extra files from the server when you delete a plugin from the site.
❑For the plugin management system, the option was added which allows to use the {THEME} tag in the names of folders in the ZIP archives. When downloading the archive through the plugin system, this tag will be replaced with the name of the template being used. For example, by placing the file /templates/{THEME}/test.tpl in the archive, your template file will be placed in the template used on the site. Thus, when using complex plugins that contain examples of template files, they can be immediately loaded into the desired folder containing the user's template.
❑In the plugin management system the ability to use the control characters of the preg_replace function, such as \\1, is used in the "Find and replace" action of the replacement line, which removes the restrictions on finding and replacing some code in the DLE.
❑Now for extra fields of "Image" and "Image Gallery" type you can individually assign description for each image, which will be converted to the HTML alt attribute.
❑Now for extra fields of "Image Gallery" type you can change the sorting order of the uploaded images simply by drag and drop. After uploading images you can swap images as you want. Also uploaded images can be moved to other extra fields.
❑For articles and comments a new type of rating is added - "Like and Dislike». This type of rating allows to keep count of likes and dislikes separately. New tags have been added for articles and comments templates: {likes} and {dislikes} to display number of likes and dislikes correspondingly, and [rating-type-4] text [/rating-type-4] tag to display the text inside of it if this rating type is enabled.
❑Now in user profile settings of Administration panel you can set a list of trusted categories where a corresponding user is allowed to publish. This will allow a user to manage specific categories where other users will not have the permission to publish. Or vice versa - you can exclude a user from a specific news category where you do not want him to publish.
❑In user profile settings of Administration panel you can set a list of trusted categories where a corresponding user is allowed to publish without moderation. Such settings will allow for more flexible rights distribution without creating a bunch of user groups, or even groups for each particular user.
❑Now in the articles edit section in advanced article search of Administration panel you can choose where to search. You can search in all content or only in title, short description, full description or extra fields. Algorithms of search has also been significantly improved.
❑Now for advanced article search in article edit section of Administration panel you can search in several categories.
❑Now you can use "&" and "#" characters in tag cloud, which allows to use names of various brands in the cloud, e.g. "H&M".
❑Now in Administration panel you can allow Administrators to authorize with social networks. When this option is enabled, users who are in the Administrators group can authorize with their social network accounts.
❑Now in comment edit section of Administration panel you can search for comments by string. In this section you can search for comments by any keywords. It makes comments editing more convenient.
❑Now in cross-reference control section of Administration panel you can replace using "In static pages only" and "In static pages, articles and comments" for mass actions on links.
❑Now you can use styles of your template from preview.css file to preview banners in the ad management section in the Administration panel. Thus, you can see a more accurate appearance of your ads if they use classes from your template.
❑Now you can use [not-news] tags [/not-news] in template of short articles description (shortstory.tpl). It allows to show the enclosed text if there are no articles by the given criteria. Thus, you can use your own message instead of the standard one if there are no articles in a given section of the site. You can make unique messages for every section. Also, these tags can be used in custom article display templates with {custom ...} tag.
❑Now you can use new tags for password recovery e-mail message: {%losturl%} which displays only the URL to reset a password, and {%ipurl%} which displays only password reset URL to reset the IP block. It allows you to make specific designs of these links in the letter, e.g. as buttons. And also you can hide the link to reset the IP block if you do not use it on your site.
❑The system for removing categories in Administration panel has been improved. If the category to be removed contains subcategories that are also subjected to deletion, then all actions for articles that are related to the category will automatically be distributed to articles that also related to subcategories of this deleted category. And the same actions will be applied to these articles in subcategories.
❑Now in "Filter by: IP, username or e-mail" module you can add blocked addresses, logins, or e-mails as lists rather than one by one. It significantly speeds up the process of adding if you already have a list of users to block.
❑In "Filter by: IP, Login or E-Mail" module you can edit existing rules. You can select and edit any rule, without having to delete it and re-add it again.
❑In "Filter by: IP, Login or E-Mail" module you can select several rules or all of them simultaneously, and unblock these rules in one click.
❑Now "Filter by: IP, Login or E-Mail" module supports IPv6 addresses that you can specify to block access to the site. You also can block IPv6 subnets.
❑Now you can specify IPv6 addresses in the user profile for those who are allowed to authorize. You also can specify not only a separate address, but IPv6 subnet.
❑Now for the custom sorting of articles displayed by {sort} tag you can set sorting for each specific category.
❑Now you can use "p", "div" and other tags in links in articles. Thus DataLife Engine supports more features of HTML5 standard.
❑Now you can add new users in the DataLife Engine control panel when working from a smartphone.
❑Changes have been made to nested comments. When the maximum nesting level for comments responses is reached, then in case of adding another replies they are displayed on the given maximum nested level in the discussion thread. Earlier, when the maximum nesting level was reached it was impossible to answer the comment. Now it is possible to post any number of replies.
❑Now in extra fields that have "Cross-Reference" type you can use double quotes and ampersand characters.
❑If the HTML message format is used for the e-mail recovery letter template, then the links that are generated by {%lostlink%} tag in this template will be generated as a ready HTML code, not just text links.
❑Now in the engine settings there is an option to set articles sorting by the number of comments by default. The same thing was added for sorting criteria when viewing the catalog.
❑Now in category settings there is an option for articles sorting publications to sort by the number of comments by default.
❑Changes have been made to extra fields, if the field is not allowed to be added by certain user groups. If the value of the extra field was added by the user with the corresponding rights, and subsequently the article is edited by a user who does not have the permission to edit this field, then the value of this field is no longer cleared - it comes back to its previous state.
❑The limit on the number of Description meta tag characters for categories is increased up to 300 characters. The maximum length now corresponds to the maximum length set by Google search engine to display this information in search results.
❑Similar articles search has been improved. Similar articles search results are sorted in a more relevant manner.
❑Visitors’ IPv6 addresses support has been improved. In some specific cases, the full address could not be placed in the database. Now the length of the fields is reserved according to RFC 4291 specification.
❑Formation of the og:description meta tag of the Open Graph protocol has been improved for full articles. Formation is more correct when it is used as the main content in extra fields of articles .
❑The work of the DataLife Engine security system has been improved to check the data on subdomains more correctly for some hostings which have subdomain structure of sub-folders of the main domain.
❑Now tel: protocol is supported for links published on the site using BB tags.
❑TinyMCE and Froala visual editors are updated. A number of detected errors is fixed in these editors.
❑An issue is fixed where fields of "List" type were used in extra fields of the user profile where values with the symbol "|" were used.
❑An issue is fixed where some symbols in the field values could incorrectly change in the plugin control section if the action on the file in the menu changed.
❑An issue is fixed where you could not use [lееch] tags for internal pages. It was only possible for external sites.
❑An issue is fixed where the site could not be upgraded if encoding other than UTF-8 was used on the site and Administrator's login or password contained Cyrillic symbols.
❑An issue is fixed where the pop-up block about new personal messages did not appear if the user logged out and then logged in after some time.
❑An issue is fixed where comments editing did not work in the engine control panel if TinyMCE editor was enabled in the engine settings.
❑An issue is fixed where the period in days within which it was allowed to send comments to the article did not show if this period was set in Administration panel.
❑An issue is fixed where an extra field of "Download file" type was not displayed as a file download link but as a usual tag.
List of changes of 12.1 version:
❑Windows-1251 encoding is no longer supported.
❑Automatic DataLife Engine update system is added.
❑A new system for installing and managing plugins is added.
❑Now you can enable or disable the plugin system support in the engine settings of the Administration Panel. If you do not use this system, you can disable it in the engine settings to increase the performance of the engine and reduce the server load.
❑Now you can convert your database automatically from the Administration Panel for sites where utf8 encoding is used for database, not utf8mb4 four-byte encoding. These encodings are fully compatible, but conversion of your site to utf8mb4 will give full support for all the characters, e.g. Emoji, musical symbols and many others.
❑Now you can display links to the previous and next articles when viewing the full article.
❑The {news-id} tag has received global support in all templates.
❑Now in the user management section of Administration Panel you can search for users who are prohibited from posting articles or comments.
❑Users of the demo version now can automatically switch to full version after entering the license key. As you know, the source code of the demo version is closed from editing. Therefore, after submitting the license key you will be able to automatically replace demo version files with the open files of the full version in addition to removing restrictions from the database. This process is fully automated, and can be started in the Administration Panel in one click.
❑Now in advanced articles search of the control panel you can search for articles which have votings and passwords.
❑Search in the "Actions Llist in Administration Panel" is essentially improved. Now you can search not only by login or IP, but also by the name of action itself. For example, by entering "delete article" you will see the entire list related to articles deletion. It works for any action.
❑Now you can select categories in the "Optimization Wizard" module of the engine control panel from which you want to remove outdated articles. Thus, you can filter and specify categories where you do not need to delete old articles.
❑In "Optimization Wizard" module of the engine control panel you now can apply the following actions: clear all personal messages or clear read messages to leave only unread messages.
❑Now you can write personal messages using AJAX technology. When clicking on the link of writing a new personal message in the user information display card, or when viewing his/her profile, a new personal message form will occur in a pop-up window and will be sent using AJAX request without reloading the page. Thus, users of your site can quickly send personal messages.
❑Now when viewing the full article you can format og:description meta tag of the Open Graph protocol. This meta tag is designed to correctly send your articles to social networks.
❑Now you can immediately go to the article preview after saving it when adding or editing the article in the control panel.
❑In the BBCODES editor, when using the text processing, all the necessary non-breaking spaces are directly presented as UTF-8 symbols, not as HTML entities. This makes it much easier to read and edit text in the editor, and allows you to avoid inconvenient merged text in future.
❑When polls and votings are used, the automatic selection of the first choice is removed. Thus, before making a choice in the voting or poll, the user must actively choose one of presented answers, which helps to avoid accidental voting for the first answer.
❑RSS feed spoilers filtering is added. Now DLE automatically removes all unused functionality from RSS feed leaving only the content that was specified in the spoiler.
❑Now in RSS export you can use {full-stоry} tag in conjunction with other tags without affecting HTML formatting.
❑Now in a regular site search you can use automatic search on static pages. If no article was found in result of regular site search, an automatic search will also be performed on static pages. Thus, visitors do not need to use the advanced search and choose static pages there to find what they need. This feature will be especially useful for those sites that use many static pages and do not have articles.
❑Now you can use automatic search on static pages for quick search on the site. If no articles were found, the engine will automatically perform search on static pages and display links to them if they match the search.
❑Now you can display polls from articles when displaying articles using {custom ...} tag. To display polls, use the {poll} tag in the template, and in the short and full article templates.
❑Now you can use sites of any encoding as a source for RSS articles import and for RSS informers, regardless of your site’s encoding. DataLife Engine automatically detects the encoding of the data source and recodes the data into the needed encoding.
❑Symbols number limit of Description meta tag for articles is increased to 300 characters. The maximum length now corresponds to the maximum length of information displayed by google search engine in search results.
❑System of automatic external images size reduction is improved. This system works if it is enabled in the engine settings. A small delay before running the corresponding JS function is added for this, which allows you to set the image size correctly if you have slow Internet connection. Also the automatic detection of the actual image size is added (not their size in the page block). On small screens it allows to enlarge them when clicking on images.
❑The formation of canonical links and meta tags of social networks for static pages is improved. If the static page has been split into several pages, then each individual page will have its own canonical links not just leading to the first page.
❑Minor changes of DLE video player have been made to make video watching more convenient. The size of the player is significantly reduced, which speeds up its loading to the browser. And the automatic addition of the title attribute for HTML video tags is also removed.
❑Gzip compression rate of JS and CSS files, which DataLife Engine uses, is significantly improved. It is active if compression is enabled in the engine settings.
❑For the Cross-References module, address recognition of the pages which contain Cyrillic characters and other Unicode characters is improved. It allows to correctly verify that the page refers to itself, and to not replace keywords for these pages.
❑For the Redirects module, address recognition of the pages which contain Cyrillic characters and other Unicode characters is improved. It allows to correctly make redirects from the pages specified in this module.
❑Now you can add new categories to Administration Panel when using the engine control panel from a smartphone.
❑Support of current version of the vk.com API is updated to allow loging-in using this social network account. Also, now users who do not have an E-mail address can log-in using vk.com.
❑The system for isolating template tags from each other has been redesigned and improved so that they do not interfere with each other’s work and information output.
❑A number of security features have been revised to prevent unauthorized actions for enhancing the website’s security.
❑PHP v. 7.2.x is now fully supported.
❑The Cyrillic transliteration system has been improved. Transliteration will follow the correct rules, which improves the readability of the Russian text expressed in Latin symbols.
❑DataLife Engine server installation is optimized and simplified. You’ll need to enter and select the small amount of data when installing the engine on the server. DataLife Engine installation script will automatically detect the rest.
❑TinyMCE and Froala visual editors are updated. A number of detected errors is fixed in these editors.
❑An issue is fixed where user could not respond to a comment on the all comments page, if RECAPTCHA was enabled for a particular user group in Group Settings.
❑An issue with the DLE API is fixed where the API did not perform user authorization checks if his/her account was not yet transferred to the new password storage system.
❑An issue is fixed where extra fields data was saved incorrectly when changing the sorting of these fields.
❑An issue is fixed where the site administrator could incorrectly merge comments if threaded comments were enabled and the comments were sorted in descending order.
❑An issue is fixed where in case of quick article editing, files and images in extra fields could not be loaded.
❑An issue is fixed where the category menu did not take into account the engine settings, whether User-Friendly URL is enabled, and always generated links with User-Friendly URL.
❑An issue is fixed where the source code inserted with [code] [/cоde] tags or using the corresponding code snippets button in visual editors could be incorrectly converted from HTML entities to their ASCII versions.
❑An issue is fixed where the information with [xfvalue_X image="Nr"] tag could not be displayed in the full article template when displaying a single image of the extra field of "Image Gallery" type.
❑An issue is fixed where it was not possible to use smileys in comments or articles when using Floara visual editor on mobile devices.
❑An issue is fixed where it was not possible to use some Cyrillic letters in user registration on sites which use UTF-8 encoding.
List of changes of 12.0 version:
❑Categories are implemented for the advertising management module. Now in this module you can create categories and post your advertising materials in them. The categories are displayed as folder images at the very top, in front of the list of added advertising materials. You can also create unlimited number of subcategories. Thus, having a large number of advertising materials, you can place them in various categories and subcategories for an easier navigation.
❑Views counter for promotional materials is added to the engine control panel. The views counter counts only views of real users who visit the website using a browser. Bots scanning the website are not counted. The account of views is enabled directly for each banner, so you can count views only for some of them. Also you can specify whether you need to count all banner views, or only views from unique users.
❑Banners display time limit based on the number of views is added in Administration Panel. It allows you to automatically disable the banner display when the specified number of views is reached.
❑Views counter for promotional materials is added to the engine control panel. DataLife Engine automatically intercepts HTML tags published using <а href="..."> tags and automatically counts clicks on them. Any special registration of these links is not required, they can lead to any needed addresses. Also, you can specify whether to count all clicks on the link, or only clicks from unique users.
❑Banners display time limit based on the number of clicks is added in Administration Panel. It allows you to automatically disable the banner display when the specified number of clicks is reached.
❑Views and clicks counters of each banner can be reset in the Administration Panel.
❑Canonical references can now be used in code of all website pages, including sections navigation, full article page, etc. This feature allows you to increase website’s SEO optimization, and also to avoid duplicate pages if incorrect links to your website are published somewhere on the Internet, or if you need to disable the control of incorrect user-friendly URLs for some reason.
❑In category settings of the control panel you can set for each category whether it is allowed to publish articles from this category on the homepage of the website by default. If you enable it, the corresponding box will be checked when you add or edit an article. If the category is not allowed to be published on the homepage, then the box will be unchecked when you add or edit the article.
❑In category settings of the control panel you can set for each category whether it is allowed to publish comments for articles from this category by default. If you enable it, the corresponding box will be checked when you add or edit an article. If the comments are not allowed for the category, then the box will be unchecked when you add or edit the article.
❑In category settings of the control panel you can set for each category whether it is allowed to rate articles from this category by default. If you enable it, the corresponding box will be checked when you add or edit an article. If the rating is not allowed for the category, then the box will be unchecked when you add or edit the article.
❑Automatic website protection from embedding into iframes on other websites is implemented in security settings section of the control panel. If you enable it, your website will be automatically not displayed if it is embedded into the iframe of another website. This way you can protect your website from such attacks as clickjacking.
❑The capabilities of the Meta Tags module have been extended. This module has been renamed into "Titles, descriptions, meta tags". Now in this module you can set not only meta tags for pages, but also a separate title and description for the page, which can then be displayed anywhere in your template. New global tags for templates have been added for this: {page-title} – displays page title, {page-description} - displays page description. You can use BB and HTML tags in page description. Thus, using this module, you can, for example, create and display titles and descriptions for the tag cloud for each separate tag.
❑New global template tags [page-title] text [/page-title] are added, which output the enclosed text if page title was specified in "Headers, descriptions, meta tags" for a viewed page. And [not-page-title] text [/not-page-title] tags with the opposite effect were added. The enclosed text is displayed if the title of the viewed page was not specified. Also, similar tags were added for description: [page-description] text [/page-description], which output the enclosed text if page description was specified in "Headers, descriptions, meta tags" for a viewed page. And [not-page-title] text [/not-page-title] tags with the opposite effect were added. The enclosed text is displayed if the description of the viewed page was not specified.
❑[not-active] text [/not-active] tags are added for the category menu template (categorymenu.tpl). The enclosed text is displayed if the viewed category or article does not belong to a menu category. This tag can only be located inside the [item] [/item] tags and is used, for example, to output some information (e.g. links) only for non-active menu categories.
❑Publications display capabilities based on the values of extra fields in articles are expanded. Link http://your site/xfsearch/field name/field value/, as before, displays articles containing the specified value in a specified field if "Use as cross-reference" box is checked. Link http://your site/xfsearch/field value/ displays articles containing the specified value in all extra fields. Link http://your site/xfsearch/field name/ displays articles where the specified field is filled out.
❑To output pages with no content, now you can enable a new option in engine settings to assign a separate page with the name 404.html in the root directory of your site. If this option is enabled, instead of the standard system message "Unfortunately, this page is not available, probably its address have been changed or the page is deleted.", you can display a special properly designed page. This feature is useful for webmasters who want to make a separate design of 404 pages of their websites.
❑Now in the engine settings you can assign an HTTP header where to obtain the IP addresses of users from. This feature will be useful for websites that use different external proxy servers, and do not have the ability to properly reconfigure the server for them to get the correct real IP addresses of visitors. For example, it is useful when using services like cloudflare to protect against DDOS attacks, having a normal hosting plan without access to server settings. Now you can set the path to get IP addresses of visitors in the engine settings of Administration Panel.
❑When you remove a category in the engine control panel you now can choose how to deal with articles located in this category. You can: "Remove this category from articles", "Replace the category with another category or categories", and "Remove all articles in this category". If you delete or replace a category of the article, then only the category itself will be removed or replaced. For example, if your article is in the categories "World", "News", "Popular" and you remove "In the world" category, then for articles in this category only "World" category itself will be removed or replaced, all other categories of these articles will remain as they are.
❑A new type of extra fields has been added for articles: "Pure HTML and JS". DataLife Engine will not interfere in text written in this field, will not filter HTML-code in it and allows pure JаvaScript code. This field is useful when you need to use some code in articles that you do not need to check – for example, some media player. Warning! Considering the fact that the engine will not filter text in this field, it is necessary to establish restrictions – please specify user groups which are allowed to use it. Do not allow it to be used by all users, otherwise it can cause security risks.
❑For article extra fields that have the option "Use as cross-references" checked you can specify the delimiter for links. You can specify both individual characters and HTML code as a delimiter. Previously, a comma was used as a delimiter, now you can specify custom delimiter for each field, which allows you to create unique appearance for each field in your template.
❑Yandex Turbo technology is now supported for normal RSS feeds without enabling RSS feed such as "Yandex news" in RSS feed type settings. For this, the full article display using {full-story} tag for any type of RSS feed is added. Also the standard template /templates/rss.xml is updated, which demonstrates how the template with the full support of "Yandex Turbo" should be like. The customization of RSS template for "Yandex Zen" technology is also supported in the same way.
❑Now you can respond to comments when viewing latest comments on the website if nested comments are enabled in the engine settings. It allows you to quickly respond to incoming comments without opening every article.
❑Browser page load speed is accelerated and loading is improved because some of the heavy scripts were transferred to a deferred load which is independent of the page load. These scripts are simultaneously loaded into the browser along with the rendering of the page and are launched only after the page is ready in the browser. This visually increases page load speed.
❑Now unregistered users of the website can send complaints to the Administration about articles and comments. Only registered users could do this before.
❑Now you can use shema.org markup to display rating of "Evaluation" type. This markup allows you to display the article's rating both in full articles and in Google search results.
❑Now orientation of uploaded photos is defined automatically based on metadata contained in the graphics files. In case the original photo was inverted, then the engine will automatically correct its position when it is uploaded. This eliminates the need to manually edit images if the camera was rotated during photographing.
❑Now there is an automatic notification of the website administration about the new article which is expecting moderation (if this is enabled in the engine settings) if the article was added from the engine control panel. Previously notification was sent only if the article was added directly from the website.
❑If the user is editing the previously published article in the control panel but the user group he is in is prohibited from publishing without moderation or is allowed to publish not in all categories, then the corresponding e-mail notification will also be sent to the website administration saying that the article is waiting for moderation.
❑Work of Breadcrumbs module is changed. If articles are viewed from a certain category, then in this category a references to it will be displayed as plain text, not links. The links will be shown only for categories that are higher in hierarchy. Also references will be displayed as links if user went further through navigation through the pages in this category. This feature allows you to avoid circular references.
❑Two new replacement areas for links have been added for Cross-Reference Module in the control panel. You can specify replacement only in static pages, and set a replacement in static pages, articles and comments.
❑For "Search and Replacement" module in the control panel a mass replacement of text is now possibile in polls for publications and in polls on the website.
❑Now you can remove all articles which are made by a particular user and waiting for moderation. To do this, in the user management section click on the number of his articles and select the corresponding menu item.
❑Now you can remove all comments which are made by a particular user and waiting for moderation. To do this, in the user management section click on the number of his comments and select the corresponding menu item.
❑Formatted output of different counters (for views, publications, comments) is added in the Administration Panel of the engine. The output of these counters is now formatted with space-separated hundreds, thousands, millions, etc. to give a better visual representation and perception of these numbers.
❑New [catlist=id1,id2....] text [/catlist] tags are supported for comments display and add comments templates (addcomments.tpl and comments.tpl) which display enclosed text if the article is of the specified categories, and also the tags: [not-catlist=id1,id2....] text [/not-catlist] - which display enclosed text if the article is NOT of the specified categories. You can specify a different design of the comments display and the comments adding for articles of different categories.
❑Now word declensions are supported for display tag or votes number of article rating. For example, you can use {vote-num} [declination={vote-num}]review||s[/declination]. Previously, this was not available for this tag since it contains HTML code, not just a number.
❑If in engine settings HTTPS protocol is set to be used on the whole website, then the browser cookies will also be sent to the server only via the HTTPS protocol and will be automatically blocked if HTTP protocol is used.
❑Added control of incorrect User-Friendly URLs for static pages the article text of which is divided into several pages. If an invalid page number is specified, an automatic 301 redirect will be performed to the initial address of this page.
❑For RSS import of articles, import of images from the enclosure tag containing the image for the article is supported. If a short description in the RSS stream is just text, and the image is given in it as a separate tag, then the image will be added to the very beginning of the short article during the import.
❑Redirect is supported for full articles when using RSS import of articles. If the link from the RSS feed is a redirect to the full text of the article on the source site, then DataLife Engine will automatically follow this redirect and will take the content from the source. It makes import of full text better than before.
❑Changes have been made to work of tags [comments] [/comments] and [not-comments] [/not-comments]. If comments are prohibited for a particular article, these tags will also hide their content.
❑If it is allowed to leave comments but a single user or user group was not allowed to post comments according to settings, then the corresponding notification will be displayed not at the end of all comments, but in a specific place of the add comment form with the tag {addcomments} defined in template by you, thus allowing you to determine the location of this message.
❑User e-mail addresses is automatically received now when authorizing using Odnoklassniki social network if the application received the appropriate rights from Odnoklassniki. By default Odnoklassniki do not give rights to receive e-mail addresses, and to obtain the access you need to contact this social network to get the permission to receive e-mail addresses. If the permission is received, DLE will also automatically import the e-mail address.
❑The system for calculating image aspect ratios is improved when creating small copies. It allows to get a more correct small copy of a better quality.
❑The system of articles search with a simple search type enabled in the engine settings. The new algorithm allows you to find articles more accurately and correctly.
❑Duplicate pages control is improved when viewing the latest comments.
❑Processing is optimized for articles’ extra fields when displaying their short descriptions, as well as when popular articles output module is enabled.
❑TinyMCE and Froala visual editors are updated. A number of errors is fixed in these editors.
❑Support for inserting hidden text tags using the appropriate button in the editor is added for TinyMCE editor.
❑When using the Floara editor for comments, the quick image upload and paste into a comment is added. You can either click on the picture insert icon and select the file to be uploaded, or simply drag the picture file from your computer to the editor field with the mouse. After that the image will be automatically uploaded and inserted at the cursor position in the field where you released the mouse.
❑Some minor changes have been made in the layout of the script control panel to eliminate some errors in layout and improve the interaction with the control panel.
❑Mailing library, as well as a library for determining mobile devices are updated.
❑An issue is fixed where the [comments] and [not-comments] tags were not processed in the article preview.
❑An issue is fixed where meta tags for video and audio from social networks were not formed correctly when video was published in extra fields and consisted of playlists and descriptions of video and audio files.
❑An issue is fixed where in certain circumstances and with certain server settings the article preview might not work when adding articles from the site.
❑An issue is fixed where dynamic comments loading did not work if it is enabled in the engine settings and the {jsfiles} tag is located at the very bottom of the website.
❑An issue is fixed where the latest comments display did not work if some categories were not allowed for a certain user group.
List of changes of 11.3 version:
❑Control Panel has been completely redesigned. We made it modern, readable and contrasting. Besides visual changes the new design also has a number of functional features. The new control panel has ten color schemes to choose from, not just one, and a special night template designed in dark colors for comfortable work in the dark. You can adjust the width of the sections side bar and width of the whole control panel. You also can enable a full-screen mode when working on devices with small screen sizes, hiding the browser bar and tabs to increase the working space of the panel. Each user of the Administration Panel can configure its custom look, its parameters and the color scheme. A special dual system for settings storage is used to save parameters of the panel. The settings are saved both on the server and locally in a browser providing unique features when using the control panel settings. Server-based saving of settings allows to avoid the "flickering" effect when applying the user's custom design, and also to automatically apply selected settings when using another browser. Whereas storing the settings locally allows you to restore the selected settings after a parameters reset on the server, for example, in case of engine re-installation or after its global update. We hope that you will enjoy the new control panel.
❑A short preview of the latest personal messages has been added to the control panel . Thus, the user can quickly open the message directly from the control panel.
❑This feature allows you to choose the action right after the article is published. You can choose between: "Add another article," "Edit article," "Go to articles list." It allows you to go to the most frequently used actions in one click.
❑This feature allows you to choose the action during the editing right after the article is saved. You can choose between: "Back to article edit" and "Go to articles list." Thus, users who frequently save text of the article during editing can quickly go on edit after saving.
❑Now you can enable a function in Static Pages section of Control Panel which allows you save the location of a user on a website before editing or adding the page. It allows to return user back to the previous location. This feature is useful when there is a large number of pages or setting any search parameters. After editing the user will not have to search or go back to the needed page manually.
❑This feature allows you to choose the action right after you saved a page. You can choose between: "Add another page", "Edit page", "Go to list of pages". It allows you to go to the most frequently used actions in one click.
❑This feature allows you to choose the action right after you saved a page. You can choose between: "Add another page", "Edit page", "Go to list of pages". It allows you to go to the most frequently used actions in one click.
❑A new feature of highlighting of articles, comments, static pages, etc. In Administration Panel is added to perform mass actions on them. It allows to easily distinguish chosen elements.
❑User profiles edit has been completely redesigned in Administration Panel. Now you can edit all the profile parameters which previously were available only through profile edit on the website.
❑A new Meta Tags module is added. This module allows you to reassign title, description, keywords meta tags for certain pages of the site in the Administration Panel. DLE engine automatically generates meta tags for all pages of the site, however you can reassign meta tags for any pages. For example, you can assign specific values for meta tags for the feedback page, rather than use general values from the engine settings. Now, with this module, you can do it in Administration Panel of your website. In this module you specify the URL of the page for which you want to reassign the meta tags and specify new values for these tags. After that, the specified values will be applied to this page. You can reassign all the tags together and separately. For example, if you leave the keywords field empty, the default values for that field and for that page will be applied. You can specify the address of the page for which you want to change meta tags, and also you can specify a URL group using the '*' character which stands for search by any set of characters. E.g., if you specify /page/*/, then specified meta tags will be used for pages /page/1/, /page/2/, /page/any text/, etc.
❑Now you can export users from the website. If you use third-party services or programs for organizing mailings for users, then with using the export you can quickly generate the necessary data. Users export is done in Administration Panel in User Edit section. You can export both all users and users selected by criteria. You can export the list either in CSV or Exel format.
❑You can transfer articles to other categories at the certain time. To do this you need to choose "Move to another category" action in "Expiration before" option when adding or editing an article, and assign one or more categories where you want to move articles to when the given time is reached.
❑You can transfer articles to other categories at the certain time. To do this you need to choose "Move to another category" action in "Expiration before" option when adding or editing an article, and assign one or more categories where you want to move articles to when the given time is reached.
❑Now you assign a password or a list of passwords for each article to view it. If a password is set for an article, then it will be asked to be entered to get an access to a full version of the article and the article will be shown only if the correct password is entered. The entered password will remain in effect until the user closes the browser, and the password will not be requested again within the same session on the site.
❑You can exclude certain static pages from the site search results. When adding or editing a page in Administration Panel, you can check "Exclude from search results" option for each static page separately.
❑Now you assign a password or a list of passwords for each static page to view it. If a password is set for a static page, then password will be asked to open the page and it will be opened only if the correct password is entered. The entered password will remain in effect until the user closes the browser, and the password will not be requested again within the same session on the site.
❑Autosuggestion for extra fields which have the type of "cross-references" when adding and editing publications is added. Words list for autosuggestion is obtained from the database. It makes it easier to fill these fields in, and also reduces the probability of an error in words.
❑You can use masks to specify a template for redirects in Redirects module. When specifying URL to perform redirect from, you can specify the '*' character which means that any set of symbols may be instead of '*'. E.g., you can specify /page/*/ to set redirect from pages like /page/1/, /page/2/, /page/any text/, etc.
❑Now you can quickly switch to editing a group of a specific user.
❑For static page templates (static.tpl and other assigned pages), the new tag [edit] text [/edit] is added, which displays the enclosed text as a link to edit the static page for user groups who are allowed to edit static pages. This allows to quickly move to editing the needed page, when there is a large number of static pages.
❑A new parameter "id_as_list" is added for custom articles tag {custom...} that works in conjunction with the "id" parameter, and sorts the publications as they appear in the list. For example, the tag {custom id = "3,4,1,2" order = "id_as_list"} will display articles first with ID 3, then 4, then 1, and 2. This feature is useful when you want to display the required articles in a strictly defined order.
❑A new parameter "id_as_list" is added for custom comments tag {customcomments...} that works in conjunction with the "id" parameter, and sorts the comments as they appear in the list. For example, the tag {customcomments id = "3,4,1,2" order = "id_as_list"} will display comments with ID 3, then 4, then 1, and then 2. This feature is useful when you want to display the required comments in a strictly defined order.
❑You can allow to attach video in comments using the tags [vidеo=...] in user group settings. This option is used to allow or deny certain user groups to attach video in comments.
❑You can allow to attach media widgets in comments using the tags [mеdia =...] in user group settings. This option is used to allow or deny certain user groups to attach media widgets in comments.
❑Changes have been made to quick editing of articles. Now in quick editing mode only those fields are shown that were previously filled in during article adding or full editing mode. This applies to both the article annotation and full article fields. If the article annotation and full article fields have not been filled in, they will not be displayed in quick edit mode. This feature is useful for those who use only extra fields in articles. They will not see unnecessary fields.
❑You can remove such fields as "article annotation" and "full article" from the article addition template, while retaining all other functionality of editors. This feature will be useful for those who use just extra fields to add articles.
❑A new global tag for the {category-id} templates is added which allows to display the ID of the category viewed by the visitor. This tag will be useful when organizing the menu on the site and when you need to quickly reassign any CSS classes or the names of template files, when you edit articles display templates.
❑A new global tag {category-title} is added for templates , which allows to display the name of the category viewed by the visitor. This tag will be useful when you need to display the name of the category you are viewing.
❑You can specify a full description for categories. The description is created in the Administration Panel when adding or editing categories in the corresponding section. In the description of the category you can use both BBCODES tags and HTML tags. A new global template tag {category-description} is used to display the description on the site when the user views the category. It is also available when displaying full descriptions.
❑You can use a new "only" value for the "subcat" parameter of the output tag {catmenu ...} of the category menu, which allows to display only subcategories of the specified category. For example, if you use the {catmenu id = "1" subcat = "only"} tag, only the subcategories of the category with ID "1" will be displayed. This feature is useful to display only subcategories of a certain category. For example, you can automatically display a list of subcategories from the viewed category using the simple expression [available = cat] {catmenu id = "{category-id}" subcat = "only"} [/avalilable] .
❑Now you can exclude the selected category from search results in the Category Settings of Control Panel. Thus, you can set visibility of each category in search results. If the category is excluded from the search results, then articles from this category will not be displayed there when you search for articles.
❑Now you can display the uploaded images separately for extra fields of "Image Gallery" type. For this the tag [xfvalue_X image="Nr"] is used in templates, where "X" is the name of the extra field, and "Nr" is the number of image from the gallery. For example, if you apply [xfvalue_test image="2"], then image number two will be displayed and loaded into an additional field named "test". Thus, you can use one field, and at the same time display a preview from the gallery in one picture in article annotation, and full gallery when viewing the full article.
❑Now you can safely use {titlе} tag in HTML attributes when displaying articles. For example, you can use alt="{titlе}" and the text will preserve the validity of the document if the header contains quotation marks.
❑Support for attaching videos and posts from Facebook has been added for [mediа=...] tag.
❑Gzip compression for CSS files used by the engine is added, which allows to significantly reduce the size of CSS files, and therefore to speed up the loading of pages. Compression can be enabled together with the compression of JS files in the engine settings. When you enable compression, only DLE engine’s own CSS files are compressed.
❑Now you can enable automatic reset of the browser cache for CSS and JS files used by the engine after its update. This feature allows the browser to use the newest files after the engine update, not use the old ones from the browser cache.
❑Tag {THEME} is now supported in promotional materials preview in the engine control panel.
❑A visual highlight is added for the number of characters entered into the field, and the number of allowed symbols left when adding any data in Administration Panel. This feature allows to visually see the maximum amount of symbols available for the field.
❑If the protocol of your site is not specified in the engine settings, DLE will use a secure SSL connection and will generate links to HTTPS protocol starting from this engine version.
❑Preventive measures are added to protect the site from "endless" redirects if only HTTPS protocol is enabled in the engine settings and the server is not configured properly and does not transmit information about the used protocol.
❑Preventive measures are added for the word filter section to protect against accidental deletion of words from the word filter in Administration Panel. Now this action requires confirmation.
❑403 HTTP code (access is denied) is sent to the browser for personal article bookmarks pages if an unregistered user goes to the bookmark address. Thus the page’s data will not be indexed by the search engines. Search engines are not indexing a page with just one access error.
❑The database load has been significantly reduced when displaying the latest comments on websites with a large number of comments.
❑The display of the tag cloud block is optimized for databases with a large number of articles on the site. The database query is improved and speeded-up.
❑Support for curly braces "{" and "}" in the "Word Filter" module is added and now you can use words containing these symbols in the filter.
❑Articles from the site map are automatically hidden from search engines if access to the article is denied for guests in "Access" tab of the article.
❑Froala and TinyMCE editors have been updated. Previously found issues are fixed in both of them.
❑HTML code parser for published articles is updated.
❑An issue with the incorrect CRON notification of search engines about the site map updates is fixed when the site name was specified without a protocol in the engine settings.
❑An issue is fixed where visual editors could not be displayed on the article publication page if there were "custom" tags on the page.
❑An issue is fixed where the visual editor could not load during quick editing if articles display was done only by {custom …} tag, without using the main {content} tag.
❑An issue is fixed where the merged text was sent without line breaks in e-mail notifications about new comments or personal messages.
❑An issue is fixed where line breaks were lost in empty lines when using the TinyMCE editor for articles.
❑An issue is fixed where some template tags for static pages were displayed incorrectly when displaying static pages in search results.
❑All previously declared and found small errors are fixed.
List of changes of 11.2 version:
❑New "Redirect" module is added for Administration Panel of the engine. In this module you can specify URLs to create redirects to another pages. This module will be really useful, when you delete or move something to another location. For example, you deleted a certain category and replaced it with another one. In this case you can create a redirect from the previous category to a new one by specifying an old and a new URL in this module. When visiting an old address 301 redirect will be performed, which redirects users to a needed page automatically and allows search engines to link the needed URLs. Also, this module may be used if some of your links were incorrectly indexed by search engines.
❑Caching system of Memcache was completely rebuilded. The concept of data prefixes was introduced for this type of caching. If you choose this type of caching and change some information in a database , cache is cleared for the required elements only but not completely, as it was before. This type of caching greatly reduces the server load.
❑Now in engine settings you can specify the number of pages to be cached for article annotations. Earlier the script could cache only the first 10 pages of navigation on the website. Now you can specify any number of pages that you want to cache.
❑Now you can set only HTTPS protocol to be used on your website. When this option is enabled, all users who visit your website pages using HTTPS protocol will be redirected to the secure SSL connection. Thereby, there is no longer need to edit .htaccess files and nginx settings to make automatic redirections.
❑Now you can enable BB tags in engine settings to be used for images in WYSIWYG editors. If this mode is enabled, images will be inserted as BB tags. It will be useful for those who use visual editing for articles and want to optimize the space taken by images in the edit field. If you turn this setting off, images will be displayed as pictures.
❑Now you can attach files to feedback letters. For this, in User Group settings you can specify user groups which are allowed to attach files to the letters. You also can set the maximum number of attached files and their maximum total size.
❑New [attachments] text [/attachments] tags are added for a feedback template (feedback.tpl). Text in these tags is displayed if attachment of files for feedback letters is allowed for a certain user group.
❑Now you can use several feedback forms on the website. A special URL is used in the browser for this. http://yourwebsitename.com/index.php?do=feedback address is used to add a standard feedback form. In order to add another feedback form, you can use http://yourwebsitename.com/index.php?do=feedback&template=X1&mailtemplate=X2 address, where X1 is a name of a feedback form, and X2 is a name of a letter template which is sent using this form. If X1 template is specified, then you should have feedback_X1.tpl file on the server in the template folder, and if X2 is specified, then you should have email_X2.tpl file on the server in the template folder. For example, if you specify http://yourwebsitename.com/index.php?do=feedback&template=test&mailtemplate=test then feedback_test.tpl feedback file and email_test.tpl email file must be in the template folder. These files support all the same tags as the standard feedback form and standard email template in the Administration Panel do. Concerning that feedback forms support several types of extra fields, you can make several feedback forms on your website.
❑All images published using BBCODES tags automatically are receive adaptive properties so that they do not go beyond the boundaries of the website elements where they are published. It makes template markup process easier for beginners.
❑Search by username, IP, and date is added for "List of Actions in Administration Panel" module. You should simply enter the needed data in a search bar and the engine will search for the corresponding data. It allows to easily find required information in logs.
❑H1...h5 heading tags are now ignored in "Cross-section" module. Text will not be replaced with cross-sections in these tags.
❑Search and replacement for promotional materials is added in the Control Panel of the engine for "Search and Replace" module .
❑Now you can specify the article from which the rebuilding will be started for "Articles Rebuilding" module. For example, if the articles rebuilding process is broken, or the window is accidently closed, you can continue rebuilding from the needed article without having to start everything from the beginning.
❑Comments rebuilding is added for "Articles Rebuilding" module. In case of changes in the parser or website settings you can run an automatic rebuilding for all comments on the website so that the changes took effect in previously published comments.
❑In articles rebuilding section in the Control Panel of the engine the speed of the articles rebuilding is increased. Also, the errors processing system is improved.
❑Now comments edit modules support comments editing instead of a simple text field. You can enable this in the Control Panel. It provides a more convenient way to edit comments.
❑Now you can select all comments with a single click to perform mass actions faster. You can enable it for comment edit modules in the Control Panel.
❑Unregistered users are filtered by IP, username, and email address when they add comments. If the username or email address is in the filter list then the user is not allowed to leave comments.
❑Now you can specify categories in a browser bar to be selected by default. This feature is added for articles publishing module. For this the following URL is used: http://yourwebsitename.com/index.php?do=addnews&category=X, where "X" stands for IDs of needed categories, separated by comma. For example, if you use http//:yourwebsitename.comindex.php?do=addnews&category=3,4,5, then categories with IDs 1, 2, 3 will be chosen in the article add form. It is useful if extra fields for articles of several categories are used on a website, and if you want to give several forms for posting articles in several categories to users who add articles .
❑Now you can use micro-markup directly in article text. (such attributes as: itemprop, itemtype, itemscope)
❑Automatic long words splitting is added for personal messages, not just for comments.
❑"enclosure" tag for RSS feed is now supported for RSS informers. It is used to define images. If there is no images in an article text of RSS feed, but they are defined by enclosure tag, then an image from this tag is assigned for {image-1} tag. E.g. it can be useful for weather RSS informers.
❑Now you can specify which user groups are allowed to see hidden text ([hidе] text [/hidе]). In the tag parameters you can specify which groups are allowed to view the contents. For example, you can write [hidе=3] text [/hidе] and in this case only reporters are allowed to view the contents of the tag. Groups can also be enumerated by commas, e.g. [hidе=2,3,4] text[/hidе]. If the group parameter is not specified, then the group settings from the Control Panel are applied which define whether user is allowed to view the text or not. Website Administrators can always see the hidden text, regardless of the parameters specified in the tag.
❑Tag [media=...] in News is completely re-made. Now this tag is intended not only for embedding video from youtube service, but also for embedding various photos, audio, video, documents and widgets from a large number of websites and services. For this, the tag has been completely shifted to use oembed open protocol, which helps to get the embedding code from the services. 15 services are supported at the moment: youtube, instagram, twitter, facebook, flickr, vimeo, docs.com, vine, gettyimages, codepen.io, dailymotion, mixcloud, soundcloud, coub, ifixit. New services that support oembed can be easily added if necessary.
❑Now you can use a new futureannounce="yes" parameter for custom articles display using {custom ...} tag. This parameter works in conjunction with the days="X" parameter, and specifies that articles from future dates should be taken. For example, {custom futureannounce="yes" days="1"} tag means that it is necessary to display articles whose publication date is set to tomorrow (+1 days). {custom futureannounce="yes" days="2"} tag displays articles whose publication date is set for tomorrow and the day after tomorrow, etc. This parameter may be useful for those who want to show upcoming announcements on a website.
❑If "Block files uploading from other servers" is enabled and the link to your file is posted on another website then users who click this link will be transferred directly to a needed article or static page where the file is located, not to a homepage of the website.
❑New {id} tag which shows category's ID is added for category menu template (categorymenu.tpl). It can be useful if you need to visually emphasize a certain category.
❑In language files of control panel you can select a date format. It can be useful if your website is intended for a culture where date format differs from Russian format.
❑Preventive protection measures are added in case of accidental deletion of images uploaded to an article by clicking "Delete Chosen" button. You'll have to additionally confirm that you want to delete the selected images.
❑Automatic image format detection is added for cases of inconsistency of file data with the file extension. For example, if an image has .jpg extension, but in fact it is a .gif image, then the engine won't display the file error, but it will automatically process the image as .gif image.
❑A typographic processing of text is added for TinyMCE and Froala editors. Also, general improvements of typographical processing rules are made.
❑Database load is optimized for articles which are displayed using {custom ...} tag when categories are specified as an articles selection criteria, and articles from some categories are prohibited to be displayed in Group Settings .
❑Automatic detection of the URL encoding is now added for articles from the tag cloud and for results of a search by extra fields. Encoding of such URLs is defined automatically not to loose them if the encoding type is changed, i.e. when replacing windows-1251 with UTF-8.
❑Control System for incorrect user-friendly URLs is improved for articles displayed from the tag cloud, for results of a search by extra fields, and for categories displaying.
❑The system of article blocks caching is improved when they are displayed using {custom ...} tag.
❑Now voting logs and ratings of deleted users are automatically removed. For example, if users are automatically deleted after not visiting a website for a certain time then their information in logs is also cleared. Thus, if a new user will choose a username of a deleted user he will be completely able to rate and vote.
❑The system of safe embedding of flash elements into an article text field is improved. The names of the acceptable variables are no longer case sensitive and can be written in any register.
❑PHPMailer email creation and transfer library has been updated.
❑TinyMCE and FroalaEditor have been updated. Also, in FroalaEditor it is now possible to paste text from MS Word and keep its formatting the way you like.
❑Automatic control of URLs encoding which are published using [lееch=...] text [/lееch] tag. If a URL is published when a certain encoding is used on the website and later the website changed the encoding type then the URL which contains non-latin symbols will also be automatically converted when editing.
❑Now when you rate an article it is checked whether it is allowed to rate the article or not. It prevents from beefing up a user's rating when it is prohibited to rate certain articles.
❑New preventive mechanisms are applied to protect the website from intruders who use social engineering techniques.
❑Loading and rendering of website pages where WYSIWYG editors are used is optimized and accelerated. Gzip is now used to compress TinyMCE editor. Duplicate editors loading is removed for articles and comments editing and also for comment replies.
❑DLE player no longer supports .flv videos.
❑An issue is fixed where [videо=...] tag is not processed if there is no full domain name with a protocol in a video's address.
❑An issue is fixed where website layout is damaged if service DLE tags are used in article headings.
❑An issue is fixed where contents of a hidden text could be seen by users subscribed to comment notifications, even though they might not be allowed to view hidden text when publishing a comment which contain hidden text tags.
❑An issue is fixed where users are allowed to use non-breaking spaces as usernames, which allows to make visually unseen usernames.
❑An issue is fixed where there could be problems with custom extra fields when posting articles. It happened if not all extra fields were used in articles publication template.
❑An issue is fixed where an incorrect signature was sent in the letter confirming the change of e-mail address if the full address of the website was specified without a protocol in the engine settings.
❑An issue is fixed where it is impossible to set 0 as a value of custom extra fields.
List of changes of 11.1 version:
❑Now Two-Factor Authentication is added. This feature can be enabled Engine Settings of Control Panel. If it is enabled all users are able to activate Two-Factor Authentication in their profile settings. When user activates this type of authentication, a one-time PIN is sent to user’s email address as he/she logs in using the own username and password. That one-time PIN must be entered to get an access to user’s account. With this setting user also enables "IP change control" and "Browser and device control". This option improves the security of user data greatly. For example, if account login data is stolen, it is still not enough to access the account, since access to user’s email address becomes necessary.
❑New {twofactor-auth} tag is available in user profile template (userinfo.tpl). It displays the check box where user can enable or disable Two-Factor Authentication.
❑Articles counter for each category is added. Articles are counted in each category taking into account various site settings and parameters of the article. For example, if article is published in a subcategory and subcategory articles display is enabled in parent categories, then this article will be counted in all the parent categories. However, if parent category is also specified in the category list of this article, then the double counting will not be performed. The most effective method is used to count this data, which allows to save memory and reduce loads. For this, MySQL server does its part of counting, and PHP does the rest part. Also, the counted articles are cached if caching is enabled on the website. Although the optimal counting method is used, this option increases the server load, so you can enable or disable it in engine settings of Control Panel. This counted data can be displayed in different ways which will be described further in this description.
❑Now you can make and display category menu in templates. {catmenu} tag is used to display category menu. This tag can be used in any template file, it is global. It uses and embeds categorymenu.tpl template file.
❑{catmenu} tag may not only be used to simply display the category menu, but it can also be customized. The following parameters can be customized for this tag: {catmenu id="1,2,3-5" subcat="yes" template="custom" cache="yes"}
❑A new global {catnewscount id="X"} tag is added for templates. It displays the number of articles within a certain category, where X stands for ID of a needed category. This tag is useful to display the number of categories in manually created menu templates.
❑A completely new HTML code parser is added for articles editing. This parser is used to filter the incoming HTML code when writing articles and static pages. The new parser, unlike the old one, not only checks all the entered text on the security of HTML code, but also automatically corrects user errors in the code. For example, it closes unclosed HTML tags, removes incorrect CSS styles, and fixes bugs related to the validity of entered HTML code. Along with the new parser features, HTML code checking is carried out much faster than in the old parser (in comparison with the previous 11.1 version)
❑All the HTML code generated in articles texts by DLE is transferred according to the HTML5 specification instead of the outdated XHTML.
❑A completely new user password storage system is added in MySQL database. Earlier md5 algorithms were used to store passwords hashes, which have become obsolete fairly quickly. They allowed to get the original password using brute force method if an attacker gained access to the password hash. The new password storage system uses CRYPT_BLOWFISH hashing algorithm, which currently is considered as an attack-proof cryptoalgorithm. This update is designed primarily to protect the original user passwords in case of the database crack, for example, if an attacker gains direct access to the database. Since original passwords are not originally stored in the database, password hashes change is performed in the "soft mode" as users enter the website using their usernames and passwords. Thus, all the existing passwords work, but as users log in, the hashing algorithm is replaced. Also, a new password storage system provides an automatic password hashing algorithms update as soon as new cryptographic algorithms appear for PHP, thereby password hashes will always be stored in a safer way.
❑Thanks to the new password storage system, when a website account connects to a social network account, the initial password no longer resets. If you are a previously registered website user and logged in using a social network, you can no longer continue to use your old password to log in.
❑A more simplified insertion of flash movies and flash players is added. Now the engine will automatically turn the code of a flash video in the safest form, instead of just removing it from the article text. Even though Flash technology is outdated, many websites continue to use it.
❑Now you can restore the forgotten password directly on the page of entering to Control Panel . Also, the password recovery algorithm is changed. Previously, password recovery was disabled for groups that have access to the Administration Panel for security purposes, supposing that administrators will not forget passwords from their website. However, practice has shown that these people forget their passwords too, which led to password recovery problems and to manual editing of the database. Now all users who have access to the Control Panel are always forbidden to recover password from the website, but they always can make it directly from the login page of Control Panel. In order to secure administrator passwords from the recovery in case if, for example, administrator’s email was hacked, Administration Panel address can always be renamed with a unique name, thereby making this page unavailable for the other people.
❑Now mass mailing and messaging can be performed in Administration Panel by choosing a registration date duration of users to send them messages. It provides an additional flexibility for mass mailing.
❑Now mass mailing and messaging can be performed in Administration Panel by choosing a range of users’ last visit dates to send messages to these users. It provides an additional flexibility for mass mailing.
❑Articles sort order by the date of edit can now be used to display articles with a custom format using {custom ...} tag. For this order="editdate" parameter is used. For example, if {custom order="editdate" sort="desc" limit="5"} is used, then the last five edited articles are displayed. This displaying method is useful when you need to show the recent information in the news block, e.g., when links are updated, etc.
❑Now you can add help text when making article extra fields, which will be shown to users while adding articles. It allows you to show tips for users to know what to enter into the field.
❑Now you can specify which user groups are allowed to use a certain field when making article extra fields. It allows you to manage fields not only in terms of categories but also in terms of user groups.
❑Now you can set which user groups are allowed to see certain fields in the published articles when you create article extra fields. It simplifies the process of layout markup if some groups are denied to see certain extra fields. It can be easily enabled and disabled in the Control Panel.
❑New {image-x} and [image-x]text[/image-x] tags are now supported in RSS feed template (rss.tpl). They display URL of an "X" image and show text between them if an image presents.
❑Tags {image-x} and [image-x]text[/image-x] are now able to support text not only from a brief article description, but also from article extra fields. Images numbering firstly comes from a brief description text, then from an extra fields text. This feature is useful for webmasters who do not use an article brief description, and place pictures in extra fields texts.
❑Tags {image-x} and [image-x]text[/image-x] can now ignore emoticons in texts. Previously if emoticons were used in a text they were accounted and displayed by this tag. Now they are completely ignored and not taken into account, and only images from articles are displayed.
❑If an article is removed from a website and sent for moderation, this article is not shown in Related Articles section. Previously, it was necessary to reset the related articles cache to remove it from this block.
❑PHP interpreter running mode now can be automatically detected on a server. If the operating mode has been changed in Server Settings, then features not supported by this mode will be disabled. For example, if advanced authentication mode is enabled in Control Panel and PHP has been switched into FastCGI or CGI where this mode is not supported by the server, this feature will be automatically disabled, and the Administrator will easily log into Control Panel.
❑Now subscription to articles comments is available without leaving a comment there. New [comments-subscribe] text [/comments-subscribe] tags are added in a full article template (fullstory.tpl) and add comments template (addcomments.tpl). Text between them is displayed as a link to the article comments subscription. It allows users to subscribe to comments without leaving a comment.
❑Now you can use extra fields in the feedback section of your website. You only need to place the desired field with the specified name in feedback form to add an extra field there. After that it is available to be used in email message templates. It is necessary to use the following attribute: name = "xfield[X]" in the input field to add additional field to the form, where X is the name of the field written in latin letters.
❑Now in Administration Panel you can set advertising materials to be displayed or not displayed on specific devices. You can set your advertisements to be shown on a single or several types of devices such as: computers, tablets or smartphones. It allows to simplify the template layout, and to slightly reduce the traffic amount if advertising materials are not shown.
❑Now in Administration Panel you can set advertising materials to be displayed or not displayed on specific devices. You can set your advertisements to be shown on a single or several types of devices such as: computers, tablets or smartphones. It allows to simplify the template layout, and to slightly reduce the traffic amount if advertising materials are not shown.
❑Logging of successfully authenticated users who have access to Administration Panel is added in logging system of administrators’ actions . Previously only unsuccessful login attempts and successful authentications to the Control Panel were recorded.
❑The size and checksums calculation for the files uploaded using the engine is added to these files. After that these files are saved in a database along with other information about them. When attachments are displayed for downloading, this information is not calculated in real time for each displayed file, but is taken from the database. This feature significantly reduces the server load when large number of files is published.
❑Now you can specify descriptions for small image versions using FroalaEditor WYSIWYG editor. To set the description you need to write an alternative image description text using the corresponding button on the image. These descriptions will be displayed when original images are opened using smaller image versions.
❑Insertion of small image versions is changed in TinyMCE WYSIWYG editor. Now HTML code is used to display small image versions in the editor instead of BB tags. Thus, the inserted image is instantly displayed in the editor and you can edit the image (for example, you can write its description).
❑[img ...] tag formatting is changed in order to ensure better SEO of your website. Now "alt" attribute of the tag of the first image in the text field is automatically filled with the article headline (if there is no manual description). For all the other pictures this field remains blank. A situation when different images have the same description can have a negative effect on search engine optimization, so it is better to make image descriptions manually if you want to improve the optimization as much as possible. To make this change for the old published articles, it is necessary to run articles rebuilding from Control Panel.
❑Generation of small image version appearance is changed to ensure better SEO of your website and get rid of redundant code. Now an image description is automatically taken from the “alt” attribute. And this attribute will not be automatically filled with the article title if there is no manual description. To make this change for the old articles published earlier, it is necessary to run articles rebuilding from Control Panel.
❑"rel" attribute is now unavailable for the generated code of small image versions in order to secure the validity of the generated code.
❑Now access parameters of user groups are checked to allow or deny them to download files attached to an article . It can be enabled in "Access" tab. For example, if a certain user group is forbidden to view the article, it will not be allowed to download files attached to this article too.
❑Now category access parameters of user groups are checked to allow or deny them to download files attached to an article.. For example, if a certain user group is forbidden to view the articles category, it will not be allowed to download files attached to these articles too.
❑The self-reference detection system of Cross-Reference Module is improved, when AutoCorrect is not performed. Previously, it was necessary to write the link in the full format, including the domain, e.g.: http://site.com/test/1-test.html and only in this case there was no replacement on the page. Now it is sufficient to write its shortened version, without specifying the domain /test/1-test.html and keyword will not be replaced when visiting the page. This feature will be useful if “http” and “https” are both used on a website at the same time and also if multiple mirror domains are used.
❑The check of a category assigned to the article when adding a new category in the mass actions is added in the content management section of Administration Panel. If the category is assigned, then it doesn’t assign again. This feature allows to avoid multiple assignations of categories to articles.
❑The processing system of article extra fields during their displaying in templates is improved. Now it is not necessarily to specify values of these fields in templates in order for these fields to be processed. This feature is convenient for webmasters who use a variety of field values to form the desired template markup, but not to display these fields in the template.
❑Drop-down menu of the Administration Panel is improved so that it does not exceed the visible part of screen when its height is too big.
❑Changes are made in the sort order of the uploaded images. Previously, uploaded images were sorted in the order in which they were uploaded, and when any of the images was deleted they sorted in alphabetical order, which confused users if there are many images in the article. Also, it made it difficult to find the needed image to insert it into the article. Now when you upload images they are also stored in the order in which they were uploaded, but when an image is removed, the order of the other images stays the same.
❑Control system for incorrect user-friendly URL is improved. If a link to homepage or categories has a nested structure with several pages separated by slashes, and it does not end with a slash, it will redirect you on this page, but only with the slash in the end. For example, previously an incorrect link to a category: website.com/test/page/3 without a slash in the end redirected you to website.com/test/, whereas now it redirects you to website.com/test/page/3/ and you will reach the needed page.
❑The engine compatibility with MySQL v. 5.7.x is improved.
❑TinyMCE and FroalaEditor WYSIWYG editors are updated to the latest versions. Many bugs of these editors were fixed for many browsers.
❑An issue is fixed, where a full path to the uploaded avatar haven’t been saved when user logged in using social network account. It could lead to problems with user avatar displaying if a single user data is used on multiple domains and websites.
❑An issue is fixed, where incorrect articles selection could happen sometimes if {custom ...} tag is used with combination of several parameters.
❑An issue is fixed, where extra fields with "Image Gallery" type were displayed incorrectly if various extra fields are displayed simultaneously both in the full article template (fullstory.tpl) and in the main page template (main.tpl).
❑An issue is fixed, where error "Field value is too long" could appear for fields which are automatically generated by the engine, e.g. for description meta tags.
❑An issue is fixed, where reCAPTCHA key couldn’t refresh after successful comment posting.
❑Previously declared and found small errors of the engine are fixed.
List of changes of 11.0 version:
❑Uploading images to comments is now became possible. This possibility is enabled and adjusted in Group Settings. You can adjust image uploading for comments for each user group separately. Also you can set different setting parameters for uploaded images, for example maximum number of uploaded images, image width, height and file size, etc. A user deals with a simplified comment edit form when uploading images to comments. These images are uploaded according to related presets in Group Settings. User is able to manage his uploaded images. They can be deleted or replaced if it is allowed to edit comments.
❑InnoDB engine support is added for MySQL database. You can select the type of storage during the installation of the engine. User can choose InnoDB or MyISAM. We recommend to keep in mind the following when you make this choice: If your website is not frequently updated by new contents (registration of a huge amount of users, frequent comments posting, etc.) then it is recommended to use MyISAM type since it has faster access to a database. If your website is expected to be used for active discussion by a big number of users then we recommend to use InnoDB type. InnoDB is the best option for the most websites since it scales easier in the future. Database type choise is available only if the version of MySQL is 5.6.4 or newer. If MySQL version is older then only MyISAM is available.
❑In this version you can create and manage playlists for video content of the website.
❑Now you also can create a description for video in the player. The following format is used in video tag for this: [videо=path to a video file|path to the thumbnail|description of the video]. The same can be used for a group of video files in a playlist separated by comma. The example of the display may be seen on the screenshot above.
❑Links to YouTube videos can be used in [videо=...] tag. It allows you to create mixed playlists with your uploaded videos and videos from YouTube.
❑In this version you can create and manage playlists for audio content of the website. You need to specify audio files separated by comma in audio tag to add them to a playlist
❑Now you also can create a description for audio tracks in the player. The following format is used in audio tag for this: [audiо=path to an audio track|description of the track]. The example of the display may be seen on the screenshot above.
❑Links to audio streams can be specified to be played in the audio player. It allows you to create and manage playlists of audio streams.
❑Themes selection for the player is available in Player Settings of Administration Panel. You can choose between the light and the dark theme to make the look of your player more suitable to your website’s design.
❑The procedure of embedding of audio and video content is improved in editors. You can create playlists while adding a video. There you can specify links to a video or audio content, links to thumbnails, and their description.
❑A new WYSIWYG editor is used in DataLife Engine. Its name is FroalaEditor. This editor has simple and user-friendly interface (the best interface in our opinion) to create and edit a content. HTML-code generated in it is the most clean and doesn’t have anything unwanted in it. It is also comparitevely lightweight and it renders quickly on the page.
❑A new extra fields type is added for articles. It is called: "Uploaded Image Gallery". In this field you can adjust settings for uploaded images, set the maximum number of images available to upload into this gallery. Image is uploaded by a single click in Administration Panel or on the website. Images are grouped into an image gallery to display this field on the website.
❑The automatic restriction for uploading images or files is added for extra fields of "Uploaded Image" and "Uploaded File" types correspondingly. This restriction works until previously uploaded image or file is removed. It allows to avoid keeping unused files associated to articles on a server.
❑New tags [xfvalue_thumb_url_X] and [xfvalue_image_url_X] are added for extra fields of "Uploaded Image". These tags display URL of smaller version of uploaded image and URL of full-sized image correspondingly, where "X" stands for a name of an extra field. These tags may be useful for webmasters who would like to have customized appearance of published articles, e.g. together with another extra fields.
❑For extra fields of "Yes/No Switcher" type, a possibility to set “On” or “Off” value by default is added which can be used whe adding a new article.
❑Now you can view uploaded by the engine documents online.. For this, the following tags are added into attachments display template (attachment.tpl): {online-view-link} whish displays URL of online view of a document, and [allow-online] text [/allow-online] tags. A text between them is displayed in case if an uploaded document is of the supported format. The following types of documents are available for the online view: Adobe PDF, Microsoft Word, Microsoft Excel. Documents are displayen directly in a user’s browser using Google Docs Viewer service, so users don’t have to have Microsoft or Adobe office software installed on their computers.
❑Since developers of LiveEditor decided to end its support and there weren’t any updates in recent years we decided to remove this editor from DataLife Engine. Websites that were using this editor will be automatically switched to FroalaEditor.
❑Now you can add a description (alt attribute) when attaching multiple images to an article. For this, you need to select a group of images and click on any of them to edit a description. After that, click "Add Selected" button. This description will be applied to all the images when attached.
❑Zend OPCache automatic cache reset is added. It resets the cache when website settings are changed. Thus you don’t need to manually reset the cache or wait for changes to take effect if this feature is activated.
❑The way of the list of categories displaying is changed in categories editing section of Administration Panel. Now all the subcategories are shown in a nested from. They can be expanded for a specific parent category when necessary. Also there are buttons to expand and collapse all categories of the list in one click. A pop-up window is used to add a new category. This simplifies the work with a large number of categories and subcategories in Administration Panel.
❑For each separate article you can unsubscribe all subscribers to its comments. If there are subscribers to an article, then you may see a number of them and unsubscribe them in More tab of Control Panel from this particular article when you edit it. This feature may be useful if article commentation is suspended.
❑Now article comments subscription is available for published comments even when these comments are moderated.
❑In this version there is an indication of number of articles user is subscribed to in a user profile. User can unsubscribe from comments to articles there. For this, a new {unsubscribe} tag is used in userinfo.tpl template. It shows a checkbox which allows to unsubscribe from comments and shows the number of articles user is subscribed to.
❑Also there is an option in user profile that allows users to subsribe to automatic notifications on new comments to their articles. A user doesn’t have to subscribe to every particular article he or she made. User just needs to check the corresponding checkbox on User Profile page. To display the checkbox, a new {news-subscribe} tag is used in userinfo.tpl template.
❑User can subscribe to automatic notifications on replies to his/her comments in user profile. To do this, user needs to just check the corresponding checkbox on his/her User Profile page. To display the checkbox, a new {comments-reply-subscribe} tag is used in userinfo.tpl template.
❑PHP Memcached extension is now supported! DLE engine automatically defines which of PHP extensions is installed, Memcache or Memcached, and depending on that it uses the corresponding PHP extension if Memcache is enabled in engine settings. Thus there is no more need to stick to PHP Memcache extension only.
❑Now it is possible to add one category for multiple articles in a list of mass actions of Edit Article section in Administration Panel. Unlike the currently existing "Change Categories" option, "Add Category" allows to assign chosen categories to the articles, without changing previously created categories.
❑Now you can specify a range of articles in [news=1,2,3] Text [/news] template tag using a dash symbol. For example, you can specify [news=1,2,50-60] Text [/news]. Likewise the range may be specified the same way for the opposite [not-news=1,2,50-60] Text [/not-news] tag. It simplifies the process of design, and you don’t have to specify each article’s ID separated by commas.
❑Now you can specify a range of pages in [page-count=1,2,3] Text [/page-count] template tag using a dash symbol. For example, you can specify [page-count=1,2,50-60] Text [/page-count]. Likewise the range may be specified the same way for the opposite [not-page-count=1,2,50-60] Text [/not-page-count] tag. It simplifies the process of design, and you don’t have to specify each page’s number separated by commas.
❑Now users can unsubscribe from letters sent from "Mass mailing" of Administration Panel. For this, you need to use {%unsubscribe%} tag in a mailing template or in a particular letter, which represents a URL to unsubscribtion from letters for this user. When user follows this link, his/her profile marks gets "Do not receive notification letters" status. User just needs to follow the link without necessity of logging in to the website or performing any other actions. It allows to unsubscribe from notification letters from the website easily if he/she lost the interest in it. Unsubscribed status of user still allows to send him/her notification and information letters. We highly recommend webmasters to take users’ subscription status into account in order not to get into spam filters of users’ mailboxes.
❑A new rel attribute is added for all external references, which are posted in articles and comments. This attribute has "external noopener noreferrer" parameters. It allows to reduce the possibility of potential website attack by social engineering mechanisms.
❑Now you can set the number of days to cache a full article after its publication. Cache creation and updating is a time-consuming operation. Articles lose their popularity over time, and if an article is not often read, then it is inappropriate to create and maintain the cache for it for a long period of time. If there are not many articles published on your website, then you can increase the number of days, but if you do have many articles published, you would better reduce it. Anyway, we do not recommend to set the caching time less than 30 days. Use shorter periods only if you experience problems with a free disk space or if you have many articles published monthly. But for those who do not publish that much articles, we recommend to increase the period.
❑Since this version you can move all the articles from one user to another in Edit Users section of Administration Panel. For this, you must select the needed articles, choose transfer of articles to another user, and specify username where articles will be transferred to. This feature will be useful in case if there is a need to move all the articles to another user before deleting the account.
❑Now you can recount the number of articles of a user automatically in Edit Users section of Administration Panel. For this, you need to click the number of articles and choose Count Articles. This feature can be useful if there were mass actions on articles or articles were added by-passing the engine.
❑Now you can recount the number of comments of a user automatically in Edit Users section of Administration Panel. For this, you need to click the number of comments and choose Count Comments. This feature can be useful if there were mass actions on comments or comments were added by-passing the engine.
❑The speed of articles displaying is improved when articles are sorted by rating or views. The displaying speed of articles sorted by rating is also improved.
❑The system of comments number accounting in user profile statistics is improved. Also, a mass counting of comments is performed when deleting articles. It eliminates the need for periodic statistics recounting.
❑The view of DataLife Engine Administration Panel is optimized for portrait orientation of mobile devices. Thus the control panel became friendlier to smartphones.
❑Jquery library is updated to 2.xx
❑TinyMCE editor is updated to the latest version.
❑In this version the problem is solved, when it was impossible to use a dot symbol in extra fields of cross-reference type.
❑In this version the problem with formatting of invalid HTML markup of nested comments is solved.
❑The problem is solved, where URL to a category with user-friendly URL was displayed for {category-url} tag, regardless of user-friendly URL settings in Administration Panel.
❑The problem is solved, where extra fields’ indexes were doubled for those extra fields which had cross-reference option in case if article is associated with several categories.
❑The problem is solved, where [available=main] text [/available] and [not-available=main] text [/not-available] tags of Home page didn’t work properly if the static page was set to be the Homepage in engine settings.
❑The problem is solved, where a return to the first page of Edit Articles section happened if article’s comments removal was performed in this section, regardless of pre-defined search and display filters.
❑Indicated and previously declared small errors of the engine are fixed.