ZebroidDocumentationImportSQL import profiles

SQL import profiles

Documentation is not ready yet! If you have any questions - please contact with us using contact form
In program: Project → Import → SQL import profiles
To have possibility correctly to import SQL files, the program needs to explain what fields and in what table to it are necessary. For this purpose it is necessary to create a profile of import SQL.

Profiles of import SQL (tab «Article (main)»)

Profiles of import SQL (tab« Article (main) »)

In the top part of a window there are names of profiles. At double to a clique on a profile it is activated for editing.

The editor consists of 5 parts:

  1. Articles (main) — rules formation of the basic fields for article — the name and the text;
  2. to Article (add.) — rules formation of other fields for article;
  3. Categories — rules formation of categories;
  4. Comments — rules formation of comments of article;
  5. Filters and replacement — rules of search and replacement in the text after import.

«The SQL-file Analysis» which распарсит the file and will allocate tables being in it is recommended to use the button and weeding that considerably will facilitate process of drawing up of a template.

the Prevention : it is not recommended to create profiles of import to people who did not work earlier with databases.

Ready profiles

Import profiles created by us arrive to you together with updatings but if for any reasons at you they are absent or files have been damaged — you can download them on this page.

DataLife Engine.iniSize: 930 byte
Drupal.iniSize: 405 byte
Joomla 1.5.x.iniSize: 774 byte
MODx Evo.iniSize: 614 byte
WordPress.iniSize: 507 byte

Features of some CMS:

  • Drupal — as the content undertakes from the table «node_revisions» as a result can попадатся different versions of same article (depends on that, you edited it or not). By means of cleaning of doubles they easily leave
  • WordPress — as a matter of fact only import of a content without preservation of categories, labels etc.

Articles (main)

the Table — a table name from which posts will be imported. Concerns the first and the second вкладке.

the Name — corrected formation of the name of article. Теги in this field are specified in double braces. For example:

{{name}} - {{author}} 

In this case the name will consist of the given two fields.

article Text — formation тегов articles corrected. Simply place necessary теги in proper places. As well as in the previous case теги are specified in double braces (the editor will illuminate them dark blue).

Articles (add.)

Here the table in which are set an accessory defined тегов to article fields is presented. It consists of 2 basic columns:

Parameter — a field in which value тега will be brought. The list of accessible parametres:

  • the Category (identifier)
  • the Category (name)
  • Podategorija (name)
  • Labels
  • Date (виндовс a format)
  • Date (юникс a format)
  • the Sign of static page
  • alt_name
  • description
  • keywords
  • the record Identifier
  • the Condition to (choose)
  • the Condition to (pass)

the Field — a field name in the table of posts from which value will undertake.


It is necessary to fill this bookmark, if in base the structure of categories is separately described. Anything new on this вкладке is not present, unless the list of parametres for categories differs a little:

  • the Name
  • the Identifier
  • Alt_name
  • the Parent (name)
  • the Parent (identifier) — this field on which it is possible to define a parental category
  • the Condition to (choose)
  • the Condition to (pass)


It is necessary to fill this bookmark, if in base the structure of comments is separately described. Anything new on this вкладке is not present, unless the list of parametres for comments differs a little:

  • the Identifier
  • the Author
  • the Text
  • Date (виндовс a format)
  • Date (юникс a format)
  • the Condition to (choose)
  • the Condition to (pass)

Filters and replacement

In the given bookmark it is necessary to create rules of replacements, which are necessary to translate a content kept in a DB with by symbols in is suitable for use. As there it is necessary to create rules, with the help which will ubiratsja/be replaced office теги CMS.

Parameter samples