Setting up the DataLife Engine. General DLE Settings

Based on the DLE engine (DataLife Engine). I will describe the setup in great detail, trying not to miss anything; I think that setting up dle will turn into a long series of posts. In this series of posts, we will not only look at the setup in detail, but also figure out why each setup function is needed.

For posts dedicated to setting up the DLE engine, I will use the DataLife Engine v.9.4., or rather the demo version of this engine. This is enough for me to tell you about the settings and capabilities of DataLife Engine.

The first article will be devoted to the admin section: “ General script settings". You can find this section as follows: after going to the DLE (DataLife Engine) admin panel, which is located at site.ru/admin.php, you will see quick access to the main sections of the admin panel. Today we need the item " system setup" , and in it there is a section “ general script settings". There are, of course, other ways to get to this section, but in my opinion this is the easiest way.

So let's start setting up the dle engine, the first point is title. In the title write the name of your project, for example: Everything for beginner webmasters. Your title can sound anything, by default it is on the DLE engine, the site is called DataLife Engine, if we enter any other name, it will be changed. And it will form a title dle, which will be displayed in the browser tab, as well as on the search results page. Therefore, take the title seriously. Here, I think it's clear.

Well, home page, I think it's clear. Enter your domain name, for example: site.ru and that’s it.

Encoding used, by default, is windows-1251, which means that your resource supports the Russian language. If you have a demo version of the DataLife Engine, you don’t need to change anything here. If the CMS is purchased, then the encoding can be changed, for example, to UTF-8 and then your project will become multilingual, at this stage we will not consider the encoding in detail, I think it’s understandable if we don’t change your demo, even if it’s purchased, but the domain is located in the ru zone, to be honest, I don’t see the point in changing the encoding.

Next point: Description, in which we briefly describe the content of our project, for example: Everything about creating, setting up and promoting blogs or websites, etc., but no more than 200 characters. In theory, this description should be displayed in search engines, so take this seriously, and do not forget to include in the description the keywords by which your resource will be promoted in the future. It will look something like this in a Google search:

Next, Keywords(we enter the words separated by commas), also according to these words, search engines will pay attention to your page, the keywords should correspond as closely as possible to the direction of your website or blog, first you need to make a list of keywords and check the number of requests for these words. To check the number of requests, we use this page on the Internet http://wordstat.yandex.ru. We will not consider this in more detail at this stage, since this no longer relates to this topic of the post, but to optimization in search engines. Here you see for yourself what to write in this field, the keywords will be different for each.

Short name, here I think everything is clear. This name will be displayed in the speedbar module. You can, again, repeat the name of the project. So we've sorted out the names, let's continue. The speedbar module (aka breadcrumbs) looks like this:

Correction of time zones, serves to correct the time on the site. For example, your server is configured for Moscow time, but you live in a different time zone and want the time on the site to correspond to your time zone, this can be corrected in this column. How to fix it is all clear there, we write the hours in minutes, the current server time is also written in this column, you can navigate by this time.

In the column (human-readable URL), it is advisable to select “Yes”. It is needed so that your address is visually perceived by users, which has a good effect on the usability of your resource. To make it clearer, I will give examples of news with and without CNC, news with CNC dle: http://site. ru/addnews.html, without CNC: http://site.ru/index.php?do=addnews, that is, with CNC the visual perception of the link is much better than without it.

Then select CNC type, everything is in your hands here, but I don’t recommend choosing the third type as it increases the load on your server.

Handle invalid CNC URLs: Here I advise you to put “Yes”, since this option is useful for SEO, but you can not enable this option if you want. More details about what it is needed for are written in the settings, it’s quite clear.

Then select language used, since I have a demo version, I don’t have much choice, only one language, it’s Russian, but for the ru domain zone, this will be enough.

Next, default site template — is default, but you can choose another one. A separate article will be devoted to this topic, on how to install a template on DataLife Engine (DLE). Of course, we all want some kind of special, non-standard template, looking ahead, I will say that installing a template on dle is very simple. Download the template you like from the Internet or make your own, copy the template folder to the engine directory, into the templates folder, and if your resource is on a local server, restart it. And now the template will appear in the default site template selection column.

After choosing a template, go to two settings “ Enable WYSIWYG editor...“, in both cases I recommend choosing “Yes”, so using a visual editor it is much easier to edit news (articles) and comments than using BB codes. Although, it’s your choice, experiment and opt for convenience. DLE WYSIWYG editor is a visual editor.

This is what the editing panel looks like using BB codes.

This is what the editing panel looks like using DLE WYSIWYG.

