A layout file is with everything that goes with a normal HTML page to do so. Layout files are used as a template to create new pages and with the extension. Tpl in /content/layouts stored.
Important! If no wildcard awarded and no menu and block files are created, the "Edit" does not appear in the Admin. If this behavior is desired, the variable set in the file "/settings/globalvars.php" $webutler_config['fullpageedit'] are set to 1, to move the "Edit Current Page" in the Admin. !!!
This new links appear automatically on all pages, menus can be stored in separate files. In order for a menu is loaded, the file name must be written with comment fields in the layout file or page. Format:
<!-- begin_menu_MENUFILEAME -->
<!-- menu_MENUFILENAME -->
<!-- end_menu_MENUFILENAME -->
Blocks are on offer, when a content on different pages to be displayed and you want to change this content centrally. The formatting is the same for the menus:
<!-- begin_block_BLOCKFILENAME -->
<!-- block_BLOCKFILENAME -->
<!-- end_block_BLOCKFILENAME -->
Content areas that are to be opened in the editor are enclosed in comments. Format:
<!-- begin_content -->
editable content
<!-- end_content -->
The comments should be of an HTML block element enclosed (best DIV) and may not be nested, eg a menu within <!-- begin_content --> and <!-- end_content -->.
All menus must be created as "Unordered List = UL", so that they can be edited with the intended functions of the editor!
If a custom error page is created, must include the following source for the error message in the file:
<?PHP echo $webutlercouple->errorpagetext; ?>
For a smooth paste new columns elements the award of CSS classes to the various page elements is mandatory.
Who would not take advantage of the columns elements, set in the file /settings/globalvars.php the variable $webutler_config['insertcolumn'] to 0.
wb_menuelement - for menus
wb_blockelement - for blocks
wb_contentelement - for editable content
The classes must be awarded to an enclosing DIV. Other elements such as SECTION, HEADER, FOOTER etc. are not supported.
The columns elements themselves have the class
wb_columnselement
All four classes are needed so that new columns elements are inserted only outside of DIVs with these classes. If the classes are not set, nesting can occur which would make the administration inoperable.
wb_menuelement and wb_blockelement also replace the old class "block_border" and wb_contentelement replace the class "content_border".
Under the menu item Page > Columns new columns elements can configured. After a new columns elements has been selected, it can be inserted before or after each page and present in the DIV with one of the four CSS classes. If none of the classes exist, no columns can be selected. It should therefore at least once are the class wb_contentelement in the layout file.
Column settings such as distances can be made in the CSS file "columns/columns.css". Listed under System > Stylesheets.
All columns elements marked with the classes wb_contentelement or wb_columnselement can be deleted.
If columns are inserted in the editor, they are marked with gray border.
The menu item of the current page can be given a CSS class for a different look. If a nested menu is used, the class can also be assigned to the parent elements. If there are several menus to another class is possible for each menu.
Virtuelle Kategorien können angelegt werden. Seiten werden einer Kategorie zugeordnet und bei Aufruf erscheint die Kategorie in der URL. Kategorien sind nur in der URL sichbar. Virtual categories can be created. Pages are assigned to a category and the category will appear in the URL. Categories are only visible in the URL.
Highlighting categories is very similar to highlighting parent elements in a nested menu, but establishes a connection between 2 separate menus.
Any number of sub-categories and sub-menus can be set.
Example:
1. There is a main menu with the menu item "Services", that calls the page "info.phtml".
2. On the page "info.phtml" there is a second menu with the pages "service1.phtml" and "service2.phtml".
Now if you want, that the menu item Services (page info.phtml) is highlighted when you're on the pages service1.phtml or service2.phtml. Simply set all 3 pages in a category, for example "service", set a CSS class for the category in the main menu and activate the checkbox "highlight current category also".
Result:
If you call the page service1.phtml or service2.phtml from the second menu, the page info.phtml will be highlighted in the main menu.
If the checkbox "highlight current category also" is not set, the page info.phtml will not be highlighted. Are the pages service1.phtml and service2.phtml are set in a sub-category, eg "service/subservice", the checkbox must not be set and info.phtml, ie the category "service" is highlighted.
Important! If in the same menu several pages use the same category, all those pages are highlighted.
<script> ... </script> and <?PHP ... ?> code snippets may only be included in the <head> and <body> of a page. Code snippets outside of <head> and <body> are set mess validation in the editor.
With the variable $webutler_config['codeicon'] = "1" in globalvars.php code snippets can be visualized with icons. The icons do not always work smoothly! Icons are images and images are not valid at any place in the source code. If you have, for example, a list and want to control individual list items with PHP, the source code can look like this:
<ul>
<li>Item 1</li>
<?PHP if($a == 1) { ?><li>Item 2</li><?PHP } ?>
<li>Item 3</li>
</ul>
In the editor, the list looks like this:
• Item 1
[<>] • Item 2 [<>]
• Item 3
But the source is saved as:
<?PHP if($a == 1) { ?><?PHP } ?>
<ul>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ul>
As you can see, the code snippets has moved before the block element (UL). Default for $webutler_config['codeicon'] is 0. The variable should only be set to 1, if code snippets, seen as <img />, are valid in the source code.
Files such as CSS or Javascript can be dynamically loaded into a page or all pages. For this the file must be passed to the page. There are 2 options. If general files to be inserted into all pages, they can be loaded via the file "settings/extradata.php". Just copy the following lines in the file:
$webutler_autoheaderdata[] = '<script src="headerscript.js"></script>';
$webutler_autofooterdata[] = '<script src="footerscript.js"></script>';
If files are to be loaded on modules, the following can be put in the include file:
$webutlercouple->autoheaderdata[] = '<script src="headerscript.js"></script>';
$webutlercouple->autofooterdata[] = '<script src="footerscript.js"></script>';
Sometimes it is useful to know the file name of the last page, for example, redirects or as an alternative to "history.back()". But can to the session variable $_SESSION['history']['lastpage'] be accessed.
If user login administration is installed, the authentication information of the user in the session variable $_SESSION['userauth'] will be saved.
For multilingual pages can be retrieved using the session variable $_SESSION['language'], the language chosen by the visitors.
In each form contained on a page an additional hidden field is inserted. When a form is sent via POST from one side, the value of the hidden field with the value of the session variable $_SESSION['antixpost'] compared. The form will be sent only if the values match. This operation is designed to help spam curb a little.