General Information > Liste des changements

Liste des changements de la version 14.2:

❑Le programme d'installation de DataLife Engine a été entièrement repensé. Il est rendu plus simple et plus polyvalent. Lors de l'installation, vous pouvez désormais choisir la langue dans laquelle l'installation se déroulera, ainsi que la langue qui sera la langue principale du site. Selon la langue sélectionnée, les modèles correspondants seront installés, dans la langue sélectionnée, et les entrées correspondantes seront effectuées dans la base de données. L'ensemble de l'installation s'effectue également grâce à la technologie AJAX en mode entièrement automatique.

❑ Pour les packs de langue situés dans le dossier /language /, la possibilité de spécifier des informations supplémentaires sur la langue a été ajoutée, qui peut être utilisée lors de l'affichage d'une liste de langues. Par exemple, la sortie du nom dans la langue nationale, pour une perception plus pratique de la langue souhaitée par une personne. Pas seulement le nom du dossier où se trouve le module linguistique.

❑Pour les modèles situés dans le /templates / folder, la possibilité de spécifier des informations supplémentaires sur le modèle a été ajouté, qui peut être utilisé lors de l'affichage d'une liste de modèles. Par exemple, la sortie du nom du modèle, dans la liste des modèles sur le site, pour une perception plus pratique du nom du modèle souhaité. Et pas seulement le nom du dossier où se trouve le modèle.

❑Ajout de la localisation ukrainienne du script Datalife Engine. La langue ukrainienne est désormais également incluse dans la norme de distribution et sera prise en charge à l'avenir lors de la mise à jour.

❑Ajout de lapos sibilité de changer la langue du panneau de configuration DataLife Engine à la volée, en étant sur n'importe quelle page du panneau de configuration, sans avoir besoin de se déconnecter et de revenir dans le panneau de configuration. L'utilisateur du panneau d'administration peut choisir l'un des langues disponibles dans le système.

❑Ajout de la possibilité de définir l'ordre des catégories pour les publications, si l'actualité est autorisée à ajouter une publication à plusieurs catégories. L'ordre des catégories sera défini dans l'ordre dans lequel elles ont été sélectionnées par l'utilisateur lors de l'ajout ou de la modification de la publication, et pas dans l'ordre dans lequel ils sont triés dans le panneau d'administration. Par exemple, si la première catégorie de la liste est "Dans le monde", et la seconde est "Sports", et que l'utilisateur a d'abord sélectionné "Sports". et alors seulement "Dans le monde", alors leur tri et leur sortie des nouvelles seront également.

Liste des changements de la version 14.1 :

❑Ajout d'une fonctionnalité d'affichage des données de profil utilisateur pour l'auteur de la publication sur les modèles de sortie de publication courte et complète (shortstory.tpl et fullstory.tpl). Comme la fonctionnalité nécessite également une requête de base de données supplémentaire, elle peut être activée ou désactivée dans les paramètres du script dans la section des performances optimales. Par conséquent, la fonctionnalité peut être activée si nécessaire ou désactivée pour améliorer les performances du script et réduire la charge sur le serveur. Pour développer une telle fonctionnalité, plus de trente nouvelles balises de modèle ont été ajoutées, qui contiennent des informations de profil utilisateur, y compris des données de champs supplémentaires.

❑Pour les modèles de sortie de commentaires (comments.tpl), le support de nouvelles balises de comparaison a été ajouté. Par exemple, [if field = "value"] text [/if] affiche le texte incorporé si la valeur du champ est égale à la valeur spécifiée.

❑Ajout de la prise en charge de la nouvelle mise en cache via le cache deframework Resdi. Le type de cadre de cache (Encaissement de fichiers, Memcache ou Redis) peut être sélectionné dans les paramètres de script. Si votre serveur Redis nécessite un login et un mot de passe pour se connecter ou protégé par mot de passe, toutes les données d'autorisation nécessaires peuvent être spécifiées. Pour utiliser ce type de framework de cache un Serveur Redis et un plugin pour l'interpréteur PHP php-redis doit être installé sur le serveur.

❑Le cache Memcache a été modifié. Ces modifications ont été apportées pour éviter d'éventuels problèmes avec le cash-flush automatique sur les projets à forte charge, car dans certains cas, les informations sur les clés mises en cache peuvent être supprimées en raison du manque de mémoire cache pour les stocker. Par conséquent, la mise en cache d'autres données peut prendre plus de temps que d'habitude.