Next comes a rather useful option: “ turn off the site“, this option transfers the resource to the offline state. If you think that your project is not yet ready to be seen by users, then enable this option. If everything is ready, then turn off the option and release the project to the network. You can also use this function when updating the structure or template of your resource. I note that this option is useful if your “experimental” is on hosting, and not on a local server, like mine.

Last option ( reason for shutdown) will be useful to those who take advantage of the site shutdown. The reason for the shutdown is already written in the text field, which you can edit to suit yourself or write your own reason.

That's it. You have taken the first step towards setting up DLE (DataLife Engine). Now all that remains is to save the general dle settings and wait for the next post about setting up the DLE engine.

Note: posts about setting up DLE (DataLife Engine) will be presented in this form, for better perception of the information received, so that you don’t end up with a mess in your head. Of course, it was possible to describe the entire setup in one article, something like this: select this here, put this here, write this there. But I want you to understand what each function does. There are too many settings and features in DLE for one post. I hope for your understanding.

The following changes were prepared and implemented:

1. Added the ability to log in to the site using social networks. This support is enabled in the script settings in the control panel. And setting up social networks directly is carried out in a special new section of the control panel: “Setting up social networks”. In this section, you can configure which social networks you want to support on your website, as well as specify the necessary parameters and keys for the operation of a specific social network. This section also provides detailed help on how to create applications on social networks for authorization. In total, six social networks are currently supported: Vkontakte, Odnoklassniki, Facebook, Yandex, Mail.ru, Google. Thus, your visitors can quickly log in to your site using their login and password on social networks, without having to go through the registration procedure with entering captchas, confirming E-mail, and so on.

text, which display the text enclosed in them if support for authorization using the VKontakte social network is enabled. And also the tag (vk_url)

text, which display the text enclosed in them if support for authorization using the Odnoklassniki social network is enabled. And also the tag (odnoklassniki_url), which displays a URL link to authorization in this social network. networks.

text display the text enclosed in them if support for authorization using the social network Facebook is enabled. And also the tag (facebook_url), which displays a URL link to authorization in this social network. networks.

text, which display the text enclosed in them if support for authorization using the Google social network is enabled. And also the tag (google_url), which displays a URL link to authorization in this social network. networks.

text, which display the text enclosed in them if support for authorization using the Mail.ru social network is enabled. And also the tag (mailru_url), which displays a URL link to authorization in this social network. networks.

text, which display the text enclosed in them if support for authorization using the Yandex network is enabled. And also the tag (yandex_url), which displays a URL link to authorization on a given network.

3. Added the ability to create when uploading images to the server not only thumbnail copies, but also medium-sized copies of the downloaded images. Thus, you can now create a small preview image, a medium thumbnail copy and the original image when uploading images.

4. Added the ability to insert images uploaded to news indicate in what form they should be inserted. Namely, enlarge them when you click on them to the original image, or insert them simply as images, without any links in them. 5. In the script settings in the script control panel, the time offset setting has been removed. Instead, a more convenient selection of the server time zone in which the script will work has been added. Using time zones is more convenient because... The transition to summer and winter time will be automatically made (for example, if the server is located in Europe and you have set the Moscow time zone, then you do not need to make settings twice a year). The correct time zone of your server will also be broadcast in RSS.

6. Added the possibility of personal selection each registered user of the time zone in which he is located. This feature allows site visitors to see for themselves the correct time of publication of articles and comments. For example, the server and administration of the site are located in Moscow, and the registered user is located in Krasnoyarsk, then this user can go to the site’s profile settings and select the Krasnoyarsk time zone, and after that he will see the date and time of news and comments in his Krasnoyarsk time, etc.

7. For the user profile editing template (userinfo.tpl) new tag added (timezones) which displays a list of available time zones in the system, and allows him to select his own time zone for his profile on the site.

8. Added possibility for polls, added to publications, display them not only when viewing full news, but also when viewing short news. To do this, in the short news template (shortstory.tpl) you can use tag (poll). The survey itself is also designed in the poll.tpl template

9. For short news output templates (shortstory.tpl) added the ability to use banner tags added in managing advertising materials in the admin panel. Thus, you can very flexibly display banners on the pages of your site together with tags (banner_x) and independently determine after which news on the page you want to display advertising.

10. For templates for displaying short and full news (shortstory.tpl and fullstory.tpl) new tags added text, which display text in them in the form of a link to add news to bookmarks on the site, and tags are also added text, which display the text in them in the form of a link to delete news from bookmarks on the site. These tags will allow you to more flexibly customize the design of your site, for those who want to abandon the general tag (favorites), which displays only one pre-programmed picture for the given action.

