Idioms intitle datalife engine control panel. Installing DLE. On which hosting can you install DLE?

DataLife Engine (DLE) is a multi-user news engine designed for organizing your own blogs and media on the Internet. Thanks to 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 websites 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 ease of use of this technology on the site. Thanks to the increased attention to the security of the script, the ease of working with it, as well as dynamic development, more than 70,000 portals have already spoken in favor of using DataLife Engine, successfully using it in their work. The engine is optimized for search engines, which will bring additional customers to your site.

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

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

Please note that this software is paid, and installation will be discussed using the demo version as an example.

Installing CMS DLE

To start installing DLE, you need to go to your 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 kit, for example here http://dle-news.ru/demo.html.

Go to the hosting control panel, select “File Manager”, then go to the www/domain_name directory. We delete the index.html file created by default when adding a domain, click the “Upload” button, select the CMS DLE archive and click 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 end up with something like this:

Next, we need to create a CMS DLE (DataLife Engine) database; to do 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 completing the steps described above, access your domain name in the browser, proceed to install CMS DLE (DataLife Engine) and click the “Start installation” button:

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

83.69.23*.*** domain name

The server's IP address can be viewed in the hosting control panel, Domain Names - Records entry:

domain_name.ru.

A (Internet v4 address)

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

Check the box “I accept the terms of the agreement” and continue the installation.

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

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

Database name: vh12345_dle

DB username: vh 12345_ admin

Password: the password you specified when creating the database

MySQL Server: Database Type column in the Databases section db01.site (see point 4) or

indicate in this field mysql.your_domain

The prefix is ​​set arbitrarily.

The data for accessing the control panel is to create an administrator account for your site; here we indicate the desired login/password and e-mail of the administrator.

Installation of CMS DLE (DataLife Engine) is complete.

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

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

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 a tag (odnoklassniki_url), which displays a URL link to authorization in this social network. networks.


text displays the text enclosed in them if support for authorization using the social network Facebook is enabled. And also a 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 a 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 a 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 in this network.

3. Added the ability to create, when uploading images to the server, not only small copies, but also medium-sized copies of the uploaded 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 indicate in what form to insert them when inserting pictures uploaded to news. 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 ability for each registered user to personally select 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), a new tag (timezones) has been added, which displays a list of available time zones in the system and allows you to select your own time zone for your profile on the site.

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

9. For short news output templates (shortstory.tpl), the ability to use banner tags added in managing advertising materials in the admin panel has been added. Thus, you can very flexibly display banners on the pages of your website 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 text tags have been added, which display the text in them as a link to add news to bookmarks on the site, and text tags have been added, which display the text in them in the form of a link, deleting 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 image for these actions.

11. Added new global tags for templates: text, which display the text enclosed in them if the site is viewed using a smartphone, as well as text tags, which display the text enclosed in them if the site is viewed by a 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 enclosed in them if the site is viewed using a tablet, as well as text tags, which display the text enclosed in them if the site is viewed by a 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 text tags, which display the text enclosed in them if the site is viewed by a 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 template files for static pages that are located not only in the root folder of the template, but also files located in subfolders of the template.

15. Added the ability in the cross-references module to assign for each keyword how many replacements of a given 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 the search on the site 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. The algorithm for processing existing links on the page when replacing keywords from the cross-references module has been improved. Now the mandatory absence of HTML tags inside links is no longer required; replacement in them will not be made regardless of this.

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

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

20. Added the ability to edit the 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 the template for displaying information about a registered user on the site (login.tpl), the ability to display the values ​​of his additional fields that he filled in during registration or in his profile settings has been added. 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. However, 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 of the full news being viewed in the title meta tag, if the news was divided into several pages.

