Console intitle datalife engine control panel. Adding pictures and files to DLE. Data for access to MySQL server

Data Life Engine (DLE)is a multi-user news engine designed to organize your own blogs and media on the Internet. With a powerful system for publishing, customizing and editing news, the engine is one step ahead of its closest competitors. And thanks to the precise and thoughtful structure of the kernel, which minimizes the requirements for server resources, the engine is able to easily work with highly visited projects without creating any special load on the server. Flexibility and ease of customization and integration of your own design will allow you to deploy your own sites in the shortest possible time, without any additional material costs. Using advanced AJAX technology will reduce both your server traffic and the traffic of your visitors, not to mention the convenience of using this technology on the site. Due to the increased attention to the security of the script, to the convenience of working with it, as well as dynamic development, more than 70,000 portals that successfully use it in their work have already spoken in favor of using the DataLife Engine. The engine is optimized for search engines which will bring more customers to your site.

Official site:http://dle-news.ru/

FAQ: http://dle-news.ru/faq.html

Please note that this software ispaid, and the installation will be discussed with an exampledemo versions.

InstallationCMS DLE

    To start installing DLE, you need to go to the hosting control panel using the link and data sent to your contact e-mail when ordering the service.

    Download the CMS DLE (DataLife Engine) distribution, for example here http://dle-news.ru/demo.html .

    Go to the hosting control panel, point "File Manager" and then to the directory www/domain_name. Delete by default the index.html file created when adding the domain, press the "Upload" button, select the CMS DLE archive and press OK.

    After downloading the CMS DLE (DataLife Engine) archive, click on it once so that it is highlighted and press the "Extract" button. After unpacking the archive, you should come to this view:

    Next, we need to create a CMS DLE (DataLife Engine) database, for this, in the hosting control panel, go to the "Databases" item and click the "Create" button. Enter the database name, username and password and click OK:

In the future, the name of the database and user is used with a prefix in the form of your login in the hosting control panel:

The Database Type column displays the database host db01.site.

    After performing the above steps, we access the browser by the name of your domain, proceed to install CMS DLE (DataLife Engine), press the button "Start installation":

Note! To start installing CMS DLE (DataLife Engine) when accessing a domain, the domain must already respond to records from the hosting server. If the domain has just been added to the server and information about its records has not yet been distributed over the network, you can register and save it on your computer in hosts file following entry: server IP address domain name

83.69.23*.*** domain name

The IP address of the server can be viewed in the hosting control panel item Domain names- Entries entry:

domain_name.ru.

A (Internet v4 address)

    At the next step, to continue the installation, you need to read and accept the license agreement.

We put a daw "I accept the terms of the agreement" and continue with the installation.

9. One of the important steps during installation is setting up the system configuration, where you need to correctly specify the data for connecting to the database and set the login and password of the site administrator.

The data that is required from you (using the example of our user):

Base name: vh12345_dle

Database username: vh 12345_ admin

Password: the password you specified when creating the database

MySQL server: column Type of database in the section Databases db01.site(see item 4) or

indicate in this field mysql.your_domain

The prefix is ​​set arbitrarily.

Data for access to the control panel is the creation account administrator of your site, here we indicate the desired login / password and e-mail administrator.

    Installation of CMS DLE (DataLife Engine) is completed.

Delete file install.php, it is located in the directory www/your_domain

    We request a domain through a browser, enter the CMS DLE (DataLife Engine) admin panel and start working with the site.

Let's talk about the menu on the dle website. More precisely, how to add your own items to the menu, or replace existing ones with new ones. Quite often, for beginners who have just installed this CMS, the question arises: “How to replace the standard menu items in the standard template with your own?” If, in wordpress, this can be done without editing the code, then in dle the situation is different, you still have to get into the code and figure it out a bit. However, there is nothing difficult in adding new items, and I hope you can see this today.

So, let's get down to business. To begin with, we need to create items that later need to be implemented in the dle menu, be it pages or categories. To do this, go to the admin panel and click on the item "list of all sections."

And then it all depends on the situation. If we need to add a link to the site category to the menu, then go to the “Categories” item, and if we need to create a page that the menu item will direct the user to, then go to the “Static Pages” item. There is no fundamental difference between them, so we will choose one of the two options, for example, "Categories".

A form for creating a new category on the site will appear. Everything is simple there. What each form field is used for, see image.

Not all fields that are described in the figure are mandatory, but only the first and second fields. And the points that I did not touch on the image do not relate to categories at all, but to global engine settings, such as dle news output settings, and also provide the ability to assign a unique template for each category separately.

