Following changes have been developed and added:
1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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”
16. 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.
17. 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.
18. 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.
19. 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.
20. 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.
21. 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.
22. 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.
23. 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.
24. 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.
25. 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.
26. 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.
27. 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.
28. 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.
29. 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.
30. 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.
31. Added automatic removal of the static page map from the site map, if there are no static pages on the site.
32. Added automatic removal of the category map from the site map, if there are no categories on the site.
33. 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.
34. 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.
35. 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.
36. 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.
37. 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.
38. 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.
39. Added support for DataLife Engine JS scripts on some types of browsers embedded in TVs.
40. 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.
41. 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.
42. 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.
43. 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.
44. 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.
45. The navigation system in the RSS import management module of publications in the DataLife Engine control panel has been improved.
46. Improved the visual design of the Froala and TinyMCE editors when using a dark theme in the DataLife Engine control panel
47. 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.
48. Updated internal third-party libraries, as well as jQuery and the TinyMCE visual editor to the latest versions.
49. 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.
50. Added support for PHP 8.2.xx
51. 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.
52. 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.
53. 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.
54. Fixed an issue where caching of comments output using the {custom comments ….} tag did not work
55. 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.
56. Fixed an issue where there were problems when using uploading images and files in Yandex browser.
57. Minor issues in the script that were detected and stated earlier have been fixed.
已经制定并添加了以下更改：
1.增加了对上传网站上出版物和静态页面的HiDPI（Retina）图像和屏幕截图的自动支持。在图像上传管理器中，在上传图像之前，您可以指定图像是高像素密度的图像，例如，这是在HiDPI（Retina）屏幕上拍摄的屏幕截图，DataLife Engine将在加载时自动创建两份图像副本，一份用于普通屏幕，另一份用于高密度屏幕，以及当访问者查看网站时，如果他有高密度屏幕，他会看到高密度像素图像，如果是普通屏幕，那么是普通图像。对于较小的图像副本也会发生同样的情况。因此，您可以在您的网站上自动发布高质量的高清屏幕截图。作为实现的一个示例，您可以查看此新闻中发布的图像。只有在编写出版物时使用视觉编辑器时，才支持插入高清晰度图像。
2.图像缩略图副本的显示在原始尺寸的基础上进行了完全重新设计，并转移到现代JS库的使用。图片库的显示也经过了重新设计。现在，您可以在模板的帮助下轻松更改视觉外观，画廊的所有元素都使用矢量图形进行了调整，图像在任何设备上的显示都变得舒适，包括支持手势的移动设备，可以舒适地观看放大的图像。
3.在网站上显示短新闻时，数据库查询已被重新设计。当使用包含大量发布的大型数据库时，这些查询得到了优化。当浏览短新闻页面时，从数据库中进行采样的速度要快得多，并且消耗的服务器资源也要少得多。
4.您网站的RSS提要生成系统已经重新设计。由于Yandex和DZen已经分离，现在不可能在单个流中形成内容。因此，DataLife Engine现在为不同的服务同时广播三个不同的流。在地址http://yoursite/rss.xmlRSS以用于各种系统和服务的通用格式进行广播，并且完全符合RSS 2.0标准。在http://yoursite/rssturbo.xmlYandex Turbo出版物的RSS订阅源在http://yoursite/rssdzen.xmlZen出版物的RSS订阅源正在播放。现在，线程是完全独立的，彼此不相交，而是单独工作。这同样适用于网站和用户出版物类别的分离。您可以在脚本的文档中详细查看RSS提要的所有地址。此外，在这方面，RSS提要的模板格式也发生了变化。新建标记[rss]。。。[/rss]用于标准rss块，[turbo]。。。[/turbo]标签用于turbo新闻块，[dzen]。。。[/dzen]标签用于zen新闻块。更新后，您需要使RSS模板与新的操作模式保持一致。例如，您可以从分发档案中获取标准模板templates/rss.tpl。
5.增加了对WebDAV外部存储的支持，用于上传和存储图像和文件。此存储的类型是在控制面板的脚本设置中选择的。用于连接和使用此存储器的参数也设置在那里。
6.为允许编辑出版物但禁止访问DataLife Engine管理控制面板的用户添加了在网站上完全编辑出版物的功能。以前，他们只能进行快速编辑，但现在他们可以完全编辑所有字段的新闻，包括空白的附加字段。为此，使用了在网站上添加出版物的模块，用户将在添加页面上编辑新闻，而已填充的字段将已填充，并且他只能进行必要的编辑或补充出版物中未指定的字段。
7.设置允许插入iframe标记的域名列表的功能已添加到脚本设置中。因此，您可以独立指定一个安全域列表，从中插入发布内容。您还可以完全禁用在网站上的出版物中插入iframe标记的权限。
8.在控制面板的脚本设置中，添加了启用和禁用PHP错误输出的功能，如果这些错误发生在代码中。建议在技术工作期间启用此选项，例如，在更新脚本之前或安装插件之前，以便在出现错误时可以直观地看到它们。此设置允许您不更改服务器设置以启用此功能，也不查看服务器错误日志以查看问题。n已修复。
9.为所有网站访问者添加了一个自动重置浏览器静态JS和CSS文件缓存的系统。当您单击DataLife Engine控制面板中的“清除缓存”功能时，会重置一个特殊的唯一缓存ID，该ID由脚本在连接静态CSS和JS文件时使用。如果使用｛include标记…｝连接模板中的样式和脚本，则浏览器缓存也将重置。因此，例如，在更改模板样式时，您可以重置缓存，确保所有访问您网站的访问者无一例外地立即看到更新的信息和布局，而无需等待浏览器中的缓存过时。
10.为所有模板添加了一个新的全局标记｛cache id｝，它输出当前的缓存id，您可以在连接静态文件时在模板中使用该id，绕过｛include file＝…｝等内部DLE功能，当站点管理员单击控制面板中的“清除缓存”按钮时，它们的浏览器缓存将自动重置。例如，您可以将<link href=“{THEME}/font/style.min.css？v={cache-id}”rel=“stylesheet”type=“text/css”>构造用于静态样式文件。
11.TinyMCE视觉编辑器的外观设计经过了重新设计。菜单的显示已被删除，其所有功能都以按钮的形式立即显示，因此可以更方便地可视化访问编辑器的功能，而无需在各种菜单中搜索它们。
12.对于TinyMCE视觉编辑器，增加了使用预设样式快速设计块的功能。例如，您可以一键设计信息块或警告块，设置块的边界等。这使出版物的设计更容易、更快。
13.对于TinyMCE视觉编辑器，添加了在插入和编辑图像时为图像选择预设类的功能，您可以自行在模板中进行排列。因此，您可以在一次点击中立即将所需的设计放入图像中。
14.当使用TinyMCE视觉编辑器在网站上写评论和个人信息时，添加了快速插入用户登录信息并链接到其个人资料的功能。只要输入@符号，然后开始输入用户的登录信息，DataLife Engine就会自动搜索用户数据库并提供自动插入选项。发布后插入的内容会自动转换为用户卡的链接，当你点击它时，你可以看到用户的信息，给他写消息，并访问他的个人资料。
15.该网站上的在线文档查看服务已被微软的服务取代，而不是谷歌以前使用的服务。这确保了查看时更完全的兼容性，并且还添加了对可用于在线查看的其他新格式的支持。支持格式的完整列表：“doc”、“docx”、“docm”、“dotm”、“dotx”、
16.为RSS新闻导入模块添加了全面的编辑器。根据在控制面板中为出版物启用的编辑器，它将在编辑简短出版物和接收完整出版物时自动连接和使用。
17.当从各种RSS源在控制面板中导入出版物时，如果链接指定了一个没有域的路径，则会添加到图像的自动转换链接。例如，如果源站点“/image/file.jpg”上有一个链接，那么它将自动转换为包含源域的链接https://domain.com/image/file.jpg”，因此这些图像将在出版物中正确显示。
18.在从各种RSS源导入出版物的模块中添加了接收完整新闻时对不正确HTML代码的自动预过滤。根据您为RSS源设置的HTML模板接收到内容后，将对其进行不支持或未关闭的标记的预筛选，并进行完全筛选，然后显示在编辑器中进行进一步编辑。
19.对于位于templates文件夹中的模板参数文件（info.json），添加了指定模板属于哪种类型（浅色或深色）的功能。要执行此操作，请使用参数“type”：“light”表示模板为浅色，使用参数“type”：“dark”表示模板是深色。当您启用模板为深色时，所有视觉编辑器将自动切换到深色模式，并具有相应的深色设计，而无需手动编辑模板样式。
20.对于完整的新闻输出模板（fullstory.tpl），添加了一个新的{related ids}标签，该标签输出该新闻的类似发布ID列表。当与｛custom…｝标记一起使用时，此标记非常有用，例如，｛custom-id=“｛related ids｝”｝标记将显示此出版物的所有类似新闻，并支持所有可能的模板标记，而与基本的｛relative news｝标记不同，在基本的｛。因此，您有更多的机会在网站上设计出版物。
21.对于个人消息输出模板（pm.tpl），添加了对新标签的支持：{login}，该标签输出个人消息作者的登录，没有任何额外的设计。
22.对于个人消息输出模板（pm.tpl），增加了对新标签的支持：{date=date format}，它以标签中指定的格式输出日期。因此，您不仅可以输出整个日期，还可以输出其各个部分。日期格式是根据PHP中采用的格式设置的。例如，标签{date=d}将显示新闻或评论发布的月份的日期，标签{date=F}将显示月份的名称，标签{date=d-m-YH:i}将显示完整的日期和时间。
23.对于用户配置文件输出模板、评论、个人消息（comments.tpl、pm.tpl、userinfo.tpl、profile_popup.tpl），添加了对新标签的支持：{lastdate=date format}，该标签以标签中指定的格式输出用户最后一次访问该网站。因此，您不仅可以输出整个日期，还可以输出其各个部分，或者使用自己的日期格式，而不是默认的日期格式。日期格式是根据PHP中采用的格式设置的。例如，标签{lastdate=d}将输出月份的日期，标签{lastdate=F}将输出月的名称，标签{listdate=d-m-YH:i}将输出完整的日期和时间。
24.对于用户配置文件输出模板、评论、个人消息（comments.tpl、pm.tpl、userinfo.tpl、profile_popup.tpl），添加了对新标签的支持：{registration=date format}，该标签以标签中指定的格式输出用户注册的日期。因此，您不仅可以输出整个日期，还可以输出其各个部分，或者使用自己的日期格式，而不是默认的日期格式。日期格式是根据PHP中采用的格式设置的。例如，标签{registration=d}将输出月份的日期，标签{register=F}将输出当月的名称，标签{gistration=d-m-YH:i}将输出完整的日期和时间。
25.已为您的网站页面的元标签添加了自动标签使用<link rel=“preconnect”href=“http://yourwebsite.com/“fetchpriority=”high“>，这使您可以保持浏览器连接打开状态，在访问网站的其他页面时不再打开。这使您能够略微提高和加快网站的响应速度，尤其是在互联网连接缓慢的情况下。
26.在脚本设置中，在文件上传设置部分，添加了设置文件写入服务器时将对其设置哪些访问权限的功能。有两种模式可供选择：“公共”和“私人”。使用专用模式时，将仅为文件的所有者设置完全访问权限，文件将以该所有者的名义上载到服务器。使用公共模式时，将为所有服务器用户设置完全权限。默认情况下，使用公共模式，但对于一些使用S3协议的外部服务器，有必要启用私有模式。例如，Cloudflare S3服务。这为用于数据存储的各种云服务提供了更广泛的支持。
27.在将大文件上传到服务器时设置包大小的功能已添加到脚本设置中。上传大文件时，这些文件被拆分为单独的包，以免超过服务器上设置的限制。您可以指定一次发送到服务器的数据包的大小，以兆字节为单位指定。发送的数据包越少，上传到服务器的速度就越快。您还可以根据服务器限制的具体设置来设置自己的数据包大小。
28.增加了在上传文件用于发布时将文件添加到队列的自动过滤功能。如果要发布的上传图像或其他文件的数量有限制，用户将无法向队列中添加超过允许数量的文件。此外，对图像和其他文件的过滤是相互独立的，并且每个限制都会单独考虑。因此，用户不仅清楚地看到他已经用完了限制，无法添加更多，而且不必要的数据和文件也不会发送到服务器，从而节省了服务器资源。
29.在将图片上传到网站上的评论时，如果对可以上传评论的图片数量设置了最大限制，则还增加了对排队文件的自动限制。
30.如果脚本设置中禁用了标记云支持，或者如果标记云没有关键字，则添加了从站点地图中自动删除标记云地图的功能。
31.增加了如果网站上没有静态页面，则自动从网站地图中删除静态页面地图。
32.添加了如果网站上没有类别，则自动从网站地图中删除类别地图。
33.对于评论和个人消息，使用{date}标签时，评论或个人消息的日期输出已更改。当显示日期时，将更详细地说明自消息发布以来有多少时间，如果有分钟，它将指示有多少分钟，如果有小时，有多少小时，如果不到一周，将指示一周中的哪一天和时间，等等。因此，始终可以清楚地看到此评论的发布时间。
34.对于显示注册日期和用户上次访问日期的模板标签{registration}和{lastdate}，在使用它们的整个网站上，该日期的输出都发生了更改。在显示日期时，引入了一种更高级的统计方法，用于统计自该日期以来经过了多少时间。如果分钟已经过去，它将指示已经过去了多少分钟，如果小时，那么已经过去了几个小时，如果不到一周，那么将指示一周中的哪一天和时间。因此，它将始终清晰可见，例如，用户在网站上的最后一次活动。例如，我20分钟前在网站上，或者昨天12:20，等等。
35.当在网站上引用评论时，已自动添加引用消息离开时的日期。同时，如果有一点时间过去了，那么为了便于阅读，它会指示自消息发布以来有多少时间过去了。例如，10分钟前。此外，随着时间的推移，这些信息会在网站上自动更新。
36.在Datalife Engine控制面板的设置中，增加了设置控制面板缩放比例的功能。所有面板元素都按比例缩放，这将允许一些用户更方便地使用控制面板。
37.在Datalife Engine控制面板的设置中，添加了启用额外字体平滑的功能，这使您可以在一些监视器上看到更舒适的文本。
38.所有规则都在文件中。用于管理Apache服务器的访问权限已被重写，以便同时支持所有Apache行，包括2.2.x和2.4.x行，即使某些模块被禁用。
39.在嵌入电视的某些类型的浏览器上增加了对DataLife Engine JS脚本的支持。
40.增加了对使用“拖放”方法上传出版物其他领域的图像和文件的支持。要开始下载文件，只需用鼠标将文件从计算机移动到该字段的下载按钮所在的区域即可。
41.网站上出版物的评级被切换为使用数据xx属性，而不是使用HTML中的id属性。因此，您可以在一个出版物的多个位置同时使用评级输出，例如，在出版物的底部和顶部，以便在网站上进行更方便的评级。自动更新也将同时发生在安装它的几个地方。
42.网站上的评论评级已切换为使用数据xx属性，而不是使用HTML中的id属性。因此，您可以在一个注释中同时在多个位置使用评级输出，例如，在注释的底部和顶部，以获得更方便的评级。自动更新也将同时发生在安装它的几个地方。
43.通过持续不断的多次请求，在对树注释被禁用的注释的响应的情况下，在注释字段中插入用户的昵称后，自动转移到新行已经被删除。当使用可视化编辑器时，将使用快速插入到用户卡的链接。
44.当切换控制面板的主题和操作模式时，TinyMCE视觉编辑器的自动重建和更新已添加到面板设置窗口，而无需重新加载页面。例如，当切换到深色主题时，编辑器也会自动完全更新并切换到使用深色主题，而不会使页面过载。
45.数据生命引擎控制面板中出版物的RSS导入管理模块中的导航系统得到了改进。
46.在DataLife引擎控制面板中使用深色主题时，改进了Froala和TinyMCE编辑器的视觉设计
47.为DataLife引擎控制面板添加了一个新的附加配色方案。它旨在使面板显示得更温暖，同时对内容的感知更具对比度。我们希望用户会喜欢新的附加方案。此方案是可选的，并且在面板设置中启用，所有以前存在的方案也将保留。
48.将内部第三方库以及jQuery和TinyMCE可视化编辑器更新为最新版本。
49.增加了在服务器上使用GD2库时将AVIF格式的图像上传到服务器的功能。只有在服务器上安装了PHP 8.1及更高版本，并且还支持从服务器解码图像数据时，才能使用此功能。
50.增加了对PHP 8.2.xx的支持
51.修复了一个问题，即在短新闻输出模板中检查模板文档中描述的标签[if field=“value”]text[/if]的某些字段不起作用。
52.修复了一个问题，即如果新闻本身从网站上删除，则无法删除上传到新闻评论的图像。
53.修复了在两种不同的http和https协议上同时使用网站时，在TinyMCE编辑器中插入表情符号的错误操作问题。
54.修复了使用{custom comments….}标记缓存注释输出不起作用的问题
55.修复了在DataLife Engine管理面板中使用深色主题编辑网站评论时TinyMCE视觉编辑器显示错误的问题。
56.修复了在Yandex浏览器中使用上传图像和文件时出现的问题。
57.先前检测到并说明的脚本中的小问题已得到修复。