Immoral datalife engine printable version. DataLife Engine v.8.2 Final Release has been released

21.10.2021

System

Free third-party module for creating photo albums in the DataLife Engine system. The system will be adapted to work with a large amount of graphic information and will provide your site with a decent display of a wide variety of images. Users of your site will get real pleasure from viewing photo albums, will be able to express an opinion about photos, vote for their favorite photo, mark friends and acquaintances. And the installation of the module for you will be as comfortable and safe as possible for your site.

Simple and safe installation.
- New methods of displaying information and photos, support for formats.
- Maximum number of templates is the best photo album look.
- Multi-categories, with access settings for adding photos and viewing an album.
- Admin control center for the module, as well as a separate control panel for administrators and moderators right on the site.
- Marks on photos: just text or user.
- Caching database queries, caching graphics and other dynamic information.
- Adding photos in multiplayer mode, adding photos by archive, as well as bulk upload.
- Ajax technologies.
- Operating files are extracted from the system.
- Systems of access levels for groups and users.
- RSS feeds: unlimited number of feeds of photos, albums, tags.
- Creation of additional fields: from regular test to file upload.
- Storage of configuration data in the database.
- The system of moderators.
- The system is easily reconfigurable to other modules, such as a bulletin board.
- Photo search functions, tags, rating of photos.
- Support for HighSlide and other widgets.
- Photo effects.
- Setting the quality of the issued photos.
- Rich "usability".
- Editing of their photos and their comments by users.

Development was carried out within six months, faster than the previous version. In this version, the developer tried to fulfill the wishes of his clients as accurately as possible. For example, a great feature has been added to compress photos on upload. Now your photo album has learned to control the amount of graphics even better. The internal system of the module itself has not changed at all, but significant changes have taken place. And these changes are in the field of graphics processing and output of pages of the photo album. Firstly, the cache of some pages of the module was canceled, but nobody canceled the cache of the elements of this page, secondly, the most serious change is that the operating files were taken out of the system, this reduced the load, and thirdly, the number of templates was reduced. The module is becoming more and more adapted to a large number of photographs, and can be the foundation of such sites as a website for a photographer, a site about children's pictures and masterpieces of art.

Well, now let's try to figure out the new one.

1. Compress photos in any download mode.

Now in any mode of uploading photos, you can set the parameters for compressing photos. This saves space on the server and relieves the program from unnecessary load. The number of photos in your photo album can grow dramatically if space on your server is severely limited.

2. Editing your own comments and photos.

With each version, the photo album is getting closer to the average user: the user can now edit his comments, edit his photos. This function can be disabled in the module settings.

3. Display of the photo album icon.

Among the most anticipated innovations are the icons for albums and categories. For each album, a random icon will be displayed, or the one that is set as the default. The function can be disabled. Now you can easily make your photo album look like in "VKontakte". In the admin panel in the list of albums, their icon, set as by default, is now also displayed.

4. Updated template editor.

Added information about tags to the module template editor.

5. Ability for developers to add new fields to presets and language packs.

Previously, it was not convenient for every developer to add new language settings or settings, it is long and dreary. In the new version of photo albums, this is all automated, but before adding new parameters, you will have to pass a small test that asserts that you understand and understand the program code.

6. Moderation of added photos.

After adding photos, they are sent for moderation. For which groups to enable photo moderation, you can specify in the module settings.

7. Trash or hidden photos.

Photos can now be hidden or "sent to the trash". After that, all hidden photos can be deleted at once in the admin panel, or restored. Photos disappear from photo albums, tapes, and other photo outputs.

8. Publication after a certain date.

At the time of adding photos, you can now specify the date after which the photos will be available for viewing. It will be possible to publish future photos from the admin panel, individually or all at once.

9. Improved the journal in the admin center.

The review of the journal has been revised. Added the ability to delete the voting log-record, however, as well as any other records. As well as clearing the log completely.

10. New bulk loader.

The new bulk bootloader is nicer to look at and has more functionality than its predecessor.

11. Added the ability to specify user groups who can add photos to this album.

In addition to the rights to view the photo album, it is now possible to specify a list of user groups that can add to this album.

12. Removed code from templates, added new tags.

In order not to overload the processor of your server, the code was removed from the templates photo.tpl, photoid.tpl.

13. Display of comments of a certain user.

Everything is simple here, now you can see all comments to photos for a specific user. And, accordingly, remove them at once.