After filling in the required fields, at least the first two, click on the add button. This action will create a new category on the site, a link to which we will add to the dle menu. And Special attention note the second field, where it was necessary to write an alternative name for the category, which will be the address at which the category will be located. In my example, it will look like this: http://site.ru/primer_category/

Now, let's move on to directly adding a new item to the dle menu.

To do this, in the admin panel you need to go to the "Website Templates" section.

And then you need to select one of the two files, if a standard template is used, in which the menus on the site are registered. There are two types of menus in the standard template: this, and both horizontal and vertical. The topmenu.tpl file is responsible for the horizontal menu, and the sidebar.tpl file is responsible for the vertical menu in the left column of the site. Both of these files can be found in the left column of the Site Templates section. And when you click on one of them, the code of this file will appear in the right column.

After opening the file, we need to fix any existing item on ours. That is, change the name, in this case to the name of the category. And substitute a link to the category itself (alternative name), instead of #. That is, if I replace the “About site” item, then the menu code will look like this:

By analogy, you can change the rest of the menu items. As for the second, horizontal menu, the situation is exactly the same there. And of course, everything that you don't need can be removed. And of course, save the edited file.

If you are not sure about something, for example, that you will delete something superfluous, then just do it so that in case of unforeseen situations it can be restored.

And that's all for me.

The following changes have been prepared and implemented:


1. Added the ability to upload images to the server for comments published on the site. This opportunity enabled and configured in the group settings. For each user group, you can enable or disable uploading images for comments. Also, for each group, you can set different individual parameters for uploaded images, for example, maximum amount uploaded images to comments, their size and weight, etc. When uploading images to comments, the user has access to a simplified form for uploading comments, and images are uploaded according to the parameters specified in the group settings. At the same time, the user can manage his uploaded images. He can delete or replace them if he is allowed to edit his comments.

2. Added support for InnoDB engine for MySQL database. When installing the script, you can choose which type of storage to use. You can choose to use either InnoDB or MyISAM. When choosing an engine, we recommend to be guided by the following criteria. If your site will rarely be updated with new content (registration of a large number of users, active addition of new comments, etc.) i.e. reference site, it is recommended to use MyISAM type, it is faster when fetching from the database. If the site is planned to be actively discussed by a large number of users, it is recommended to use InnoDB type. For most sites the best choice it will be InnoDB, because it scales more easily in the future. The choice of database engine is available only if your server has a version of MySQL not lower than 5.6.4. If the MySQL server version is lower, then only MyISAM is available.

3. Added the ability to create and use playlists when playing videos on the site. To do this, video files are simply listed in the video tag separated by commas. For example:
4. Added the ability to create a description, for a video that will be visible when shown in the player, for this, the following format is used in the video embed tag: , the same can be set for all files if a comma-separated file playlist is used. You can see an example of the display in the screenshot above.

5. Added the ability to use in the tag, also links to videos in the Youtube service. Thus, you can organize mixed playlists that include your video and videos on the Youtube service.

6. Added the ability to create and use playlists when playing audio on the site. To do this, audio files are simply listed in the audio tag separated by commas. For example:
7. Added the ability to create a description, for audio that will be visible when playing music in the player, for this, the following format is used in the audio embed tag: . You can see an example of the display in the screenshot above.

8. Added the ability for the audio player adding links to play streaming audio. Thus, you can set and display playlists to listen to on your site of radio stations.

9. In the settings of the players, in the admin panel, added the ability choosing a theme for the player. You can choose either a dark or light theme for the player, which makes the display of the player on your site more organic.

10. Improved procedure for inserting video and audio materials in editors. When adding a video, you can immediately create playlists, and you can immediately set in the input window not only a link to video and audio, but also links to posters for them, and a description for video and audio files.

11. A new WYSIWYG editor has been added to the DataLife Engine. The name of the new editor is FroalaEditor. This editor has an easy and understandable interface (in our opinion, the best interface) for creating and editing content, the HTML code it generates is one of the cleanest and has almost nothing superfluous, it is relatively lightweight, it has a fast rendering of the editor on the page.

12. Added a new type for additional fields of publications:"Downloadable image gallery". While creating of this type fields you can set parameters for uploaded images, as well as the maximum number of images that can be uploaded for this gallery. When adding a publication in the admin panel or on the site, the image can be uploaded in one click. When displaying this field on the site, the images will be grouped into a gallery of pictures, which can also be flipped through each other when viewing, if small copies were created for the pictures.