11. Added new global tags for templates: text, which display the text contained in them if the site is viewed using a smartphone, as well as tags text, which display the text enclosed in them if the site is viewed by the visitor not from a smartphone. These tags are global and can be used in all template files. Thus, you can flexibly customize the display of your website content, depending on the device used by the visitor, for example, manage the display of advertising for devices and much more.

12. Added new global tags for templates: text, which display the text contained in them if the site is viewed using a tablet, as well as tags text, which display the text enclosed in them if the site is viewed by the visitor not using a tablet. These tags are global and can be used in all template files. Thus, you can flexibly customize the display of your website content, depending on the device used by the visitor, for example, manage the display of advertising for devices and much more.

13. Added new global tags for templates: text, which display the text enclosed in them if the site is viewed using a desktop browser (desktop computers, laptops), as well as tags text, which display the text enclosed in them if the site is viewed by the visitor not using a desktop browser. These tags are global and can be used in all template files. Thus, you can flexibly customize the display of your website content, depending on the device used by the visitor, for example, manage the display of advertising for devices and much more.

14. Added the ability to specify static pages template files located not only in the root folder of the template, but also files located in subfolders of the template.

15. Added a feature in the cross-reference module assign for each keyword how many replacements of this word should be made on the page.

16. For full-text search on the site, a logical search mode has been added, which can significantly improve site search and the relevance of the information found for the search query. This innovation allows you to show the visitor the most suitable news, comments or static pages that match his request.

17. Improved processing algorithm already existing links on the page when replacing keywords from the cross-referencing module. Now the mandatory absence of HTML tags inside links is no longer required; replacement in them will not be made regardless of this.

18. Improved algorithm for finding and replacing keywords from the cross-references module, thanks to which it was possible to significantly increase the speed of the script with a large volume of links.

19. For cross reference control module In the admin panel of the script, the ability to mass set the keyword replacement area has been added, and the ability to mass set whether to take into account the case of letters or not has been added.

20. Added editing ability values of additional fields for the user’s profile, directly in the script’s admin panel in the user’s own profile settings section.

21. For a template for displaying information about a registered user on a website (login.tpl) added the ability to display the values of his additional fields that he filled in during registration or in his profile settings. To display additional profile fields, exactly the same tags are used as in profile templates (userinfo.tpl) and comment templates (comments.tpl).

22. The stationary ICQ field has been removed from the user profile database. This decision was made because this messenger has lost its relevance and the use of this field is insignificant, despite the fact that it takes up space in the database. In this case, if necessary, you can create this field as an additional field for your profile and use it if necessary on the site.

23. Added indication of the page number being viewed full news, in the meta title tag, if the news was divided into several pages.

24. Added the ability to the script settings purpose of the separator symbol for the "speedbar" module (breadcrumbs). This symbol will be used when displaying the navigation of this module, separating sections of the site. Thus, you can specify any custom separator, instead of the previously always used """. 25. Added the ability to the script settings assigning a separator symbol for the list of categories assigned to the news. This symbol will be used when displaying a list of categories when displaying news on the site, separating the assigned categories. Thus, you can specify any custom separator, instead of the previously always used """.

26. Added information output about third-party modules installed in the script control panel, in the left side panel for quick module navigation in the admin panel.

27. Redesigned keyword management for tag clouds, meta tags and additional values. fields of the cross-reference type. Now you can not only delete them in one click, but also edit them without deleting them; to do this, you need to double-click on the word you need. And also added automatic parsing of inserted words using Ctr-V, without the need to press Enter.

28. In the script control panel, added a button for quickly collapsing and expanding the sidebar. This innovation will be useful for users who have monitors with low screen resolutions to increase the working area.

29. Added automatic cache reset compressed CSS and JS files when editing these files in the control panel template editor.

31. Added support for apostrophes, for additional news fields that are of the "Use values as hyperlinks" type and for which secure mode has not been enabled. Thus, you can use, for example, words such as O'Brien, d'Artagnan, etc.

32. Added automatic generation of the CNC name for a category when it is created in the admin panel, if it has not been specified by the user. In this case, when creating this name, transliteration from the specified category name is applied.

33. When adding and editing categories in the script admin panel, added control of reserved CNC link names for categories so that users do not add names that are reserved in DLE for other needs. For example, you won't be able to add a root category named "catalog" because that name is used to organize directories on the site, but you can use that name for a subcategory where that name is no longer reserved, etc.

34. Added more convenient selection of categories when creating or editing additional news fields in the script control panel. 35. Added the ability to specify the number of days in the script settings, during which it is necessary to store script logs for the module “List of all actions performed in the script admin panel”. At the same time, for security purposes, the minimum number of days remains 30 days, so that an attacker cannot delete action logs, and the site administrator, if desired, can increase the required number of days, for example, to three months or a year, etc.