❑Pour les balises de comparaison [if field = "value"] text [/if] ont été ajoutés le support pour d'autres balises de modèle. Par exemple, l'expression suivante: [if autor = "{profile-login}"]Viewed by post's author[/if] affiche le texte spécifié, si le message est consulté par son auteur. Cela donne plus d'options pour la conception de modèles.

❑Pour ajouter et modifier des pages statiques dans le panneau de configuration, une fonction d'affichage a été ajoutée, afin qu'un utilisateur puisse voir la page juste après son ajout ou sa modification.

❑Le support de plus de 200 nouveaux services et sites a été ajouté à la balise [mеdia=...]. En effet, le support de tous les sites et services connus utilisant oEmbed pour échanger des données et ajouter du contenu aux posts a été ajouté.

❑ Support de la nouvelle balise {cloudstag} dans le template main.tpl a été ajouté. Cette balise permet d'afficher un mot-clé du nuage de tags, si un utilisateur navigue dans une catégorie de site contenant des articles ayant un mot-clé spécifique du nuage de tags. Cette mise à jour peut être utile pour les webmasters qui souhaitent afficher un mot-clé sélectionné ailleurs, par exemple à l'aide des balises HTML h1 et etc.

❑Vers le modèle de sortie du menu des catégories (categorymenu.tpl) une fonctionnalité permettant d'afficher la description des catégories dans le menu a été ajoutée. À cette fin, la prise en charge des nouvelles balises de post a été ajoutée: {description} - affiche la description de la catégorie, [description] text [/description] - affiche le texte incorporé si la description est spécifiée, et les balises inversées: [not-description] text [/not-description] - affiche le texte intégré si la description n'est pas spécifiée.

❑Vers le modèle de sortie du menu des catégories (categorymenu.tpl) un supprt des noulles balises a été ajouté: [not-parent] text [/not-parent] - affiche le texte incorporé si la catégorie n'est pas une catégorie parente et n'a pas de sous-catégories. En fait, cette balise est une balise inversée de la balise [isparent] text [/isparent].

❑Ajout de la prise en charge de nouvelles balises dans le modèle de sortie du menu des catégories (categorymenu.tpl): [is-children] text [/is-children] - affiche le texte incorporé si une catégorie a une catégorie parent, et le support des balises inversées: [not-children] text [/not-children] - affiche le texte incorporé si une catégorie n'a pas de catégorie parente.

❑Champ supplémentaire de type "Switchbox 'Oui' ou 'Non'" a été modifié : au lieu de la balise HTML select, on a utilisé la balise input (checkbox). Cela permet de s'assurer que le remplissage d'un champ sur le site correspond au remplissage du champ dans le panneau de contrôlel.

❑Vers des champs supplémentaires avec la propriété active "use as cross-link" le support du symbole de la barre oblique "/" a été ajouté.