14. Display of the number of comments in the profile.

The user profile now displays the number of comments left on photos, as well as a link to all these comments.

15. When viewing the latest comments, it is indicated to which photo the comment was added.

When viewing the latest photos, it became possible to see which photo this comment was added to. The name of the photo and a link to it are displayed.

16. The number of templates has been reduced.

In order for users to easily and quickly edit module templates, some of them have been removed altogether. But their functionality was assigned to other templates. For example, the ajax add comment form and the regular form are now one template, just a new tag is added.

17. Recalculation of statistics.

In the admin panel, among the commands for clearing the cache, updating the preview of photos, checking the photo album, another command has been added - this is the recalculation of statistics. If the photo album is mistaken due to a software error, in the number of photos in the album, you can help the module and correct this mistake.

18. Counting the number of photo downloads.

The number of photo uploads is now counted.

19. SEO gadgets for photos and albums.

Added (alt) tag for photos, added filling of meta tags for album pages. Description and keywords are generated automatically. It is enough to fill in the description and title of the photo album.

20. Caching photos by the browser.

In order to prevent the user's browser from creating an additional load on the server, caching of photos by the browser has been added.

21. Removed support for specifying preview photos and storing photos remotely.

These functions have outlived theirs and due to the loss of popularity among users of photo albums, they were removed.

22. Mass movement of photos.

Turn your eyes to bulk photo manipulation. Click on the "checkmark" next to the preview of the photo or on many photos at once. A drop-down list with possible actions will become available under all photos: delete, hide all photos, send for moderation, move to another photo album. You can select all the previewed photos at once.

23. Possibility of specifying text mark and user mark.

When creating a mark, you can specify which type this mark belongs to: user or plain text. If the text - then the link will be to the output of all photos with this text label, if the user - then there will be a link to the user profile.

24. Some requests have been improved.

25. The tag cloud is displayed on the main page.

The tag cloud is displayed on the pages of the photo album.

26. Custom sorting of photos.

Added custom sorting of photos, the most diverse, ascending and descending, by rating and by date of addition, etc. If the user chooses to sort, then it is saved. And the information is displayed that a custom sorting is used, among this information there is a link to reset the sorting altogether.

27. Instead of the date of adding the photo: today, tomorrow or the day after tomorrow.

The mechanism of replacing the date of addition with the names of days has been improved. The "apple" is removed, but with the help of tags, you can easily display the picture "new photo".

28. Added support for 404 code.

30. Now you can specify which groups have access to a certain type of uploading photos.

For each group, it is now possible to differentiate which type of photo upload the group can use.

Now the archive with photos can be added associatively. The structure of the archive will be fully displayed in the photo albums. Photo Album will create albums named after the folder containing the photos. Folders can be nested many times, just like albums.

33. Added support for GIF-animation.

34. Fixed minor bugs and shortcomings.

Download for DataLife Engine 9.2:

Download for DataLife Engine 9.2 UTF: You cannot download files from our server

Download for DataLife Engine 7.0-9.0: You cannot download files from our server

Download for DataLife Engine 7.0-9.0 UTF: You cannot download files from our server

If you find it difficult to choose the version of the module for your system, write to technical support, they will help you.

The following changes were prepared and implemented:

1. Added the ability to upload images to the server for comments published on the site. This feature is enabled and configured in the group settings. For each user group, you can enable or disable the uploading of images for comments. Also, for each group, you can set various separate parameters for uploaded images, for example, the maximum number of uploaded images for comments, their size and weight, etc. When uploading images to comments, a simplified form of uploading comments is available to the user, and the images are uploaded according to the parameters specified in the group settings. In this case, the user is able to manage their 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 storage type to use. You can choose to use either InnoDB or MyISAM... When choosing an engine, we recommend that you 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. site "directory", it is recommended to use MyISAM type, it is faster when fetching from the database. If the site plans to actively discuss something with a large number of users, then it is recommended to use InnoDB type of. For most sites, InnoDB will be the best choice, because it scales more easily in the future. The choice of the database engine is available only if your server has MySQL version 5.6.4 or higher. 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, the 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 displayed in the player, for this, the following format is used in the video insert tag: , the same can be set for all files if a playlist of files is used, added with a comma. 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 on Youtube. This way you can organize mixed playlists including your videos 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 insert tag: ... You can see an example of the display in the screenshot above.