36. The Jquery library has been updated to the latest version v1.11.1

37. TinyMCE visual editor has been updated to the latest version.

38. Updated to the latest version of HTML5 player, which fixed some playback issues.

39. Problem fixed, in which managing script settings in the admin panel did not work when using smartphones and tablets.

40. Problem fixed, in which there was an incorrect check for the completeness of the additional. fields, if before a field with the "list" type, there was a mandatory field with a different type.

41. Problem fixed, in which if the search is repeated, and the user was not on the first page of the search results, he could receive an empty page if fewer news items were found in the new results. Now a new search returns the user to the first page of search results.

42. Problem fixed, in which the “speedbar” module (breadcrumbs) displayed the user’s nested location on a static page, while in fact he was on the main page of the site if the display of a static page by default for the main page of the site was enabled in the script settings.

43. Problem fixed, in which if the user edited a news item that was awaiting moderation on the site, he could not manage the pictures uploaded to this news, and if, while editing the news, he re-uploaded the pictures, they were not assigned to this news.

44. Problem fixed associated with incorrect operation of text tags when used in a custom tag news output (custom ...)

45. Previously discovered and reported minor errors in the script have been corrected.

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 log into the site under your client account.

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

You can discuss the release at

Hello friends. I spend almost all my time. Since most of my sites are built on CMS DLE, I have to work a lot with this engine. I said before that developers are not friendly with SEO, and in general we have never heard such a word, but it turned out to be even worse than it could have been. I even prepared a whole series of posts dedicated to the “sewing” of the people’s engine (see in the category).

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

The sitemap module for DLE, which I am about to present to you, meets all SEO requirements and is extremely easy to install.

SiteMap – HTML site map generation module for DLE

Original title: 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: Display an unordered list with links to all publications, categories and static pages.
Peculiarities: Visual embed code generator. Detailed configuration of the principle of displaying all elements of the site - news, categories, static pages - the number of elements displayed, the sorting principle and sorting order, displaying elements as a link or in 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 completely new sitemap version 2.0 has been released. We are raising the bar for the ease of use of our module to a new level. We (I hope you too) really liked the visual code generation system implemented in the system and we decided to implement it in the site map module. Now you don’t need to read manuals and descriptions of all functions and their meanings - just go to the admin panel, specify a few values and that’s it - the module is ready to use!

In addition to what has been said 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, is taken into account;
such a subtlety is provided - if anyone has been working with the DLE engine for a long time, they will remember 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 in this module - new publications are displayed with a url whose CNC type is selected in the admin panel, and old ones, respectively, with a CNC url of the old type.

Despite the appearance of a visual generator, I suggest 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 follow the sign? and are separated by &.

Example of insertion (displays a site map 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 this, the module will be available at http://site.ru/sitemap/

After any changes to parameters and their values, you must clear the cache in the admin panel.

Module parameters passed via tpl during insertion:

need_cats — list of category IDs separated by commas for display in the map
exc_cats — list of category ids, separated by commas, excluded from the map

need_news — list of article ids separated by commas for display in the map
exc_news — list of article ids, separated by commas, excluded from the map

It makes no sense to specify these parameters at the same time

need_static — list of static page ids separated by commas for display in the map
exc_static — list of id static pages, separated by commas, excluded from the map

It makes no sense to specify these parameters at the same time

cats_as_links — show category names as links (1 or 0)
show_static — display static pages (1 or 0) in the map

cats_sort — sorting field for the list of categories (field from the dle_category table)
cats_msort — sorting direction for the list of categories (ASC or DESC)
news_sort — sorting field for the list of articles (field from the dle_post table)
news_msort — sorting direction for the list of articles (ASC or DESC)
static_sort — sorting field for the list of static pages (field from the dle_static table)
static_msort — sorting direction for the list of static pages (ASC or DESC)

There are 2 options for sorting direction:
- ASC - ascending (alphabetical)
- DESC - Descending (in reverse order)
if the field and sort order are not specified, the specified category settings or standard DLE parameters are used

cats_limit — maximum number of subcategories displayed
news_limit — maximum number of articles displayed from a category
static_limit — maximum number of static pages displayed

Please note none of the above settings are required, you don’t have to specify anything at all - just insert a tag (include file="engine/modules/sitemap.php") - then the default settings will be used.

Sitemap Appearance and Style Classes

It is optionally possible to change the appearance of the site map; to do this, open the style file (style.css) of your template and write the classes described below.

List of CSS sitemap classes:

Sitemap_categories - element