❑Pour la sortie de commentaires personnalisés {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.

❑Pour une sortie personnalisée des commentaires {customcomments ....} un nouveau paramètre newsidexclude="1,3,5-15" a été ajouté pour entrer l'ID des articles à exclure de l'affichage des commentaires. Par exemple, avec la balise {customcomments newsidexclude="3-10"} tous les commentaires, à l'exception de ceux des messages ayant l'ID 3-10, seront affichés.

❑Pour les messages personnalisés, la balise de sortie {custom ....} un nouveau paramètre subcat="yes" a été ajouté. Le paramètre peut être utilisé avec les options category="list" ou categoryexclude="list". Ce paramètre indique si les articles des sous-catégories doivent également être inclus. Le paramètre peut prendre l'une des valeurs suivantes: subcat="yes" indique que tous les messages de la catégorie et de ses sous-catégories seront sélectionnés, subcat="only" indique que seuls les articles des sous-catégories seront sélectionnés et que les articles de la catégorie ne le seront pas. Par exemple, le site n'a que des catégories avec les ID 1, 2 et 3. 1 est une catégorie, 2 et 3 sont ses sous-catégories. Si la balise {custom category="1" subcat="yes"} est utilisé, tous les messages des catégories 1, 2 et 3 seront sélectionnés. Si la balise {custom category="1" subcat="only"} est utilisée, seuls les messages des catégories 2 et 3 seront sélectionnés. Cela permet d'assouplir le processus de saisie des paramètres de requête, sans avoir à énumérer toutes les catégories dans la balise. Si de nouvelles sous-catégories sont ajoutées dans le panneau de contrôle, les articles seront affichés automatiquement sans qu'il soit nécessaire de modifier les modèles.

❑ Mots clés du nuage de tags peuvent désormais contenir un symbole de barre oblique "/".

❑En raison du fait qu'Instagram appartient à Facebook, pour intégrer leur contenu sur le site, il faut avoir une application d'échange de données enregistrée sur leurs services, donc si vous ajoutez du contenu d'Instagram avec la balise [mеdia=...] à la publication, DLE l'intégrera en utilisant l'application spécifiée dans les paramètres du script pour l'autorisation du réseau social Facebook. Sur les paramètres de l'application sur Facebook, l'accès au contenu via oEmbed doit être autorisé. Après cela, l'ajout de contenu depuis Instagram et Facebook en utilisant la balise [mеdia=...] sera disponible.

❑Ajout d'une fonctionnalité aux paramètres des scripts permettant d'activer ou de désactiver le paramètre NOREFERRER pour tous les liens externes dans les messages. Si le paramètre est activé, tous les liens externes dans les messages seront marqués comme NOREFERRER, ce qui ne permet pas au navigateur de partager avec des sites externes les informations sur la provenance de l'utilisateur.

❑Ajout d'une fonctionnalité aux paramètres des scripts permettant d'activer ou de désactiver le paramètre NOREFERRER pour tous les liens externes dans les commentaires. Si le paramètre est activé, tous les liens externes dans les commentaires sont marqués comme NOREFERRER, ce qui ne permet pas au navigateur de partager avec des sites externes les informations sur l'origine de l'utilisateur.

❑Après le chargement des fichiers .webm et .m3u8 ils seront traités automatiquement comme des fichiers vidéo et pourront être ajoutés à un message et lus automatiquement sur le site à l'aide d'un lecteur vidéo.

❑Ajout de la possibilité d'envoyer l'en-tête "304 Not Modified" pour les messages, en cas de réception de la demande correspondante de la part des moteurs de recherche. Si aucune modification n'a été apportée au message pendant une période donnée, DLE n'envoie qu'un court message HTTP correspondant avec le code 304. Cela permet de réduire la consommation de bande passante sur le serveur et donc de réduire la charge sur le serveur..

❑Ajout d'informations d'erreur plus détaillées pour les messages privés, lorsqu'une erreur se produit. Par exemple, si un utilisateur non autorisé se rend dans la section des messages privés, une notification s'affiche, lui demandant de se connecter ou de s'enregistrer pour continuer. Si un utilisateur suit un lien depuis un e-mail de notification de nouveau message privé et souhaite le lire, mais qu'il n'est pas connecté, la notification lui demandera de se connecter pour lire le message.

❑Les règles du site peuvent désormais être consultées juste après avoir été modifiées via le panneau de contrôle.

❑La bibliothèque jQuery a été mise à jour avec la dernière version 3.5.x, pour l'utiliser, activez jQuery 3 dans les paramètres de script sur le panneau de contrôle du site.

❑Ajout d'une fonctionnalité pour l'éditeur visuel Froala qui permet d'insérer divers objets tels que des feuilles, des listes d'images et de vidéos.

❑Ajout de l'intégration des widgets Apple music pour la lecture de musique en ligne à l'aide de balises iframe tags. En outre, les droits d'accès aux balises HTML iframe peuvent désormais être gérés à l'aide de l'attribut allow.

❑Ajout de nouveaux symboles guillemets simples (') et le signe (&). Vous pouvez désormais saisir, par exemple, Jeanne d'Arc ou des mots similaires.

❑Ajout de la prise en charge de l'option "Autoriser les moteurs de recherche à indexer les liens postés dans les commentaires" pour les éditeurs visuels WYSIWYG des sites. Auparavant, cette option n'était disponible que si l'éditeur BBCODES et les liens balisés BB étaient utilisés dans les commentaires.

❑Pour les plugins générés, les messages ont ajouté l'affichage du code source valide, lorsque les balises [cоde] ... [/cоde] ont été utilisées. La mise en évidence du code source et des balises a également été ajoutée pour rendre le texte plus facile à lire.

❑En raison de certains changements dans les algorithmes de YouTube le protocole Oembed a commencé à générer du code pour les petites vidéos par défaut. La logique de la balise. [mеdia=...] a également été modifiée. Désormais, si vous ajoutez une vidéo YouTube, les paramètres de la vidéo DLE seront appliqués et la hauteur de la vidéo DLE sera calculée automatiquement. Cela garantit que la vidéo aura la bonne taille par rapport aux autres vidéos affichées sur le site à l'aide du lecteur DLE.

❑Les métabalises des pages telles que l'en-tête, la description, les mots-clés, etc. peuvent désormais contenir des crochets et des parenthèses. Au lieu d'être supprimés, les symboles sont convertis en code HTML valide afin d'être affichés correctement par le navigateur.

❑Des modifications avaient été apportées à la logique d'affichage des images chargées pour les messages. Avant la mise à jour, seules les images chargées sur le serveur à l'aide du script DLE étaient affichées dans la liste et stockées sur le serveur. Maintenant, si pour une raison quelconque l'image a été complètement supprimée de la liste sans le script DLE, elle sera remplacée par un placeholder informant que l'image a été supprimée du serveur. Cela peut être utile pour les sites où les utilisateurs peuvent ajouter un nombre limité d'images par message. Ainsi, si une image est manquante, elle peut être supprimée des messages, et la limite du nombre maximum d'images peut être préservée.

❑Le lecteur vidéo DLE a été mis à jour avec la dernière version disponible. Plusieurs problèmes de disponibilité du lecteur vidéo sur divers appareils et navigateurs ont été corrigés.

❑Analyseur de code HTML entrant de messages a été mis à jour pour la dernière version disponible. Ajout du support des nouveaux attributs des paramètres HTML pour le support HTML5.

❑Des modifications ont été apportées aux commentaires cités. Si un utilisateur cite un commentaire avec du texte masqué et dispose de suffisamment de droits d'accès pour voir le texte masqué, ce texte masqué sera inclus dans son propre commentaire avec une citation, y compris les balises du texte masqué. Si un utilisateur n'a pas assez de droits d'accès pour voir le texte masqué, ce texte masqué sera exclu de son devis. Avant, le texte masqué était toujours exclu des guillemets, même dans les cas où un utilisateur avait suffisamment de droits d'accès pour le voir.

❑Ajout d'une vérification supplémentaire des erreurs possibles commis par l'administrateur du site lors de la modification des droits d'accès des groupes d'utilisateurs sur le panneau de contrôle. Par exemple, avant, l'administrateur pourrait accidentellement accorder l'accès à toutes les catégories et restreindre l'accès à certaines catégories en même temps. En conséquence, certaines fonctions du DataLife Engine peuvent ne pas fonctionner correctement

❑Ajout de la prise en charge des caractères "$" pour les noms d'utilisateur et les mots de passe des bases de données du serveur MySQL.

❑Ajout du support de PHP 8.xx

❑L'algorithme de génération de lien canonique a été modifié pour les sites utilisant les protocoles HTTP et HTTPS. Si un utilisateur accède au site via HTTPS ou si l'option "Toujours utiliser HTTPS" est spécifiée dans les paramètres, un lien canonique sera également toujours généré à l'aide du protocole HTTPS, quel que soit le protocole préféré spécifié pour le site dans les paramètres du script. Même si aucune préférence n'a été spécifiée.

❑ Amélioration de la génération de métabalises og:description via le protocole Open Graph pour un affichage complet du message. Désormais, dans les cas où des champs supplémentaires sont impliqués, seuls les champs de texte seront utilisés pour la génération de balises. Il peut s'agir d'une seule chaîne de texte ou de plusieurs chaînes de texte. Tous les autres types de champs, tels que les images et les fichiers, seront exclus de la génération de balises.

❑Correction d'un problème où les liens de publication sur le panneau de configuration et le plan du site ne fonctionnaient pas, si la publication appartenait à la catégorie qui a été désactivée dans les paramètres des catégories.

❑Correction d'un problème lors de la navigation via le panneau de contrôle, certaines pages actives peuvent ne pas être mises en évidence correctement.

❑Correction d'un problème avec certains messages privés, l'aperçu peut ne pas s'afficher correctement sur le panneau de contrôle du script.

❑Correction d'un problème dans certains cas, après l'édition d'une page statique, l'utilisateur était redirigé vers la liste des messages au lieu de la liste des pages statiques.

❑Correction d'un problème avec neutralisation de l'utilisateur ainsi que suppression des réseaux sociaux liés pour les utilisateurs de Firefox.

❑ Correction d'un problème avec le traitement des balises de sortie des icônes de catégories dans les modèles de sortie des messages courts et complets, lorsque d'autres modèles de fichiers non standard (shortstory.tpl et fullstory.tpl) étaient utilisés pour la catégorie.

❑Correction d'un problème avec les balises [if ..] ... [/if] ne fonctionnaient pas correctement si un champ contient des caractères majuscules.

❑Correction d'un problème avec les balises [if ..] ... [/if] ne fonctionnaient pas correctement, si un champ contient plusieurs valeurs distinctes (par exemple, des messages avec plusieurs catégories), et que la vérification était effectuée sur la valeur négative avec une condition combinée. Par exemple, la condition [if category != "1" AND category != "2"] not 1 and not 2[/if] ne fonctionnait pas correctement, si l'article était publié dans plus d'une catégorie.

❑Correction d'un problème avec les balises [not-ios] ... [/not-ios] et [not-android] ... [/not-android] dans les cas où les balises inversées étaient absentes du modèle.

❑Correction d'un problème les catégories n'étaient pas enregistrées correctement lors de l'importation de messages depuis des flux RSS vers le site.

❑Correction d'un problème échec avec la génération de liens canoniques pour l'aperçu d'un post contenant certains champs supplémentaires, où le CNC était activé, mais où un utilisateur a utilisé un lien avec le CNC désactivé. Cela se produisait parfois lorsque les paramètres du site étaient modifiés et que le site était indexé par les moteurs de recherche.

Liste des changements de la version 14.0 :

❑Nous avons entièrement repensé le module de gestion des images téléchargées dans le panneau d'administration. Vous pouvez désormais naviguer dans tous les dossiers de cette section, quel que soit le niveau d'imbrication. En plus des dossiers standard, vous pouvez ouvrir et gérer des images dans des dossiers créés par vous-même. Nous avons également ajouté un aperçu des images - il suffit de cliquer sur celles-ci en plein écran.

❑Nous avons ajouté la prise en charge de la vidéo avec un débit binaire adaptatif (fichiers HLS au format .m3u8) au lecteur vidéo DataLife Engine.

❑Nous avons ajouté le support de nouvelles balises de condition de comparaison de valeurs aux modèles d'affichage de l'histoire courte et de l'histoire complète (shortstory.tpl et fullstory.tpl). Par exemple, la balise [if field = "value"] text [/if] affichera le texte qu'elle contient si la valeur du champ est égale à la valeur spécifiée. Cette balise peut non seulement comparer l'égalité, mais aussi faire des comparaisons "plus ou moins", trouver des entrées.

❑Nous avons ajouté l'option de bloquer temporairement et automatiquement un compte dans le panneau d'administration du site Web lorsqu'il est inactif. Vous pouvez spécifier un délai d'attente en minutes dans les paramètres du script, après quoi, si l'utilisateur n'a rien fait dans le navigateur du panneau d'administration, sa session sera temporairement suspendue jusqu'à ce que le mot de passe soit saisi. Dans ce cas, l'utilisateur verra une notification et s'il continue à ne rien faire, la session sera suspendue. Cette innovation sera utile pour assurer une sécurité supplémentaire, si un utilisateur quitte temporairement son ordinateur avec un onglet du panneau d'administration ouvert. Pour reprendre la session, il suffit de saisir un mot de passe sans avoir à entrer un login.

❑Nous avons ajouté la possibilité de lier n'importe quel compte de réseau social disponible à un compte sur le site web. L'utilisateur du site peut lier un ou plusieurs réseaux à son compte, et les utiliser à l'avenir pour se connecter à son propre compte sur le site web. Pour lier un réseau social à son compte, l'utilisateur doit se connecter sur le site web, aller dans son profil et y faire le lien. Dans ce cas, vous pouvez utiliser tous les comptes d'un réseau social, il n'y a pas de conditions de correspondance, par exemple, concernant les adresses e-mail. Pour lier les réseaux sociaux dans le modèle de profil d'utilisateur, les mêmes balises que dans le modèle login.tpl sont utilisées pour la connexion via les réseaux sociaux : {vk_url}, {odnoklassniki_url}, {facebook_url}, {google_url}, {mailru_url}, {yandex_url}

❑Nous avons ajouté la possibilité de dissocier n'importe quel réseau social du compte sur le site web. Même s'il a été utilisé à l'origine pour la connexion initiale au site Web et la première inscription. Pour ce faire, nous avons ajouté la prise en charge de la balise {social-list} au modèle d'affichage du profil de l'utilisateur, qui affiche une liste des réseaux sociaux liés et des liens permettant de les déconnecter de ce compte.

❑Dans les paramètres de catégorie du panneau d'administration du script, nous avons ajouté l'option pour attribuer à chaque catégorie son propre type d'évaluation des articles. Désormais, chaque catégorie peut disposer de son propre type d'évaluation, et pas seulement de l'évaluation commune à l'ensemble du site.

❑Dans la section d'édition des messages du panneau d'administration, 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.

❑Dans la section d'édition des messages du panneau d'administration, nous avons ajouté l'option de recomptage des commentaires pour les actions de masse pour les messages sélectionnés. Ainsi, vous pouvez recompter tous les commentaires en un clic, uniquement pour les articles sélectionnés.

❑Si un champ supplémentaire est obligatoire, pour ajouter ou modifier des messages nous avons ajouté l'affichage d'informations sur le champ qui est vide et doit être rempli. Auparavant, une erreur générale indiquant un champ obligatoire vide était affichée, et les utilisateurs devaient trouver par eux-mêmes quel champ particulier est obligatoire.

❑Nous avons ajouté l'option de charger des icônes pour les catégories directement à partir du panneau d'administration de DataLife Engine. Vous pouvez charger les icônes dans la section de gestion des catégories lorsque vous ajoutez ou modifiez une catégorie.

❑Pour les modèles d'affichage des articles, ainsi que pour le modèle d'affichage du menu des catégories, nous avons ajouté le support de nouvelles balises: [category-icon] text [/category-icon] affichent le texte qui y est inclus, si dans les paramètres de catégorie une icône a été définie pour la catégorie dans laquelle le message est situé. Nous avons également ajouté la prise en charge des balises opposées: [not-category-icon] text [/not-category-icon] qui affichent du texte si aucune icône n'est définie pour la catégorie dans laquelle se trouve le message. Ainsi, vous pouvez créer le design de vos modèles de manière plus flexible, selon que la catégorie possède ou non une icône.

❑Pour le modèle d'affichage du menu des catégories, nous avons ajouté un lien vers l'icône par défaut, s'il n'y a pas de lien vers l'icône de catégorie pour la catégorie sélectionnée. Auparavant, une valeur vide était affichée comme balise d'affichage de l'icône, si aucune icône n'était définie dans les paramètres de la catégorie.

❑Nous avons ajouté l'option d'utiliser les symboles @ et ~ dans la recherche de sites , qui servaient de symboles auxiliaires lorsqu'ils étaient utilisés pour la recherche en texte intégral sur des tables travaillant avec InnoDB.

❑Nous avons ajouté le support de la compression de données basée sur l'algorithme Brotli pour les JS, CSS et HTML générés par le moteur DataLife. Cette méthode est plus efficace et plus rapide que la compression de données zip ordinaire. Pour utiliser cet algorithme de compression, le serveur doit disposer des extensions de serveur appropriées pour PHP. Si DLE détermine que votre serveur prend en charge cet algorithme, il sera utilisé automatiquement. Dans le cas contraire, la compression sera effectuée avec les moyens disponibles, par exemple la compression zip.

❑Nous avons ajouté l'option de télécharger et de supprimer des images pour les utilisateurs qui n'ont le droit de publier des histoires qu'après modération, et qui sont en même temps autorisés à modifier les messages. À cette fin, des modifications ont été apportées à la procédure de téléchargement d'images - si l'utilisateur prend des mesures pour télécharger ou supprimer des images ou des fichiers, l'histoire est automatiquement renvoyée pour subir une modération.

❑Nous avons ajouté l'option permettant de spécifier le caractère de délimitation des mots-clés attribués au nuage de mots-clés dans les paramètres de script du panneau d'administration lorsqu'ils sont affichés dans des messages sur le site.

❑Nous avons ajouté l'option d'utiliser le code HTML pour les délimiteurs d'affichage des catégories et pour le module breadcrumbs lorsqu'ils sont spécifiés dans les paramètres du script. Par exemple, vous pouvez définir “</span><span class=”test”>” pour créer un formatage plus flexible et diversifié pour votre modèle.

❑Nous avons ajouté la prise en charge de lazy loading pour les vidéos Youtube publiées à l'aide de la balise [media = ...], ainsi que pour tout autre contenu publié à l'aide de la balise HTML iframe. Si vous activez le chargement paresseux des images dans les paramètres du script, ce chargement paresseux sera également utilisé pour le contenu ci-dessus. Cela accélérera également le chargement des pages de votre site Web, car le contenu requis sera chargé dans le navigateur uniquement lorsque l'utilisateur fera défiler la page.

❑Nous avons ajouté la prise en charge de lazy loading pour les images publiées dans le texte des commentaires des utilisateurs. Auparavant, le chargement paresseux des images n'était disponible que pour les articles.

❑Nous avons également ajouté le compte des restrictions dans la fenêtre de téléchargement de fichiers apparaissant lors de l'affichage des informations sur les restrictions sur la taille et le volume des données téléchargées définis dans les paramètres du serveur. Par exemple, si dans les paramètres du script de l'utilisateur, il est autorisé de télécharger un fichier de 5 mégaoctets et que les paramètres du serveur ne permettent pas de télécharger plus de 2 mégaoctets, il sera également indiqué pendant le téléchargement que la taille maximale est de 2 mégaoctets. Cela vous permet d'éviter immédiatement toute confusion en cas de divergence entre les paramètres du script et ceux du serveur.

❑Nous avons également ajouté l'affichage du nombre de fichiers qui peuvent être téléchargés par l'utilisateur dans le module de téléchargement d'images et de fichiers, si leur nombre est limité dans les paramètres.

❑Nous avons ajouté l'option de rechercher les messages non autorisés pour l'indexation web pour la recherche avancée des articles dans le panneau d'administration. Ainsi, vous pouvez trouver rapidement les articles pour lesquels vous devez modifier cette option.

❑Nous avons modifié le comportement du comptage du nombre d'histoires pour le menu de la catégorie. Auparavant, le comptage était effectué sur la base des paramètres globaux d'affichage ou non des histoires appartenant aux sous-catégories. Maintenant, le comptage est effectué sur la base des paramètres attribués individuellement pour chaque catégorie.

❑Nous avons ajouté le support de viber://, tg://, skype://, market:// protocols pour les liens publiés sur le site web. Ces protocoles permettent d'ouvrir des liens basés sur des sites web dans des applications installées sur le téléphone, comme Viber, Telegram, Skype et Android Market.

❑Nous avons ajouté la compatibilité du transfert de la base de données d'une version ultérieure à une version antérieure pour le module de sauvegarde de la base de données. Par exemple, le site web a été créé à l'origine sur MySQL 8.0 et est transféré sur un autre serveur où est installé MySQL 5.7. Dans ce cas, la sauvegarde de la base de données sera créée dans un format compatible avec MySQL 5.7.

❑Dans les cas où la page contient plusieurs lecteurs avec de la vidéo et de l'audio, nous avons ajouté l'arrêt automatique des fichiers lus si l'utilisateur lit une vidéo ou un fichier audio à partir d'autres lecteurs sur cette page.

❑Nous avons apporté des modifications au système de formation du menu des catégories. Si l'affichage de certaines catégories n'est pas autorisé dans les paramètres du groupe et que l'affichage des nouvelles de ces catégories est également interdit, ces catégories seront également automatiquement exclues de l'affichage dans le menu pour ce groupe d'utilisateurs.

❑Nous avons mis à jour le lecteur vidéo DLE à la version actuelle, et corrigé un certain nombre de petits bogues et amélioré la lecture des vidéos sur les appareils mobiles.

❑Nous avons également ajouté la recherche et le remplacement dans les titres des articles dans le module "Recherche et remplacement" du panneau d'administration, si la recherche par histoires et titres de pages statiques est définie, ainsi que la recherche et le remplacement sur les pages statiques.

❑Nous avons ajouté la vérification automatique des connexions par les mots-clés spécifiés dans le module "Filtre de mots" du panneau d'administration dans le processus d'enregistrement de l'utilisateur sur le site web. Si le filtre correspond, l'enregistrement de l'utilisateur sera refusé. Cette fonctionnalité sera utile si vous définissez un filtre pour les mots obscènes, il n'est pas nécessaire de remplir en plus les noms interdits à l'enregistrement dans les filtres destinés à l'enregistrement.

❑Nous avons ajouté la suppression automatique des balises d'affichage des valeurs des champs supplémentaires du modèle, dans le cas où les données de ces champs supplémentaires sont manquantes. Par exemple, il existe un champ supplémentaire de type "galerie" et vous affichez ses valeurs non pas avec une seule balise d'affichage, mais séparément pour chaque image en utilisant la balise [xfvalue_X image = "Nr"], et si l'une des images n'a pas été téléchargée, alors sa balise d'affichage sera automatiquement masquée. Cette innovation concerne non seulement l'affichage des images, mais en général l'affichage de tout champ supplémentaire et de ses valeurs.

❑Nous avons ajouté l'interdiction d'envoyer des messages personnels aux utilisateurs qui font partie d'un groupe pour lequel l'utilisation de messages personnels n'est pas autorisée. Auparavant, il était possible d'envoyer des messages, mais les utilisateurs ne pouvaient les lire que lorsque cette interdiction était levée.

❑Nous avons ajouté la sauvegarde automatique du tri des champs supplémentaires du profil de l'utilisateur dans le panneau d'administration. La sauvegarde se fait automatiquement lorsque l'ordre est modifié, vous n'avez pas besoin d'appuyer sur un bouton supplémentaire pour sauvegarder.

❑Nous avons ajouté le masquage automatique d'un commentaire en attente de modération dans la section de gestion des commentaires du panneau d'administration après l'avoir édité et publié sur le site. Ainsi, le modérateur peut rapidement passer au traitement du commentaire suivant.

❑Nous avons ajouté le recomptage automatique des statistiques dans le panneau de contrôle en cas d'édition de commentaires en attente de modération.

❑Nous avons apporté des changements au système de filtrage des données entrantes destiné à la recherche sur site, dans le cadre duquel la recherche de certains mots clés s'est améliorée.

❑Nous avons optimisé le tri des champs supplémentaires pour les messages dans le panneau d'administration. Cela ajoute l'option d'effectuer plusieurs tris ou opérations sur les champs sans recharger la page au préalable.

❑Nous avons amélioré le système de détermination du protocole de site utilisé http ou https prévention de la lecture incorrecte des paramètres du serveur sur certaines configurations.

❑Nous avons amélioré le système incorrect de contrôle des liens CNC Nous avons amélioré le système incorrect de contrôle des liens CNC.

❑Nous avons mis à jour les éditeurs visuels TinyMCE et Froala aux dernières versions, et corrigé un certain nombre d'erreurs identifiées dans ces éditeurs.

❑Nous avons apporté des changements au système de contrôle du comptage des votes concernant le classement des messages et des commentaires qui a corrigé le problème survenant lorsque certains utilisateurs voulaient changer leur vote et ne pouvaient pas le faire.

❑Nous avons résolu le problème avec lagénération d'un lien vers l'article complet, si la catégorie est désactivée et qu'il s'agit de la première catégorie de la liste de plusieurs catégories.

❑Nous avons résolu le problème, qui provoquait des erreurs JS lors de l'activation de l'utilisation des emoji natifs et de la désactivation de l'éditeur de commentaires.

❑Nous avons résolu le problème, qui provoquait l'interruption du travail des champs supplémentaires avec le type de fichier téléchargé en cas de reconstruction des postes dans le panneau d'administration.

❑Nous avons résolu le problème, à cause de quoi les options d'articles "Publier sur la page d'accueil", "Autoriser les commentaires" et "Autoriser l'évaluation" n'étaient pas supprimées automatiquement lors de l'ajout ou de la modification d'articles dans le panneau d'administration, si plusieurs catégories avaient simultanément une interdiction d'utiliser ces options pour l'article en question.

❑Nous avons résolu le problème, qui provoquait la duplication de l'en-tête List-Unsubscribe lors de l'envoi de courriers électroniques en masse à partir du site.

❑Nous avons résolu le problème, ce qui, dans certains cas, a entraîné la suppression de commentaires publiés et un comptage incorrect des commentaires lors du traitement des commentaires en attente de modération.

❑Nous avons résolu le problème, la cause de la recherche avancée par commentaires ne fonctionnait pas, si la recherche plein texte et la modération des commentaires étaient activées dans les paramètres du script.

❑Nous avons résolu le problème, à cause duquel la recherche avancée ne fonctionnait pas, si une période de temps pour la recherche de commentaires était spécifiée.

❑Nous avons résolu le problème, à cause duquel la balise méta de description a été formée de manière incorrecte, si l'article n'a pas été ajouté ou modifié dans le panneau d'administration, et si le contenu de l'article était trop petit.

Liste des changements de la version 13.3 :

❑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.

Liste des changements de la version 13.2 :

❑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.

Liste des changements de la version 13.1 :

❑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 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.

❑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.

❑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.

Liste des changements de la version 13.0 :

❑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.

Liste des changements de la version 12.1 :

❑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.

Liste des changements de la version 12.0 :

❑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.

Liste des changements de la version 11.3 :

❑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.

❑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.

❑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.

Liste des changements de la version 11.2 :

❑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.

Liste des changements de la version 11.1 :

❑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.

❑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.

Liste des changements de la version 11.0 :

❑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.