13. For additional fields of type"Download image" and "Upload file", added automatic prohibition of re-uploading images and files until the previous uploaded image or file is deleted. This reduces the likelihood of attaching unused files and images to the news.

14. For additional fields of type "Upload image" new tags added: and , which output only the URL for the thumbnail of the uploaded image and the URL for the full image, respectively, where "X" is the name of the optional field. These tags will be useful for webmasters who want to personalize the uploaded publications on the site, for example, in combination with other additional fields.

15. For additional fields of the type "Switch Yes or No", Added the ability to assign the state "Enabled" or "Disabled" by default, which will be used when adding a new publication.

16. Added the ability online viewing documents, uploaded to the site through the DataLife Engine script. To do this, the following tags have been added to the uploaded files output template (attachment.tpl): (online-view-link) which displays a URL link to view the document online in the browser, as well as tags text, which output the enclosed text if the loaded document is in a supported format for viewing. The following types of documents are supported for online viewing: Adobe PDF, Microsoft Word, Microsoft Excel. Documents are viewed directly in the visitor's browser using the Google Docs Viewer service, so visitors do not need to have installed programs from Microsoft or Adobe.

17. Due to the fact that the developers of the WYSIWYG LiveEditor decided to stop any work on this editor, and he has not received any updates for several years, it was decided to remove this editor from the DataLife Engine. Sites that previously used this editor will automatically switch to using the FroalaEditor.

18. Added the ability to set a description of images (alt attribute) when mass inserting images into news. To do this, you need to select the desired images, and by clicking on any of them, set a description. Then click on the "Insert Selected" button. The specified description will also be added for all pictures when pasted.

19. Added automatic cache reset Zend OPCache when changing site settings. Thus, when this caching is enabled in the server settings, you do not need to reset the cache yourself, or wait for the changes to take effect.

20. When viewing the list of categories in the admin panel, in the category editing section, the display of the list of categories has been changed. Now all subcategories are shown collapsed and can be opened directly when needed for a particular parent category. And also added buttons, thanks to which you can quickly expand or collapse all categories in the list in one click. Adding a new category is carried out in a pop-up window. This simplifies the work with a large number of categories and subcategories in the admin panel.

21. Added the ability to unsubscribe all users, subscribed to comments, for each news separately. If the news has subscribed users, then when editing this news in the control panel, in the "Advanced" tab, you can see the number of subscribers and unsubscribe them from comments on this particular publication. This innovation will be useful, for example, if the news is closed from further commenting.

22. Added the ability to subscribe to comments to the news when a comment is posted, even when the comment is being moderated.

23. In the user profile on the site, added the ability unsubscribe from subscribed comments to publications, indicating the number of publications to which the user is subscribed. To do this, in the template userinfo.tpl (unsubscribe), which displays a checkbox for unsubscribing from comments, and the number of subscribed publications.

24. In the user profile on the site, the ability to automatically subscribe to receive notifications about new comments that are added to the news, the author of which he is. Thus, the user does not need to subscribe separately to each of his news, it is enough to cancel the corresponding checkbox in the settings of his profile. To display a checkbox, in a template userinfo.tpl added new tag usage (news-subscribe).

25. In the user profile on the site, the ability to automatically subscribe to receive notifications of new comments that are responses to his own comments. To do this, just uncheck the corresponding checkbox in your profile settings. To display a checkbox, in a template userinfo.tpl added new tag usage (comments-reply-subscribe).

26. Added support for PHP Memcached extension. The DLE script automatically determines which PHP extension is installed, Memcache or Memcached on the server, and depending on this, uses one or another PHP extension, if Memcache caching is enabled in the script settings. Thus, it is no longer necessary to install the PHP Memcache extension on the server.

27. In the admin panel, in the section for editing publications, to the list of mass actions on publications, the ability to add categories to publications has been added. Unlike the existing "Edit categories" item, the "Add category" item allows you to mass-assign new selected categories to publications, without changing old, previously added categories.

28. For the template tag Text added the ability specify a news range using a dash character. For example, you can specify Text Text. This makes it easier to create the design you need, and there is no need to prescribe all the IDs of the required publications separated by commas.

29. For the template tag Text added the ability specify the range of pages you want using the dash character. For example, you can specify Text. Similarly, the range can be set for the opposite tag Text. This makes it easier to create the design you need, and there is no need to prescribe all the numbers of the pages you need, separated by commas.