8. For the audio player, added the ability add links to play streaming audio. Thus, you can set and display playlists for listening to radio stations on your site.

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

10. Improved the procedure for inserting video and audio materials in editors. When adding a video, you can immediately create playlists, and you can also 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 DataLife Engine. The name of the new editor is FroalaEditor. This editor has an easy and intuitive interface (in our opinion, the best interface) for creating and editing content, the HTML code it generates is one of the cleanest and has practically nothing superfluous, has a relatively low weight and has a fast rendering of the editor on the page.

12. Added a new type for additional fields of publications:"Downloadable Image Gallery". When creating this type of field, 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 website, the image can be uploaded in one click. When this field is displayed on the site, the images will be grouped into a gallery of images, which can also be flipped among themselves when viewed, if small copies have been created for the images.

13. For additional fields of type"Downloadable image" and "Downloadable file", added automatic prohibition on 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 news.

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

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

16. Added the ability to view documents online, uploaded to the site via the DataLife Engine script. To do this, the following tags have been added to the template for outputting uploaded files (attachment.tpl): (online-view-link) which outputs the link url to view the document online in the browser, as well as the tags text that output the enclosed text if the loaded document is in a format that can be viewed. The following document types 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 Microsoft or Adobe programs installed.

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

18. Added the ability to set a description of images (alt attribute) when bulk inserting images into a news item. To do this, you need to select the images you want, 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 inserted.

19. Added automatic reset of Zend OPCache cache when changing site settings. Thus, with this caching 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 view of displaying the list of categories has been changed. Now all subcategories are shown collapsed, and can be opened directly if necessary for a specific 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 "Additional" tab, you can see the number of subscribers and unsubscribe them from comments to 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 posting a comment, even when the comment is being moderated.

23. In the user profile on the site, added the ability unsubscribe from signed 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, added the ability to automatically subscribe to receive notifications of new comments that are added to the news of which he is the author. 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 the checkbox, in the template userinfo.tpl added use of new tag (news-subscribe).

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

26. Added support for PHP Memcached extension. The DLE script automatically detects which PHP extension is installed, Memcache or Memcached on the server, and, depending on this, uses this or that 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 administration panel, in the section for editing publications, to the list of bulk actions on publications, added the ability to add categories to publications. Unlike the existing item "Change categories", item "Add category", allows you to massively assign new selected categories to publications, without changing the 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 write all the required publication IDs 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 write all the numbers of the pages you need separated by commas.

30. Added the ability to unsubscribe site users from mailing letters, which are sent from the "Sending messages" section of the admin panel. To do this, when sending letters, you can set either in the template or directly in the message text tag (% unsubscribe%), which displays the URL in the sent letter to unsubscribe from receiving the newsletter for the user. When clicking on this link, the status "Do not receive letters from the site" is set for the user profile. 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 the server getting into spam filters, always take into account the status that the user has set in his profile when sending messages.

31. Added auto-add for all external links, which are published in news and comments, attribute rel containing 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 the course of time, the publication also loses its popularity, and if it is not read often, then it is not advisable to create and control the cache constantly for it. If little news is published on your site, then you can increase the number of days during which to cache, if a lot, then decrease it. In any case, we do not recommend setting the cache time to less than 30 days. Use a small number of days only if there are problems with free space on the server's hard disk, or if you publish a very large amount of news per month. But for those who have a little news on the site, we recommend increasing this value.

33. In the admin panel, in the section for editing users, added the ability quick transfer of all publications from one user to another. To do this, you need to click on the number of user's publications, select the transfer of publications to another user, and indicate 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 his publications to another user.

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

35. In the admin panel, in the section for editing users, added the ability quick recalculation of the number of comments from the user. To do this, you need to click on the number of user comments and select the recalculation of comments in the menu. This option will be useful if mass manipulations with comments were made, or adding to the database bypassing the script.

36. Improved performance of news display when using sorting by rating and views. Also, the performance of displaying comments using rating sorting has been improved.

37. Improved the system for recording the number of user comments in his profile statistics. When news is massively deleted, users' comments are automatically recounted as well. This eliminates the need for periodic recalculation of statistics.

38. Optimized 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 editor TinyMCE to the current version.

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

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

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

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

45. Fixed problem whereby the tags text and text for the main page did not work correctly if the display of the static page on the main page was enabled in the script settings.

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

47. Fixed a problem in which it was impossible to enter the correct answer to the "Question-Answer" system if the user replies to the comment, and does not add a new one.