24. Added the ability to assign a separator character to the script settings 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 "" character.25. In the script settings, the ability to assign a separator character has been added to the list of categories assigned to 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 delimiter, instead of the previously always used """.

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

27. Keyword management for tag clouds, meta tags and additional values ​​has been redesigned. 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, a button has been added 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 reset of the cache of 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 have the “Use values ​​as hyperlinks” type, and for which safe mode was not 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 admin panel of the script, control of reserved names of CNC links for categories has been added 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 a more convenient selection of categories when creating or editing additional news fields in the script control panel.35. In the script settings, the ability to specify the number of days during which it is necessary to store script logs has been added 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 the HTML5 player, in which some errors with playback have been corrected.

39. Fixed a problem where managing script settings in the admin panel did not work when using smartphones and tablets.

40. Fixed a problem in which an incorrect check for the fullness of the add-on occurred. fields, if before a field with the "list" type, there was a mandatory field with a different type.

41. Fixed an issue where if a search was repeated and the user was not on the first page of the search results, he could receive a blank 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. Fixed a problem where the "speedbar" module (breadcrumbs) displayed the user's nested location on a static page, but 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. Fixed a problem in which if a user edited a news item that was awaiting moderation on the site, he could not manage the pictures uploaded to this news, and if, when editing a news item, he uploaded pictures again, they were not assigned to this news item.

44. Fixed a problem related to the 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

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 “system settings” item , 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 the title (title dle). 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, the home page, I think it’s clear. Enter your domain name, for example: site.ru and that’s it.

The default encoding used 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 item: 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 much as possible to the direction of your site 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.

A short title, 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 we select the CNC type, everything is in your hands here, but I do not recommend choosing the third type as it increases the load on your server.

Handle invalid CNC URLs: Here I recommend setting “Yes”, as this option is useful for SEO, but you can leave this option off if you wish. More details about what it is needed for are written in the settings, it’s quite clear.

Then we select the language to use, since I have a demo version, my choice is not large, only one language is Russian, but for the ru domain zone, this will be enough.

Next, the 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 selecting 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 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.

The last option (reason for shutdown) will be useful for 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 all. 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.

Go to edit the article, click the button with the image of the folder (upload files to the server).

A window will open with three tabs at the top: Uploading files, uploaded for publication, shared folder. By default, the first tab will be opened, on which we will be asked to download files from the computer (by clicking on the appropriate button), or indicate the url address of this file (to download it from the server without the need to download it to your computer).

It is also worth noting another interesting option for uploading from the uploads/files folder, this way you can move your files to another folder (/uploads/posts/).

Below are some settings that we can change directly from this window; they duplicate the main image settings located in the admin panel () and by default have the parameters specified there. However, using these settings gives us certain advantages, since it allows us to set separate settings for each group of thumbnails.

After downloading pictures via your computer, the downloaded tab for publication opens. Here you can see the downloaded pictures, their size, select them using the checkbox below and click publish selected, select all or delete files. Just remember to choose left, right, center, or no alignment at all. Please note that these are not all the settings and in this way, by default, reduced thumbnails of pictures will be inserted, and large pictures will open when you click on them. In order to insert a picture in its natural size into an article, hover your mouse and click on the picture itself, the following options will appear below. Click Original Image and Insert Image.

The engine uploads all pictures to the /uploads/posts/ folder, we can say that this is a folder specifically for pictures, a subfolder is created in it, the name of which will be the date the pictures were uploaded, and in this folder there will be full-size pictures and a folder with their reduced copies thumbs.

Other types of files are uploaded similarly (if they are allowed in the settings), except for pictures, dle automatically redirects them to the uploads/files folder, only they will be displayed as attachments (attachments) and users will see a link to download this file.

By the way, it is important to mention one more nuance: both pictures and files are strictly tied to one specific article, and when it is deleted, all accompanying pictures and files will be deleted. Even if you upload the same file twice for different articles, there will be two files with different names assigned by the system.

Now it’s time to consider what parameters we can set for pictures and files from the administrative panel.

Go to (Home - list of all sections - system settings - Setting up work with images)

And look at the settings (we have already seen some in the file and image upload window)

  • Maximum allowed dimensions of the original image – DLE can automatically reduce the original image size to the specified size. This can be achieved in two ways, the first is to specify the required size of any side, the second is to set the width and height of the original image in the width x height format, 0 – the image size does not change.
  • Default settings for the original image - i.e. on which side will the image dimensions be checked (and, accordingly, reduced) - along the largest side, along the width, along the height
  • The maximum permissible weight of images uploaded for publications - what is the maximum weight of an image in kilobytes that is allowed for uploading.
  • Automatic deletion of images – after how many days images uploaded to the site for an article will be deleted if it is not published. If nothing is specified, images will not be deleted.
  • Size of a reduced copy of the uploaded image - there are two options for setting the size: specify the required size of any side, the second - set the width and height in the form width x height Default parameters for creating a small copy of an image - on which side the reduced copy of the image will be resized (the largest side, width, height) Compression quality.jpg of the image - in what quality the picture will be copied to the server Maximum permissible weight of avatars uploaded by the user in the profile - how many kilobytes will be the permissible weight of avatars. 0 - the restriction is removed, 1 - a ban on uploading avatars.

Watermark settings

  • Allow watermarking - whether to add watermarks to the image
  • Minimum size for applying a watermark - for images with a side smaller than this size, the watermark will not be applied
Watermarking in DLE

How to set a watermark? Standard watermarks with the DLE logo are located in the dleimages folder at your_site.ru/templates/your_template_name/dleimages. Here we need to replace the two files watermark_dark.png and watermark_light.png with our own pictures, previously drawn in a text editor, for example Adobe Photoshop. They will look better if you make them translucent. You can make them the same size as the default watermarks, or set your own size, it is only important to follow the following rules: the size of the watermark should not exceed the size of the picture and both of our newly created watermarks should be the same size.

Settings for displaying enlarged images from thumbnails
  • Automatic darkening of the site when showing the original image - will the background of the site be darkened when showing a large image (when you click on the thumbnail)
  • View of the original image when enlarged from a reduced copy - the original image is shown in the browser as a modal window (using the Highslide js plugin, which is included in DLE by default, it exists separately from our engine, is distributed free of charge, it is a kind of analogue of lightbox), here You can set some visual effects for this image (shadow, frame, rounded edges).
  • Gallery mode when viewing thumbnail images – yes/no (on or off) when viewing large images from thumbnail copies, navigation will be displayed on the images, there will be a slideshow mode.

Sometimes you may encounter a problem that the gallery mode in DLE does not work - the navigation bar does not appear on the pop-up image. The fact is that the highslide.js script is connected automatically (you can find it if you open the source code in the browser), in addition, some of its parameters must be initialized, they are given below. Check that this is present in your page code.

JavaScript

hs.graphicsDir = "/engine/classes/highslide/graphics/"; hs.outlineType = "rounded-white"; hs.numberOfImagesToPreload = 0; hs.showCredits = false; hs.lang = ( loadingText: "Loading...", playTitle: "View slideshow (space)", pauseTitle: "Pause", previousTitle: "Previous image", nextTitle: "Next image", moveTitle: "Move", closeTitle: "Close (Esc)", fullExpandTitle: "Expand to full size", restoreTitle: "Click to close image, press and hold to move", focusTitle: "Focus", loadingTitle: "Click to cancel" ); hs.align = "center"; hs.transitions = ["expand", "crossfade"]; hs.addSlideshow(( interval: 4000, repeat: false, useControls: true, fixedControls: "fit", overlayOptions: ( opacity: .75, position: "bottom center", hideOnMouseOut: true ) ));

hs. graphicsDir = "/engine/classes/highslide/graphics/" ;

hs. outlineType = "rounded-white" ; hs. numberOfImagesToPreload = 0 ;

hs. showCredits = false ;

hs. lang,

playTitle : "View slideshow (space)" , pauseTitle : "Pause" , previousTitle : "Previous image" ,

nextTitle : "Next image" , moveTitle : "Move" , closeTitle : "Close (Esc)" ,

fullExpandTitle : "Expand to full size" ,

restoreTitle : "Click to close image, long press to move" ,

focusTitle: : "Click to cancel" ) ;

hs. align = "center" ; hs. transitions = [ "expand" , "crossfade" ] ;

hs. addSlideshow (( interval : 4000 , repeat : false , useControls : true , fixedControls : "fit" ,

overlayOptions: (opacity: 75, position: "bottom center", hideOnMouseOut: true)));

The same source code should also contain a function responsible for displaying images in gallery and slideshow mode, namely: hs.addSlideshow.

If we delve into the engine files, we will find that the output of these parameters is determined by the following lines of code in the index.php file, located at the root of the site.

if (strpos ($tpl->result["content"], "hs.expand") !== false or strpos ($tpl->copy_template, "hs.expand") !== false) ( if ($config ["thumb_dimming"]) $dimming = "hs.dimmingOpacity = 0.60;"; else $dimming = ""; if ($config["thumb_gallery"] AND ($dle_module == "showfull" OR $dle_module == "static ")) ( $gallery = " hs.align = "center"; hs.transitions = ["expand", "crossfade"]; hs.addSlideshow(( interval: 4000, repeat: false, useControls: true, fixedControls: " fit", overlayOptions: ( opacity: .75, position: "bottom center", hideOnMouseOut: true ));"; ) else ( $gallery = "";

if (strpos ($tpl -> result [ "content" ] , "hs.expand" ) !== false or strpos ($tpl -> copy_template , "hs.expand" ) !== false ) (

if ($config["thumb_dimming"]) $dimming = "hs.dimmingOpacity = 0.60;" ; else $ dimming = "" ;

if ($ config [ "thumb_gallery" ] AND ($ dle_module == "showfull" OR $ dle_module == "static" ) ) (

$gallery="

hs.align = "center";

hs.transitions = ["expand", "crossfade"];

hs.addSlideshow((

interval: 4000,

repeat: false,

useControls: true,

fixedControls: "fit",

overlayOptions: (

opacity: .75,

  • hs.numberPosition - shows the number of the current image in the sequence (for example, Image 1 of 5) Can take values ​​'heading' - displayed at the top, caption - displayed at the bottom. The exact string is specified in the hs.lang object (it contains the localization strings). In the same index.php file we find the line hs.lang = ( and add a parameter to the end - number: ‘Image %1 from %2’ (don’t forget to put a comma after the previous parameter);
  • hs.addSlideShow - a function that sets parameters for the gallery mode (pictures are grouped and have a common navigation bar)
  • interval - the number of milliseconds that each slide will be shown. (default 4000)
  • repeat - repetition (start from the first slide after moving to the last) (default false )
  • useControls - allow Highslide to create a slideshow control panel (true or false)
  • fixedControls - if true, the control panel is fixed, the controls are in the same position while viewing all pictures and the user can view images using the Next button without moving the mouse (true or false)
  • overlayOptions - overlay options for the control panel (object)
  • opacity - panel transparency (default: 75),
  • position - vertical position of the control panel (top, middle, bottom) and horizontal (left, center, right) (default ‘bottom center’)
  • hideOnMouseOut - hide the control panel when the mouse is not in the picture (default true)
  • Next, we change the appearance of the navigation bar. To do this, open the engine.css file (templates/Default/style/engine.css, instead of Default, substitute the name of your template if necessary). We look for lines 423, 432, 447 (.highslide-controls, .highslide-controls ul, .highslide- controls a, respectively) and replace controlbar-black-border.gif (black control panel by default) in the background url with controlbar-white. gif - white control panel.

    Ways to set a thumbnail for an article

    You can set a thumbnail for an article simply by inserting a picture at the beginning of the article text. However, you need to make sure that everything is the same, the same styles are applied, and if, for example, you need to enclose a thumbnail in a link to an article, you will have to specify the article’s address manually.

    Previously, it was possible to list the types of files allowed for downloading; now (in new versions) this feature has been moved to the Setting up user groups section and is set separately for each user group. Read more in the article Managing DLE Users.

    Maximum number of files during bulk download - how many files are allowed to be selected and queued for download at the same time

    Enable support for resuming files when downloading – whether resuming files is allowed when the connection is lost

    Enable file download counter – display information: how many people have downloaded this file.

    Well, I guess that's all! Thank you for reading to the end. See you again!
    As usual, watch the video

    DLE or DataLife Engine is a paid CMS for managing the content of your website. CMS has a powerful system for managing news, publications, articles, users and is designed for creating information portals and blogs. Thanks to many built-in functions and the use of advanced AJAX technology in the CMS, your site will consume less server resources even with a large number of visitors. In this guide, you will learn how to install DLE on Hostinger.

    Before you start this guide, you will need the following:

    • Access to your hosting control panel
    How to Install DLE on Hostinger

    Before you start installing DLE, you need to perform these steps:

    Step 1 - Download DLE installation files

    Open the upload folder in your FTP client and upload all the files in the folder to your hosting account in the public_html directory.

    THE NOTE! In this tutorial, we'll use FileZilla to upload files, but you can use any FTP client you're comfortable with.

    Step 3 - Setting File Permissions

    DLE installation is automatic; all you need to do is set the appropriate rights for several separate folders and files that you previously uploaded to your hosting account.

  • First, set write permissions for the templates folder and all its subfolders. To do this, right-click on the templates folder in the FileZilla interface and select the File Attributes… option.
  • Next, in the window that appears, enter 777 in the Numeric value to change write permissions, check the box next to Redirect to subdirectories and check Apply to directories only.
  • Next, you need to change the permissions for all files in the templates folder, but with rights 666. To do this, open the attributes of the templates folder again and set the Numeric value to 666, check the box next to Redirect to subdirectories → Apply only to files.
  • Carry out identical actions with the backup, uploads folders, as well as for all the folders located inside them. Next for the folders /engine/data/,/engine/cache/, /engine/cache/system/. For all specified directories, set write permissions to 777.
  • Now you can start installing DLE.
  • Step 4 - Installing DLE on Hostinger

    To begin installation, enter your domain name in your browser. If the installation window does not exit automatically, append install.php to your domain name. Eg, your-domain.ru/install.php.

  • If everything is done correctly, you will see the DataLife Engine Installation Wizard window. Click the Start installation button.
  • Next, accept the user agreement by checking the box next to I accept this agreement. To continue the installation, click Continue.
  • In the next window, check that your server meets the necessary requirements and click Continue.
  • Next, check that the file permissions you previously set are correct. If everything is correct, click Continue again.
  • In the new window, you need to fill in your database details and details for your DLE site administrator account.
    • Site URL – the address of your site

    Data for accessing the MySQL server.

    • MySQL Server – MySQL server for your hosting database. If you are a Hostinger user, you can find the necessary information in the Databases → MySQL Databases section.
    • Database Name – The name of your MySQL database.
    • Username – the name of the user assigned to your database.
    • Password – the password for your database user account.
    • Prefix – prefix of MySQL database tables. You can leave it unchanged.
    • Database Engine – It is recommended to leave the default value. InnoDB.
    • 4 bytes UTF – when this option is enabled, DLE will save additional information in the database. This option may affect the performance of your site.

    Data for accessing the control panel.

    Enter your credentials to access your site's control panel. Enter your real email address, it will be used to restore access to the administrator account.

    Additional settings.

    Enable CNC support – enable human-readable URL. When this option is enabled, the title of the article will be displayed in the URL. This feature is useful for SEO optimization.

  • To avoid having to run the installation or update again, delete the install.php file and the upgrade folder from your site directory. Click the Continue button.
  • Congratulations, the installation of DLE for your website on Hostinger was successful.

    Conclusion

    After finishing this guide, you learned how to install DLE on your hosting. Installing DLE is a fairly easy process if you have followed our step-by-step guide carefully. Despite the abundance of CMS today, DLE has its own characteristics and good performance.