30. Added the ability to unsubscribe to site users from mailing letters, which are sent from the "Messaging" section of the admin panel. To do this, when sending emails, you can set either in the template or directly in the message text the tag (%unsubscribe%), which displays in the sent email the URL for unsubscribing from receiving the newsletter for the user. When you click on this link, for the user profile, the status "Do not receive emails from the site" is set. At the same time, the user just needs to follow the link, he does not need to log in or perform any other actions on the site. Thus, he can easily unsubscribe from letters from the site if he has long lost interest in the site. Despite the fact that sending letters allows you to still send a message to the user, even if he has expressed a desire not to receive letters. We strongly recommend that webmasters, in order to avoid getting the server into spam filters, always take into account the status that the user has set in their profile when sending messages.

31. Added automatic addition for all external links, which are published in the news and comments, attribute rel, containing the parameters "external noopener noreferrer". This attribute allows you to reduce the likelihood of a possible attack on the site using social engineering mechanisms.

32. In the script settings, added the ability to specify the number of days, during which to cache the full news after its publication. Creating and updating the cache is also a resource-intensive operation. Over time, the publication also loses its popularity, and if it is not often read, then it is not advisable to create and control the cache all the time for it. If your site publishes little news, then you can increase the number of days during which to cache, if a lot, then reduce. In any case, we do not recommend setting the cache time to less than 30 days. Not a large number of days, use only if there are problems with free space on the server's hard disk, or if you publish a very large number of news per month. But for those who have little news on the site, we recommend increasing this value.

33. In the admin panel, in the user editing section, the ability has been added quick transfer of all publications from one user to another. To do this, click on the number of publications of the user, select the transfer of publications to another user, and specify the username of the user to which you want to transfer publications. This innovation will be useful if, before deleting a user from the database, you need to transfer all of his publications to another user.

34. In the admin panel, in the user editing section, the ability has been added quick recalculation of the number of publications by the user. To do this, click on the number of publications of the user and select the recalculation of publications in the menu. This option will be useful if mass manipulations with publications were performed, or additions to the database bypassing the script.

35. In the admin panel, in the user editing section, the ability has been added quick recalculation of the number of comments a user has. To do this, click on the number of user comments and select the recalculation of comments from the menu. This option will be useful if mass manipulations with comments were performed, or additions to the database bypassing the script.

36. Improved performance of news output when using sorting by rating and views. Also improved the performance of the output of comments that use sorting by rating.

37. Improved the system for accounting for the number of user comments in his profile statistics. Mass deletion of news also automatically recalculates user comments. This eliminates the need for periodic recalculation of statistics.

38. Optimized the display of the DataLife Engine admin panel on mobile devices in portrait orientation. Thus, the control panel has become more convenient when using it on smartphones.

39. Jquery library has been updated to line 2.xx

40. Updated the TinyMCE editor to the current version.

41. Fixed a problem where it was impossible to use the dot in the add. fields of the cross-reference type.

42. Fixed a problem where invalid layout of HTML comments was formed when using tree-like comments.

43. Fixed a problem where for the tag (category-url), the URL to the category was displayed using the CNC, regardless of the CNC settings in the script's admin panel.

44. Fixed a problem where there was a duplication of indexes of additional fields, having the option of cross-references, if the news is published in several categories.

45. Fixed a problem where text and text tags worked incorrectly for home page, if the script settings have enabled displaying a static page on the main page as the main one.

46. ​​Fixed a problem where if the news was cleared from comments in the publications editing section, then there was always a return to the first page of the news editing section, regardless of the search filters and displaying publications for editing.

47. Fixed a problem where it was impossible to enter the correct answer to the Q&A system if the user is replying to a comment rather than adding a new one.

48. Minor bugs in the script that were discovered and announced earlier have been fixed.

Information for downloading the script for clients:

Attention! Viewing this information is available only to users who have a license for the script. If you have already purchased the script, then you need to go to the site under your client account.

If you are not yet our client, then you can visit our website.

You can discuss the release at

Hi friends. I spend almost all of my time. Since most of my sites are built on CMS DLE, I have to work a lot with this engine. I have said before that developers are not friends with SEO, and in general they have never heard such a word, but it turned out to be even worse than it could be. I even prepared a whole series of posts dedicated to the "ossification" of the national engine (see in the category).