48. Minor errors in the script detected and announced earlier have been fixed.

Information for downloading the script for clients:

Attention important information for those who first install the script on a new domain:

/Documentation/upgrade.html
You must activate your copy only on the domain or subdomain on which you will use the script in the future, and in no case activate the copy on test domains, after activation your key will be blocked exactly for the domain on which it was activated. To activate the script, in the admin panel of the script, enter your activation key, which you can see in your profile on this site.

Attention important information for those who update the old version of the script to the new one:

Follow the instructions for updating the script in the distribution archive in the file /Documentation/upgrade.html
When updating a database to a new version, the update script makes complex MySQL queries that change the structure of tables. On large databases, such operations are very resource-intensive, and may take several minutes to complete, and if they cannot be performed through a PHP script, you will need SSH access to the server to execute these requests. Before each such request, the update script will show you this request, save it, so that if it is impossible to execute it through the script, you can execute it via SSH access.
Due to the fact that new versions of the script contain changes in the structure of the database, it is strongly recommended to disable the connection of third-party modules in the template files before updating, otherwise you may see errors on the MySQL website after the update.

Initially, the materials of the article can be sent to the editorial office of the journal by e-mail [email protected] in a form convenient for reviewers to read (tables and figures with signatures in the text of the article, references to literature - in a separate file). But the authors should take into account that if the editorial board makes a decision to publish it, the materials of the article must be completely brought to a form that corresponds to the "Rules for the design of articles" given below.

RULES FOR REGISTRATION OF ARTICLES

The volume of the article should not exceed 35-37 thousand characters with spaces (about 20 numbered A4 pages with a font size of 14 and one and a half line spacing, including text, bibliography, tables, figure captions), the number of figures - no more than 7. For a review article may be increased to 30 pages with no more than 12 figures. A letter to the editor can contain up to 5 pages with no more than 2 figures. Articles are accepted both in Russian and in English. Articles in Russian must be accompanied by an English translation of the title of the article and the special terms and phrases used in the article.

The text should be clear, not difficult to read (font size - 14 points, line spacing - one and a half, A4 page format, one column, left margins - at least 30 mm, top and bottom - at least 20 mm).

On the first page, articles are printed (see. "Interactive 1st Page Layout"):

UDC (see http://www.teacode.com/online/udc/);
article title;
initials, surnames of the authors (indicating the academic degree of the author after the surname, for example: A.I. Ivanov, Doctor of Technical Sciences; I.A.Petrov, Candidate of Physical and Mathematical Sciences); students must show their status (student, graduate student);
full names of organizations (each - from the red line), names of cities and states (except Russia) where these organizations are located (in the same order in which the authors are presented; the assignment of authors to the corresponding organizations is marked with asterisks above after the names of the authors and before the name of the organization );
email address (E-mail);
Received by the Editors......... (date to be affixed by the editors)
short annotation (no more than 14 lines);
"Keywords: "(should, helping search engines, link the material of articles both to the corresponding large sections of optics, and to special areas of research and development, typed in italics);
"OCIS codes:"

(see http://www.opticsinfobase.org/submit/ocis/ or Optical Journal, 2000, volume 67, no. 10, pp. 90-103); codes should be listed in order of importance.

The title and abstract of the article should not contain undeciphered abbreviations (abbreviations), even if they are generally accepted, and references to literature.

Footnotes (footnotes) in the text should be consecutively numbered, they should be placed below the line at the bottom of the page to which they refer.

References entitled "Literature", tables and figure captions are printed on separate sheets.

Detailed mathematical calculations, programs, etc., necessary for understanding the article material. are given in the Appendix, placed either at the end of the article, or (in case of an abnormally large volume) at the end of the electronic version of the article on the journal's website.

Figures are not inserted into the text: they are attached separately

Typing

Throughout the article, it is necessary to follow the uniform principle of using conventional letter symbols and symbols with their obligatory explanation at the first use in a text or formula. It is not allowed to use the same symbols or letters to designate different physical and / or mathematical quantities. In the text:

Abbreviations of words of the Latin alphabet, always used in superscripts and subscripts, should be typed directly without a period.
All letters of the Greek alphabet should be typed in roman type.
Abbreviations made up of capital letters of the Russian or Latin alphabets should be typed directly.
Type vector values in straight bold type without arrows at the top.
Type mathematical symbols like rot, div, lg, lim, exp, sin, etc. directly.
Chemical elements and formulas of chemical compounds should be typed in roman type.
In all other cases, not listed above, the letters of the Latin alphabet should be typed in italics.

Formulas should not have more than two "floors". One should use, for example, exp (- NS) instead of e - NS, and also use the forward slash when writing fractions, separating, if necessary, using parentheses, the numerator and denominator or the entire fraction as a whole from other terms of the formula. Do not use the multiplication sign in formulas. The symbol "×" should only be used to denote a vector product, in a combination of numbers like 5 × 10 4, to denote the multiplicity of magnification (2 ×), when indicating the size (2 × 2), as well as in the case of breaking the formula during transfer. Use the “·” symbol only to denote the dot product of vectors, as well as in chemical formulas (CuSO 4 · 5H 2 O). Cyrillic do not use in formulas!

Do not insert designations of units of physical quantities into formulas! Complex dimensions for the digital value of a physical quantity should be written using a slash instead of negative exponents, and without using the multiplication sign.

Continuous numbering is used for basic formulas. Formulas with a number must be written on a separate line. Formulas and expressions typed using special editors are also written in a separate line. Formulas in the text, i.e. inside a paragraph, should be typed in text mode... When typing a formula, do not use Formula and Text modes at the same time.

The following formula editors can be used: Microsoft Equation and Mathtype without changing the default settings ( you should not change fonts and sizes yourself, put spaces).

List of cited literature(see different types of links in) is compiled in the order of its mention in the article, in the text a link is given by a number in square brackets (for example,). The range of links is indicated by a dash. The list is printed on a separate sheet with the subheading "Literature" with digitization without brackets.

The list of used literature should be drawn up in the following form:

the surnames and initials of the authors are typed in italics;
for journal articles, the surnames and initials of the first 3 authors are indicated (for a larger number of authors, then “et al.” should be added), the title of the article, the name of the journal (use only generally accepted abbreviations), year, volume, issue (number), start and end pages;
for books, the names and initials of all authors, the title of the book, the place of publication, the name of the publisher, the year (for foreign books, indicate the data of the Russian translation, if any), the total number of pages or specific pages to which the author refers;
for copyright certificates, the names and initials of the first 3 authors are indicated (if there are more authors, then “et al.” or “et al.” should be put) authors, title, number of the copyright certificate, as well as the year, number and page of the Bulletin of Inventions, in which the material is published;
for patents, the names and initials of the first 3 authors are indicated (if there are more authors, then “et al.” or “et al.” should be put), title, country, number, year.

For example:

Journal article

1. A.P. Grammatin Title // Optical journal. 1997. T. 64. No. 3. S. 45−47.

2. Morin M. The name of the paper // Opt. Quant. Electron. 1997. V. 29. No. 5. P. 819−866.

Book

3. Rusinov M.M. Non-spherical surfaces in optics. Calculation, manufacturing, control. Moscow: Nauka, 1996.256 p.

4. McCartney E.J. Optics of the atmosphere. N.Y .: Willey, 1977.400 p.

5. Hart F., Henn F. Atlas of spectra of atoms. Moscow: Mir, 1987.250 p.

6. Repinsky G.N., Goncharenko E.N. Title // A. s. No. 932444. Bul. fig. 1982. No. 20.P. 247.

Patent

7. Antonov V.M. Title // Patent of Russia No. 777777. 1984.

Report theses

8. Ivanov V.V. Title // Abstracts. report II All-Union. conf. "Laser optics". L., 1962. Part 2.P. 22−24.

Deposited manuscript

9. Petrov S.I. Title // Dep. at VINITI. No. 1884−388 dated 02.19.1988.

Article in the collection

9. Rashba E.I. Title of the article in the collection // Title of the collection / Ed. Rashba E.I., Sterusha M.D. Moscow: Nauka, 1985.S. 385−398.

10. Favrol L.D. The name of the paper in this book // Title of the collection of articles / Ed. by Thompson D.O. N.Y .: Plenum Press, 1989. P. 210-247.

A link to an unpublished work can be provided only if the article on this work is accepted by the editors of the corresponding journal for publication. In this case, it is necessary to indicate the name of the journal, year, volume number and (preferably) the number of the issue with the intended publication.

Tables must be executed in Word or Excel, have a serial number and a name. Tables are printed on separate sheets and are not inserted into the text. The head of the table should not contain empty columns. Reference material in the table should be accompanied by references to relevant literature. Footnotes related to the table are indicated by asterixes (one, two, ...) and are placed below the table. General remarks on the contents of the table are printed below the table after the word "Note".

Drawings are attached to the file of the text of the article in the form of separate files in two versions: with designations (digital and alphabetic) and without them ("blind").

The submitted drawings should not be converted, but originally made in the following extensions:

Photos and bitmap illustrations must be in * .tif, * .png, * .jpg, * .bmp formats with a maximum resolution (at least 300 pixels / inch).

Vector drawings, graphs, diagrams, block diagrams must be made in vector programs, for example: Visio 4, 5,2002_2003 (* .vsd); Coreldraw (* .cdr); Excel; AdobeIllustrator; AutoCad; Compass; Matlab (export to * .ai, * .wmf format).

DOC and DOCX graphics are not allowed.

The picture field should be used as much as possible through the choice of scales along the axes and rational placement of illustrative material. Scale marks on the coordinate axes should be turned inside the chart field. Their number in the case of a linear scale should be no more than 5-7 with digitization every other. Units of measurement should be indicated in Russian. Figures should not contain inscriptions; if possible, only alphabetic and numeric designations should be used, the decoding of which is given in the figure caption. The latter should be extremely laconic and should not contain explanatory text fragments. If graphs in a certain range of values of the argument visually "merge", this range should either be excluded or shown separately in a scale suitable for resolving the curves.

To identify curves in captions, their digitization is used and reproduction of conventional symbols (circles, triangles, squares, asterisks, etc.) is not allowed. Figure captions are printed on a separate sheet and placed at the end of the article.

Figures should be as colorful as possible - for the electronic version of the magazine posted on the Internet. But in the printed version of the magazine, all drawings are performed in black and white grayscale. The publication of individual color drawings in the printed version is possible, but only if absolutely necessary, as an exception.

Simultaneous use of tables and figures to present the same work results is not allowed. Figures are numbered in accordance with the order of their mentioning in the text of the article.

Arrangement of the article material when sending to the editorial office

The text of the article, literature, figure captions, tables are put together in one file attached to the cover letter. Each figure is attached to the letter as a separate file.

Additional Information

In order to improve the quality of translation of articles, the editors ask the authors to attach a list of special terms with their English equivalents to the text of the article on a separate sheet.

Hello 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 friendly with SEO, and in general they 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 devoted to the "seos" of the popular engine (see in the category).

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

The DLE sitemap module I'm going to present to you meets all the SEO requirements and is extremely easy to install.

SiteMap - module for generating HTML sitemap for DLE

Original name: SiteMap
CMS Compatibility: DLE 8.2- 10.6
Spreading: Free, As Is, when distributing the link to the source is required
Current version: 2.2 (from 08/05/2014)
Purpose: Displays an unordered list with links to all posts, categories, and static pages.
Peculiarities: Visual code generator for embedding. Detailed setting of the principle of displaying all elements of the site - news, categories, static pages - the number of displayed elements, the principle of sorting 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 usability of our module to a new level. We (I hope, you too) liked the implemented visual code generation system very much and we decided to implement it in the sitemap module as well. Now you do not need to read manuals and descriptions of all functions and their values - just go to the admin panel, specify several values and that's it - the module is ready to go!

In addition to the above, I would like to list some 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 is taken into account, as well as the type of CNC;
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 being formed now). So this is also provided in this module - new publications are displayed with the url, the type of CNC of which is selected in the admin panel, and the old ones, respectively, with the url of the old-type CNC.

Despite the appearance of the 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 & param2 = value2")

param1 = - module parameter, value1 - parameter value. Module settings follow after? 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 through tpl during insertion:

need_cats - a list of category ids separated by commas for display in the map
exc_cats - a comma-separated list of category ids to exclude from the map

need_news - a list of article ids separated by commas to 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 - a comma-separated list of static page ids to display in the map
exc_static - a comma-separated list of static page ids to exclude 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 - show static pages in the map (1 or 0)

cats_sort - sort field for the list of categories (field from the dle_category table)
cats_msort - direction of sorting the list of categories (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 - sorting direction of 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 to display
news_limit - the maximum number of articles displayed from the category
static_limit - the maximum number of static pages to display

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

Optionally, you can change the appearance of the sitemap; for this, open the stylesheet (style.css) of your template and write the classes described below.

List of CSS classes for the sitemap:

Sitemap_categories - element