But today I would like to talk about such an important thing as the html sitemap for DLE. No matter how much I searched the Internet for a normal card module, I did not find it. There are, of course, several solutions, but all of them do not give the desired result at all, and sometimes even cause harm. I had to write the module myself, or rather entrust the implementation of my “wishlist” to professionals. I express my deep gratitude to Alexander Fomin for his enthusiasm and incredible speed of work.

The sitemap module for DLE that I am about to introduce to you meets all the requirements of seo and is extremely easy to install.

A complete list of modules for DLE from Alaich "a:

SiteMap - HTML sitemap generation module for DLE

Original name: sitemap
CMS Compatibility: DLE 8.2- 10.6
Spreading: Free, As Is, when distributing a link to the source is required
Current version: 2.2 (from 05/08/2014)
Purpose: Output an unordered list with links to all publications, categories and static pages.
Peculiarities: Visual embed code generator. Detailed setting of the principle of displaying all site elements - news, categories, static pages - the number of displayed elements, sorting principle and sorting order, displaying elements as a link or plain text, the ability to include/exclude specific elements.

Description and configuration of the HTML sitemap module for DLE

Friends, June 3, 2012 is a big day, a brand new sitemap version 2.0 has been released. We are raising the usability bar of our module to a new level. We (I hope you, too) liked the visual code generation system implemented in the system and we decided to implement it in the sitemap module. Now you do not need to read manuals and descriptions of all functions and their values ​​- just go to the admin panel, specify a few values ​​and that's it - the module is ready to go!

In addition to the above, I would like to list a few more important features:

  • the module is fully cached;
  • the module uses the DLE API;
  • the map does not display publications that have not passed moderation, as well as those planned for the future;
  • the presence / absence of CNC, as well as the type of CNC are taken into account;
  • such a subtlety is provided - if someone has been working with the DLE engine for a long time, then he remembers that in the early versions there was no CNC at all, and then it appeared, but only of one type (the same as type 3 is now being formed). So this is also provided for in this module - new publications are displayed with a url, the CNC type of which is selected in the admin panel, and old ones, respectively, with the url of the CNC of the old type.

Despite the appearance of a visual generator, I suggest that you familiarize yourself with the mechanics of the module.

The module is inserted into the main.tpl template using the tag:
(include file="engine/modules/sitemap.php?param1=value1¶m2=value2")

param1= — module parameter, value1 — parameter value. Module settings come after the sign? and separated by &.

Insert example (displays a sitemap with a list of static pages and news from categories with id=2,3,4):
(content)
(include file="engine/modules/sitemap.php?show_static=1&need_cats=2,3,4")

In order for the sitemap to be displayed on a separate page, the (include ...) tag must be enclosed in , and the (content) tag must be enclosed in . After that, the module will be available at http://site.ru/sitemap/

After any changes to the parameters and their values, it is necessary to clear the cache in the admin panel.

Module parameters passed via tpl when inserting:

  • need_cats - a list of id categories separated by commas for display in the map
  • exc_cats - list of id categories separated by commas, excluded from the map
  • need_news — comma-separated list of id articles to display in the map
  • exc_news - comma-separated list of article ids to be excluded from the map
    • it is pointless to specify these parameters at the same time
  • need_static — comma-separated list of static page ids to display in the map
  • exc_static - list of id static pages, separated by commas, excluded from the map
    • it is pointless to specify these parameters at the same time
  • cats_as_links - show category names as links (1 or 0)
  • show_static - show static pages in the map (1 or 0)
  • cats_sort - category list sort field (field from dle_category table)
  • cats_msort - category list sorting direction (ASC or DESC)
  • news_sort - sorting field for the list of articles (field from the dle_post table)
  • news_msort - direction of sorting the list of articles (ASC or DESC)
  • static_sort - sort field for the list of static pages (field from the dle_static table)
  • static_msort - direction of sorting the list of static pages (ASC or DESC)
    • There are 2 sorting options:
      • ASC - ascending (alphabetically)
      • DESC - descending (in reverse order)
    • if the field and sorting order are not specified, the specified category settings or standard DLE parameters are used
  • cats_limit - maximum number of subcategories to display
  • news_limit - the maximum number of output articles from the category
  • static_limit - the maximum number of displayed static pages

Notice none of the above settings are required, you can not specify anything at all - just insert the tag (include file="engine/modules/sitemap.php") - then the default settings will be used.

Sitemap Appearance and Style Classes

Optional change is provided appearance site maps, for this we open the style file (style.css) of our template and prescribe the classes described below.

List of sitemap CSS classes:

Sitemap_categories - element

RELATED ARTICLES