Index: trunk/themes/inlink2/suggest_cat.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/suggest_cat.tpl (.../suggest_cat.tpl) (revision 29) +++ trunk/themes/inlink2/suggest_cat.tpl (.../suggest_cat.tpl) (revision 2868) @@ -1,17 +1,17 @@ - - - - - - -
- - -
- - - - - - + + + + + + +
+ + +
+ + + + + + \ No newline at end of file Index: trunk/themes/inlink2/reviews.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/reviews.tpl (.../reviews.tpl) (revision 626) +++ trunk/themes/inlink2/reviews.tpl (.../reviews.tpl) (revision 2868) @@ -1,153 +1,153 @@ - - - - - - -
- - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- " class="link"> - - - - -
:
:
:
:
:
:
:
:
:
:
: - -
:
:
- - -
- - - - - - - -
: ()
- -
- - - - - - - - - -
-
    - - - - - - - -
    - -
    - - -
-
- - -
-
- - - - + + + + + + +
+ + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ " class="link"> + + + + +
:
:
:
:
:
:
:
:
:
:
: + +
:
:
+ + +
+ + + + + + + +
: ()
+ +
+ + + + + + + + + +
+
    + + + + + + + +
    + +
    + + +
+
+ + +
+
+ + + + Index: trunk/themes/inlink2/edit_link/modify_link_element.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/edit_link/modify_link_element.tpl (.../modify_link_element.tpl) (revision 626) +++ trunk/themes/inlink2/edit_link/modify_link_element.tpl (.../modify_link_element.tpl) (revision 2868) @@ -1,48 +1,48 @@ -
  • -"> - -
    : - " class="tips"> - - - - - - - - - - -
    - - -(: -, : -, : -, : -, : -, : -, : ) - - -
    - -" class="link-review">  -" class="link-rate">  - - - - " class="link-modify"> - - - - -" class="link-review"> -  - -
    • +
  • +"> + +
    : + " class="tips"> + + + + + + + - + + +
    + + +(: +, : +, : +, : +, : +, : +, : ) + + +
    + +" class="link-review">  +" class="link-rate">  + + + + " class="link-modify"> + + + + +" class="link-review"> +  + +


    • \ No newline at end of file Index: trunk/themes/inlink2/new.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/new.tpl (.../new.tpl) (revision 650) +++ trunk/themes/inlink2/new.tpl (.../new.tpl) (revision 2868) @@ -1,76 +1,76 @@ - - - - - - -
    - -
    - - - - - - - -
    - -
    -
      - -
    -
    - -
    - -
    - - - - - - - + + + + + + +
    + +
    + + + + + + + +
    + +
    +
      + +
    +
    + +
    + +
    + + + + + + + Index: trunk/core/module_help/phrase_edit.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/core/module_help/phrase_edit.txt (.../phrase_edit.txt) (revision 1716) +++ trunk/core/module_help/phrase_edit.txt (.../phrase_edit.txt) (revision 2868) @@ -1,7 +1,7 @@ -A label has the following fields: -
      -
    • Phrase Id - this field is a read-only, unique and internal system language phrase ID.
      • -
    • Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
      • -
    • Value - this field contains the label value in the local language of the pack. That is where the translation goes.
      • -
    • Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism. There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button. As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
      • +A label has the following fields: +
        +
      • Phrase Id - this field is a read-only, unique and internal system language phrase ID.
        • +
      • Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
        • +
      • Value - this field contains the label value in the local language of the pack. That is where the translation goes.
        • +
      • Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism. There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button. As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
      \ No newline at end of file Index: trunk/kernel/module_help/stylesheets_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/kernel/module_help/stylesheets_edit.txt (.../stylesheets_edit.txt) (revision 1713) +++ trunk/kernel/module_help/stylesheets_edit.txt (.../stylesheets_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -General
      -
      -The style sheet edit form contains the following fields:
      -
        -
      • Stylesheet ID – internal, read-only system ID of the style sheet.
        • -
      • Name – administrator-assigned friendly name of the style sheet. It is used to attach it to a theme, and it is not displayed anywhere on the front end.
        • -
      • Description – this is a field for administrator’s notes about the style sheet.
        • -
      • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
        • -
      • Enabled – this checkbox controls whether the style sheet is enabled or disabled.
        • +General
        +
        +The style sheet edit form contains the following fields:
        +
          +
        • Stylesheet ID – internal, read-only system ID of the style sheet.
          • +
        • Name – administrator-assigned friendly name of the style sheet. It is used to attach it to a theme, and it is not displayed anywhere on the front end.
          • +
        • Description – this is a field for administrator’s notes about the style sheet.
          • +
        • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
          • +
        • Enabled – this checkbox controls whether the style sheet is enabled or disabled.
        \ No newline at end of file Index: trunk/themes/inlink2/profile.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/profile.tpl (.../profile.tpl) (revision 29) +++ trunk/themes/inlink2/profile.tpl (.../profile.tpl) (revision 2868) @@ -1,107 +1,107 @@ - - - - - - -
        - - -
        - - - "> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
         * -
         *
         *
         *
         *
         *
        * ()
        -
        -
        - " class="button"> - " class="button" onClick="javascript:history.back();"> -
        - - - - + + + + + + +
        + + +
        + + + "> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
         * +
         *
         *
         *
         *
         *
        * ()
        +
        +
        + " class="button"> + " class="button" onClick="javascript:history.back();"> +
        + + + + \ No newline at end of file Index: trunk/themes/inlink2/menu_user.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/menu_user.tpl (.../menu_user.tpl) (revision 626) +++ trunk/themes/inlink2/menu_user.tpl (.../menu_user.tpl) (revision 2868) @@ -1,42 +1,42 @@ - -

        - - " class="nav-usermenu-txt"> - - | - - - " class="nav-usermenu-txt"> - - | - " class="nav-usermenu-txt"> - - - | - " class="nav-usermenu-txt"> - - - | - " class="nav-usermenu-txt"> - - - - - | - " class="nav-usermenu-txt"> - - - - | - " class="nav-usermenu-txt"> - - - - | - " class="nav-usermenu-txt"> - - | - " class="nav-usermenu-txt"> - - -

        + +

        + + " class="nav-usermenu-txt"> + + | + + + " class="nav-usermenu-txt"> + + | + " class="nav-usermenu-txt"> + + + | + " class="nav-usermenu-txt"> + + + | + " class="nav-usermenu-txt"> + + + + + | + " class="nav-usermenu-txt"> + + + + | + " class="nav-usermenu-txt"> + + + + | + " class="nav-usermenu-txt"> + + | + " class="nav-usermenu-txt"> + + +

        Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/io.php =================================================================== diff -u -N -r1415 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/io.php (.../io.php) (revision 1415) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/io.php (.../io.php) (revision 2868) @@ -1,102 +1,86 @@ - \ No newline at end of file Index: trunk/themes/inlink2/show_links.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/show_links.tpl (.../show_links.tpl) (revision 29) +++ trunk/themes/inlink2/show_links.tpl (.../show_links.tpl) (revision 2868) @@ -1,15 +1,15 @@ - - - - - - +
        - -
        -
          - -
        -
        - -
        + + + + +
        + +
        +
          + +
        +
        + +
        \ No newline at end of file Index: trunk/core/module_help/styles_list.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/styles_list.txt (.../styles_list.txt) (revision 1713) +++ trunk/core/module_help/styles_list.txt (.../styles_list.txt) (revision 2868) @@ -1,14 +1,14 @@ - - - - - - -

        Stylesheets
        -
        -        The “Stylesheets” section of the Console lists all available style sheets. Here you can add, modify and delete the style sheets, as well as enable, disable and clone them. Remember, that to take effect, a style sheet must be enabled and attached to a theme.

        + + + + + + +

        Stylesheets
        +
        +        The “Stylesheets” section of the Console lists all available style sheets. Here you can add, modify and delete the style sheets, as well as enable, disable and clone them. Remember, that to take effect, a style sheet must be enabled and attached to a theme.

        When editing base and block styles, please don’t forget that the changes do not take effect until the entire style sheet is saved.

        \ No newline at end of file Index: trunk/themes/inlink2/list_reviews.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/list_reviews.tpl (.../list_reviews.tpl) (revision 29) +++ trunk/themes/inlink2/list_reviews.tpl (.../list_reviews.tpl) (revision 2868) @@ -1,8 +1,8 @@ -
      • - -
        -(: -: - -">) -
        • +
      • + +
        +(: +: + +">) +
        • Index: trunk/themes/inlink2/display_search_results.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/display_search_results.tpl (.../display_search_results.tpl) (revision 29) +++ trunk/themes/inlink2/display_search_results.tpl (.../display_search_results.tpl) (revision 2868) @@ -1,52 +1,52 @@ - - - - - - -
        -
        - - - - - - - -
        -
        "> - " class="input" style="width: 235px;">  - " class="button">
        - - - -
        - - - - - - - - -
        - - - - -
        -
        - - -
        - - - - - -
        - - - - + + + + + + +
        +
        + + + + + + + +
        +
        "> + " class="input" style="width: 235px;">  + " class="button">
        + + + + - - + + + \ No newline at end of file Index: trunk/core/admin_templates/js/colorselector.js =================================================================== diff -u -N -r1566 -r2868 --- trunk/core/admin_templates/js/colorselector.js (.../colorselector.js) (revision 1566) +++ trunk/core/admin_templates/js/colorselector.js (.../colorselector.js) (revision 2868) @@ -1,104 +1,104 @@ - // color Selector - - var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF'; - var $color_selector_field = ''; - - function InitColorSelector() - { - var $selector = document.getElementById('colorSelector_div'); - - if( !isset($selector) ) - { - var $selector = document.createElement('DIV'); - $selector.id = 'colorSelector_div'; - $selector.className = 'table_color1'; - $selector.style.width = '178px'; - $selector.style.borderWidth = '1px'; - $selector.style.borderColor = '#000000'; - $selector.style.display = 'none'; - $selector.style.position = 'absolute'; - $selector.style.borderStyle = 'solid'; - - var $s_table = document.createElement('TABLE'); - $s_table.id = 'colorSelector'; - $selector.appendChild($s_table); - document.body.appendChild($selector); - - var oTable = document.getElementById('colorSelector'); - var iCounter = 0; - aColors = aColors.split(','); - - while(iCounter < aColors.length) - { - var oRow = oTable.insertRow(-1); - for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++) - { - var $cell = document.createElement('TD'); - $cell.innerHTML = '
        '; - $cell.onmouseover = this.colorMouseOver; - $cell.onmouseout = this.colorMouseOut; - $cell.onclick = this.colorClick; - $cell.setAttribute('ColorIndex', iCounter); - var oDiv=oRow.insertCell(-1).appendChild($cell); - }; - } - } - } - - function updateColor($event,$color_id) - { - document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value; - } - - function colorMouseOver($e) - { - if(!$e) $e = window.event; - //print_pre(this); - this.parentNode.style.backgroundColor = '#C8D3E2'; - this.parentNode.style.borderColor = '#7196CC'; - - } - - function colorMouseOut($e, $element) - { - if(!$e) $e = window.event; - if(!$element) $element = this; - $element.parentNode.style.backgroundColor = '#F6F6F6'; - $element.parentNode.style.borderColor = '#F6F6F6'; - } - - function colorClick($e) - { - if(!$e) $e = window.event; - var $color = aColors[ this.getAttribute('ColorIndex') ]; - - document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color; - document.getElementById($color_selector_field).value = '#' + $color; - document.getElementById('colorSelector_div').style.display = 'none'; - - colorMouseOut($e, this); - } - - function openColorSelector($e, $field) - { - $color_selector_field = $field; - var $div = document.getElementById('colorSelector_div'); - - var posx = 0; - var posy = 0; - if (!$e) var $e = window.event; - if ($e.pageX || $e.pageY) - { - posx = $e.pageX; - posy = $e.pageY; - } - else if ($e.clientX || $e.clientY) - { - posx = $e.clientX + document.body.scrollLeft; - posy = $e.clientY + document.body.scrollTop; - } - - $div.style.left = posx; - $div.style.top = posy; - $div.style.display = 'block'; - } + // color Selector + + var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF'; + var $color_selector_field = ''; + + function InitColorSelector() + { + var $selector = document.getElementById('colorSelector_div'); + + if( !isset($selector) ) + { + var $selector = document.createElement('DIV'); + $selector.id = 'colorSelector_div'; + $selector.className = 'table_color1'; + $selector.style.width = '178px'; + $selector.style.borderWidth = '1px'; + $selector.style.borderColor = '#000000'; + $selector.style.display = 'none'; + $selector.style.position = 'absolute'; + $selector.style.borderStyle = 'solid'; + + var $s_table = document.createElement('TABLE'); + $s_table.id = 'colorSelector'; + $selector.appendChild($s_table); + document.body.appendChild($selector); + + var oTable = document.getElementById('colorSelector'); + var iCounter = 0; + aColors = aColors.split(','); + + while(iCounter < aColors.length) + { + var oRow = oTable.insertRow(-1); + for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++) + { + var $cell = document.createElement('TD'); + $cell.innerHTML = '
        '; + $cell.onmouseover = this.colorMouseOver; + $cell.onmouseout = this.colorMouseOut; + $cell.onclick = this.colorClick; + $cell.setAttribute('ColorIndex', iCounter); + var oDiv=oRow.insertCell(-1).appendChild($cell); + }; + } + } + } + + function updateColor($event,$color_id) + { + document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value; + } + + function colorMouseOver($e) + { + if(!$e) $e = window.event; + //print_pre(this); + this.parentNode.style.backgroundColor = '#C8D3E2'; + this.parentNode.style.borderColor = '#7196CC'; + + } + + function colorMouseOut($e, $element) + { + if(!$e) $e = window.event; + if(!$element) $element = this; + $element.parentNode.style.backgroundColor = '#F6F6F6'; + $element.parentNode.style.borderColor = '#F6F6F6'; + } + + function colorClick($e) + { + if(!$e) $e = window.event; + var $color = aColors[ this.getAttribute('ColorIndex') ]; + + document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color; + document.getElementById($color_selector_field).value = '#' + $color; + document.getElementById('colorSelector_div').style.display = 'none'; + + colorMouseOut($e, this); + } + + function openColorSelector($e, $field) + { + $color_selector_field = $field; + var $div = document.getElementById('colorSelector_div'); + + var posx = 0; + var posy = 0; + if (!$e) var $e = window.event; + if ($e.pageX || $e.pageY) + { + posx = $e.pageX; + posy = $e.pageY; + } + else if ($e.clientX || $e.clientY) + { + posx = $e.clientX + document.body.scrollLeft; + posy = $e.clientY + document.body.scrollTop; + } + + $div.style.left = posx; + $div.style.top = posy; + $div.style.display = 'block'; + } Index: trunk/kernel/admin/include/help/system.txt =================================================================== diff -u -N -r1231 -r2868 --- trunk/kernel/admin/include/help/system.txt (.../system.txt) (revision 1231) +++ trunk/kernel/admin/include/help/system.txt (.../system.txt) (revision 2868) @@ -1,2 +1,2 @@ -

        This section allows the administrator to update +

        This section allows the administrator to update the system settings of the In-portal platform.

        \ No newline at end of file Index: trunk/core/module_help/base_styles.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/base_styles.txt (.../base_styles.txt) (revision 1713) +++ trunk/core/module_help/base_styles.txt (.../base_styles.txt) (revision 2868) @@ -1,9 +1,9 @@ - - - - - -Base Styles
        -
        -This tab lists all base styles of the style sheet. The base styles have exactly the same properties as the block styles (see above). They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.
        + + + + + +Base Styles
        +
        +This tab lists all base styles of the style sheet. The base styles have exactly the same properties as the block styles (see above). They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.
        The base styles define how the general page elements look, as opposed to specific content block styles. \ No newline at end of file Index: trunk/themes/inlink2/login.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/login.tpl (.../login.tpl) (revision 29) +++ trunk/themes/inlink2/login.tpl (.../login.tpl) (revision 2868) @@ -1,8 +1,8 @@ - - - - - - - + + + + + + + \ No newline at end of file Index: trunk/themes/inlink2/search_results/list_search_links.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/search_results/list_search_links.tpl (.../list_search_links.tpl) (revision 29) +++ trunk/themes/inlink2/search_results/list_search_links.tpl (.../list_search_links.tpl) (revision 2868) @@ -1,38 +1,38 @@ -
      • -"> - - - - - - - - - - -
        - - -(: -, : -, : -, : -, : -, : -, : ) - - -
        - -" class="link-review">  -" class="link-rate">  - - - - - - -" class="link-review"> -  - -
        • +
      • +"> + + + + + + + - + + +
        + + +(: +, : +, : +, : +, : +, : +, : ) + + +
        + +" class="link-review">  +" class="link-rate">  + + + + + + +" class="link-review"> +  + +

        • \ No newline at end of file Index: trunk/core/module_help/block_style_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/block_style_edit.txt (.../block_style_edit.txt) (revision 1713) +++ trunk/core/module_help/block_style_edit.txt (.../block_style_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -Each block style has the following properties:
        -
          -
        • Selector ID – internal, read-only ID of the selector.
          • -
        • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
          • -
        • Based On – the name of the base style, related to this block style.
          • -
        • Name – the name of the block style, used for internal reference by the administrator.
          • -
        • Description – this is a field for administrator’s notes about the style sheet.
          • -
        • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
          • -
        • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
          • +Each block style has the following properties:
          +
            +
          • Selector ID – internal, read-only ID of the selector.
            • +
          • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
            • +
          • Based On – the name of the base style, related to this block style.
            • +
          • Name – the name of the block style, used for internal reference by the administrator.
            • +
          • Description – this is a field for administrator’s notes about the style sheet.
            • +
          • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
            • +
          • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
          \ No newline at end of file Index: trunk/themes/inlink2/list_fav_links.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/list_fav_links.tpl (.../list_fav_links.tpl) (revision 29) +++ trunk/themes/inlink2/list_fav_links.tpl (.../list_fav_links.tpl) (revision 2868) @@ -1,38 +1,38 @@ -
        • -"> - - - - - - - - - - -
          - - -(: -, : -, : -, : -, : -, : -, : ) - - -
          - -" class="link-review">  -" class="link-rate">  - - - - - - -" class="link-review"> -  - -
          • +
        • +"> + + + + + + + - + + +
          + + +(: +, : +, : +, : +, : +, : +, : ) + + +
          + +" class="link-review">  +" class="link-rate">  + + + + + + +" class="link-review"> +  + +


          • \ No newline at end of file Index: trunk/themes/inlink2/add_review.tpl =================================================================== diff -u -N -r40 -r2868 --- trunk/themes/inlink2/add_review.tpl (.../add_review.tpl) (revision 40) +++ trunk/themes/inlink2/add_review.tpl (.../add_review.tpl) (revision 2868) @@ -1,18 +1,18 @@ - - -
        + + + + + + + + +
        + + + + +
        +
        + + +
        + + + + + +
        + + + + \ No newline at end of file Index: trunk/kernel/module_help/base_style_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/kernel/module_help/base_style_edit.txt (.../base_style_edit.txt) (revision 1713) +++ trunk/kernel/module_help/base_style_edit.txt (.../base_style_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -Each block style has the following properties:
        -
          -
        • Selector ID – internal, read-only ID of the selector.
          • -
        • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
          • -
        • Based On – the name of the base style, related to this block style.
          • -
        • Name – the name of the block style, used for internal reference by the administrator.
          • -
        • Description – this is a field for administrator’s notes about the style sheet.
          • -
        • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
          • -
        • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
          • +Each block style has the following properties:
          +
            +
          • Selector ID – internal, read-only ID of the selector.
            • +
          • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
            • +
          • Based On – the name of the base style, related to this block style.
            • +
          • Name – the name of the block style, used for internal reference by the administrator.
            • +
          • Description – this is a field for administrator’s notes about the style sheet.
            • +
          • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
            • +
          • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
          \ No newline at end of file Index: trunk/themes/inlink2/search_advanced_cats.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/search_advanced_cats.tpl (.../search_advanced_cats.tpl) (revision 29) +++ trunk/themes/inlink2/search_advanced_cats.tpl (.../search_advanced_cats.tpl) (revision 2868) @@ -1,49 +1,49 @@ - - - - - - - - - - - -
          - - - - " class="search-advanced"> - - - - - " class="search-advanced"> - - - -
          - - - - - - - - - - - -
          - -
          - -
          - - -
          - - - - + + + + + + + + + + + +
          + + + + " class="search-advanced"> + + + + + " class="search-advanced"> + + + +
          + + + + + + + + + + + +
          + +
          + +
          + + +
          + + + + \ No newline at end of file Index: trunk/themes/inlink2/confirm.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/confirm.tpl (.../confirm.tpl) (revision 29) +++ trunk/themes/inlink2/confirm.tpl (.../confirm.tpl) (revision 2868) @@ -1,32 +1,32 @@ - - - - - - -
          - - -
          - - - - - -
          -
          -

          - - - -

          -
          - - - -
          - - - - + + + + + + +
          + + +
          + + + + + +
          +
          +

          + + + +

          +
          + + + +
          + + + + \ No newline at end of file Index: trunk/themes/inlink2/details.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/details.tpl (.../details.tpl) (revision 626) +++ trunk/themes/inlink2/details.tpl (.../details.tpl) (revision 2868) @@ -1,164 +1,164 @@ - - - - - - -
          - - >
          - - - - - -
          - - -
          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
          - " class="link"> - - - - -
          :
          :
          :
          :
          :
          :
          :
          :
          :
          :
          : - -
          :
          :
          - - -
          - - - - - - - -
          : ()
          - -
          - - - - - - - - - -
          -
            - - - - - - - -
            - -
            - - -
          -
          - - -
          -
          - - - - - - + + + + + + +
          + + >
          + + + + + +
          + + +
          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          + " class="link"> + + + + +
          :
          :
          :
          :
          :
          :
          :
          :
          :
          :
          : + +
          :
          :
          + + +
          + + + + + + + +
          : ()
          + +
          + + + + + + + + + +
          +
            + + + + + + + +
            + +
            + + +
          +
          + + +
          +
          + + + + + + \ No newline at end of file Index: trunk/kernel/module_help/base_styles.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/kernel/module_help/base_styles.txt (.../base_styles.txt) (revision 1713) +++ trunk/kernel/module_help/base_styles.txt (.../base_styles.txt) (revision 2868) @@ -1,9 +1,9 @@ - - - - - -Base Styles
          -
          -This tab lists all base styles of the style sheet. The base styles have exactly the same properties as the block styles (see above). They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.
          + + + + + +Base Styles
          +
          +This tab lists all base styles of the style sheet. The base styles have exactly the same properties as the block styles (see above). They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.
          The base styles define how the general page elements look, as opposed to specific content block styles. \ No newline at end of file Index: trunk/themes/inlink2/list_rel_cats.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/list_rel_cats.tpl (.../list_rel_cats.tpl) (revision 29) +++ trunk/themes/inlink2/list_rel_cats.tpl (.../list_rel_cats.tpl) (revision 2868) @@ -1,4 +1,4 @@ -

          -" class="catsub"> - (/) -

          +

          +" class="catsub"> + (/) +

          Index: trunk/themes/inlink2/style.css =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/style.css (.../style.css) (revision 29) +++ trunk/themes/inlink2/style.css (.../style.css) (revision 2868) @@ -1,118 +1,118 @@ -/* default text */ -.text {font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} - -/* small text */ -.small { font-family: verdana, arial, helvetica, sans-serif; font-size: 9px} - -/* top navigation */ -.nav-top-bg { background-color: #a0a0e0} -.nav-top-txt { background-color: #a0a0e0; font-family: arial, helvetica, sans-serif; font-size: 13px; font-weight: 900; color: #ffffff; text-decoration: none;} -.nav-top-txt:hover { color: #ffcc33} - -/* category navigation */ -.navbar { font-family: arial, verdana, sans-serif; font-weight: bold; font-size: 10pt; background-color: #f0f0f0; color: #003399; text-decoration: none;} -.navbar:vlink { color: #003399; text-decoration: none;} -.navbar:link { color: #003399; text-decoration: none;} -.navbar:alink { color: #003399; text-decoration: none;} -.navbar:hover { color: #9d9ddc; text-decoration: none;} - -/*user navigation */ -.nav-usermenu-title { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #999999} -.nav-usermenu-txt { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #4141c0; text-decoration: underline} -.nav-usermenu-txt:hover { color: #a0a0e0; font-family: verdana, arial, helvetica, sans-serif; font-size: 12px} - -/* alternating table rows */ -.cell1 { background-color: #f6f6f6; font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} -.cell2 { background-color: #dedede; font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} - -/* dialog boxes */ -.box-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #dedede} - -/* titles */ -.title { font-family: verdana, arial, helvetica, sans-serif; font-size: 10pt; font-weight: bold; color: #373737; background-color: #E5E5E5} -.subtitle { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 800; color: #ffffff; background-color: #666666} - -/* system messages and errors */ -.sys-message { color: #C0C0C0; font-family: arial,verdana,sans-serif; font-size: 9pt; } -.error { font-family: verdana, arial, helvetica, sans-serif; font-size: 9pt; color: #FF3300; font-weight: bold} -.small-msg { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999} - -/* statistics and misc. messages */ -.stats { color: #707070; font-family: arial,verdana,sans-serif; font-size: 9pt; } -.stats-small { font-family: arial, helvetica, sans-serif; font-size: 9px;} - -/* search */ -.search-title { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 800; color: #ffffff; background-color: #666666} -.search-field-lable { font-family: arial, helvetica, sans-serif; font-size: 12px} -.search-advanced { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 900; text-decoration: none; color: #000000} -.search-bg { background-color: #dedede} -.search-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #dedede} -.search-advanced:hover { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #a0a0e0; font-weight: 900} - -/* small text fields */ -.textbox { font-family: arial, helvetica, sans-serif; font-size: 10px} - -/* buttons */ -.button { font-family: arial, helvetica, sans-serif; font-size: 10px; background-color: #f9eeae} -.buttonsmall { font-family: arial, helvetica, sans-serif; font-size: 9px; background-color: #f9eeae; ; cursor: hand} - -/* float boxes */ -.floatbox-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #fef5cf} -.floatbox-title { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #ffffff; background-color: #666666} -.floatbox-txt { font-family: arial, helvetica, sans-serif; font-size: 10px} -.spacing-pad-left { padding-left: 15px} -.floatbox-link { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #000000; text-decoration: none} -.floatbox-link:hover { color: #9d9ddc; font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700} - -/* spacing styles */ -.spacing-pad-top-right { padding-top: 15px; padding-right: 15px} -.spacing-pad-top-left { padding-top: 15px; padding-left: 15px} -.spacing-pad-left-right { padding-right: 15px ; padding-left: 15px} - -/* categories */ -.cat { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #003399; font-weight: bold;} -.cat:hover { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #a0a0e0; font-weight: bold;} -.catsub { font-family: arial, helvetica, sans-serif; font-size: 8pt; color: #000090 } -.catsub:hover { color: #9d9ddc; font-family: arial, helvetica, sans-serif; font-size: 8pt} -.cat-no { color: #707070; font-family: arial, verdana, sans-serif; font-size: 10px; } -.cat-desc { color: black; font-family: arial,verdana,sans-serif; font-size: 9pt; } -.cat-new { color: blue; font-family: arial, verdana, sans-serif; font-size: 12px; ; vertical-align: super} -.cat-pick { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #009900; vertical-align: super} -.cats-stats { color: #707070; font-family: arial,verdana,sans-serif; font-size: 9pt; } - -/* links */ -.link { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #003399; } -.link:hover { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #a0a0e0;} -.link-rate { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #006600; text-decoration: none; } -.link-review { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #a27900; text-decoration: none; } -.link-modify { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #800000; text-decoration: none; } -.link-div{ font-family: arial, helvetica, sans-serif; font-size: 12px; color: #000000; text-decoration: none; } -.link-desc { color: black; font-family: arial,verdana,sans-serif; font-size: 9pt; } -.link-detail { color: #707070; font-family: arial,verdana,sans-serif; font-size: 8pt; } -.link-new { color: blue; font-family: arial, verdana, sans-serif; font-size: 12px; ; vertical-align: super} -.link-top { color: red; font-family: arial, verdana, sans-serif; font-size: 12px; vertical-align: super} -.link-pop { color: orange; font-family: arial, verdana, sans-serif; font-size: 12px; vertical-align: super} -.link-pick { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #009900; vertical-align: super} - -/* reviews */ -.review { font-family: arial, helvetica, sans-serif; font-size: 9pt;} -.review-detail { color: #707070; font-family: arial,verdana,sans-serif; font-size: 8pt; } -.review-detail:hover { color: #a0a0e0; font-family: arial,verdana,sans-serif; font-size: 8pt; } - -/* page navigation */ -.pagenav { font-family: arial, verdana, helvetica, sans-serif; font-size: 12px; color: #00000; font-weight: bold;} - -/* copyright */ -.copyright { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999; text-decoration: none;} -.copyright:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999; text-decoration: none;} - -/* small path links */ -.small_path { font-family: verdana, arial, helvetica, sans-serif; font-size: 10px; color: #A8A8A8; text-decoration: none; } -.small_path:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 10px; color: #C7C7C7; text-decoration: underline; } - -/* normal path links */ -.normal_path { font-family: verdana, arial, helvetica, sans-serif; font-size: 13px; color: black; text-decoration: none; } -.normal_path:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 13px; color: #C7C7C7; text-decoration: underline; } - -/* search box */ -.searchbox-table {border: #F7F7FF; border-style: solid; border-top-width: 0px; border-right-width: 2px; border-bottom-width: 2px; border-left-width: 2px; background-color: #FFFFFF;} +/* default text */ +.text {font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} + +/* small text */ +.small { font-family: verdana, arial, helvetica, sans-serif; font-size: 9px} + +/* top navigation */ +.nav-top-bg { background-color: #a0a0e0} +.nav-top-txt { background-color: #a0a0e0; font-family: arial, helvetica, sans-serif; font-size: 13px; font-weight: 900; color: #ffffff; text-decoration: none;} +.nav-top-txt:hover { color: #ffcc33} + +/* category navigation */ +.navbar { font-family: arial, verdana, sans-serif; font-weight: bold; font-size: 10pt; background-color: #f0f0f0; color: #003399; text-decoration: none;} +.navbar:vlink { color: #003399; text-decoration: none;} +.navbar:link { color: #003399; text-decoration: none;} +.navbar:alink { color: #003399; text-decoration: none;} +.navbar:hover { color: #9d9ddc; text-decoration: none;} + +/*user navigation */ +.nav-usermenu-title { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #999999} +.nav-usermenu-txt { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #4141c0; text-decoration: underline} +.nav-usermenu-txt:hover { color: #a0a0e0; font-family: verdana, arial, helvetica, sans-serif; font-size: 12px} + +/* alternating table rows */ +.cell1 { background-color: #f6f6f6; font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} +.cell2 { background-color: #dedede; font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #000000} + +/* dialog boxes */ +.box-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #dedede} + +/* titles */ +.title { font-family: verdana, arial, helvetica, sans-serif; font-size: 10pt; font-weight: bold; color: #373737; background-color: #E5E5E5} +.subtitle { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 800; color: #ffffff; background-color: #666666} + +/* system messages and errors */ +.sys-message { color: #C0C0C0; font-family: arial,verdana,sans-serif; font-size: 9pt; } +.error { font-family: verdana, arial, helvetica, sans-serif; font-size: 9pt; color: #FF3300; font-weight: bold} +.small-msg { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999} + +/* statistics and misc. messages */ +.stats { color: #707070; font-family: arial,verdana,sans-serif; font-size: 9pt; } +.stats-small { font-family: arial, helvetica, sans-serif; font-size: 9px;} + +/* search */ +.search-title { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 800; color: #ffffff; background-color: #666666} +.search-field-lable { font-family: arial, helvetica, sans-serif; font-size: 12px} +.search-advanced { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 900; text-decoration: none; color: #000000} +.search-bg { background-color: #dedede} +.search-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #dedede} +.search-advanced:hover { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #a0a0e0; font-weight: 900} + +/* small text fields */ +.textbox { font-family: arial, helvetica, sans-serif; font-size: 10px} + +/* buttons */ +.button { font-family: arial, helvetica, sans-serif; font-size: 10px; background-color: #f9eeae} +.buttonsmall { font-family: arial, helvetica, sans-serif; font-size: 9px; background-color: #f9eeae; ; cursor: hand} + +/* float boxes */ +.floatbox-table { border: #000000; border-style: solid; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; background-color: #fef5cf} +.floatbox-title { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #ffffff; background-color: #666666} +.floatbox-txt { font-family: arial, helvetica, sans-serif; font-size: 10px} +.spacing-pad-left { padding-left: 15px} +.floatbox-link { font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700; color: #000000; text-decoration: none} +.floatbox-link:hover { color: #9d9ddc; font-family: arial, helvetica, sans-serif; font-size: 12px; font-weight: 700} + +/* spacing styles */ +.spacing-pad-top-right { padding-top: 15px; padding-right: 15px} +.spacing-pad-top-left { padding-top: 15px; padding-left: 15px} +.spacing-pad-left-right { padding-right: 15px ; padding-left: 15px} + +/* categories */ +.cat { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #003399; font-weight: bold;} +.cat:hover { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #a0a0e0; font-weight: bold;} +.catsub { font-family: arial, helvetica, sans-serif; font-size: 8pt; color: #000090 } +.catsub:hover { color: #9d9ddc; font-family: arial, helvetica, sans-serif; font-size: 8pt} +.cat-no { color: #707070; font-family: arial, verdana, sans-serif; font-size: 10px; } +.cat-desc { color: black; font-family: arial,verdana,sans-serif; font-size: 9pt; } +.cat-new { color: blue; font-family: arial, verdana, sans-serif; font-size: 12px; ; vertical-align: super} +.cat-pick { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #009900; vertical-align: super} +.cats-stats { color: #707070; font-family: arial,verdana,sans-serif; font-size: 9pt; } + +/* links */ +.link { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #003399; } +.link:hover { font-family: arial, helvetica, sans-serif; font-size: 9pt; color: #a0a0e0;} +.link-rate { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #006600; text-decoration: none; } +.link-review { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #a27900; text-decoration: none; } +.link-modify { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #800000; text-decoration: none; } +.link-div{ font-family: arial, helvetica, sans-serif; font-size: 12px; color: #000000; text-decoration: none; } +.link-desc { color: black; font-family: arial,verdana,sans-serif; font-size: 9pt; } +.link-detail { color: #707070; font-family: arial,verdana,sans-serif; font-size: 8pt; } +.link-new { color: blue; font-family: arial, verdana, sans-serif; font-size: 12px; ; vertical-align: super} +.link-top { color: red; font-family: arial, verdana, sans-serif; font-size: 12px; vertical-align: super} +.link-pop { color: orange; font-family: arial, verdana, sans-serif; font-size: 12px; vertical-align: super} +.link-pick { font-family: arial, helvetica, sans-serif; font-size: 12px; color: #009900; vertical-align: super} + +/* reviews */ +.review { font-family: arial, helvetica, sans-serif; font-size: 9pt;} +.review-detail { color: #707070; font-family: arial,verdana,sans-serif; font-size: 8pt; } +.review-detail:hover { color: #a0a0e0; font-family: arial,verdana,sans-serif; font-size: 8pt; } + +/* page navigation */ +.pagenav { font-family: arial, verdana, helvetica, sans-serif; font-size: 12px; color: #00000; font-weight: bold;} + +/* copyright */ +.copyright { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999; text-decoration: none;} +.copyright:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 12px; color: #999999; text-decoration: none;} + +/* small path links */ +.small_path { font-family: verdana, arial, helvetica, sans-serif; font-size: 10px; color: #A8A8A8; text-decoration: none; } +.small_path:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 10px; color: #C7C7C7; text-decoration: underline; } + +/* normal path links */ +.normal_path { font-family: verdana, arial, helvetica, sans-serif; font-size: 13px; color: black; text-decoration: none; } +.normal_path:hover { font-family: verdana, arial, helvetica, sans-serif; font-size: 13px; color: #C7C7C7; text-decoration: underline; } + +/* search box */ +.searchbox-table {border: #F7F7FF; border-style: solid; border-top-width: 0px; border-right-width: 2px; border-bottom-width: 2px; border-left-width: 2px; background-color: #FFFFFF;} Index: trunk/core/module_help/stylesheets_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/stylesheets_edit.txt (.../stylesheets_edit.txt) (revision 1713) +++ trunk/core/module_help/stylesheets_edit.txt (.../stylesheets_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -General
          -
          -The style sheet edit form contains the following fields:
          -
            -
          • Stylesheet ID – internal, read-only system ID of the style sheet.
            • -
          • Name – administrator-assigned friendly name of the style sheet. It is used to attach it to a theme, and it is not displayed anywhere on the front end.
            • -
          • Description – this is a field for administrator’s notes about the style sheet.
            • -
          • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
            • -
          • Enabled – this checkbox controls whether the style sheet is enabled or disabled.
            • +General
            +
            +The style sheet edit form contains the following fields:
            +
              +
            • Stylesheet ID – internal, read-only system ID of the style sheet.
              • +
            • Name – administrator-assigned friendly name of the style sheet. It is used to attach it to a theme, and it is not displayed anywhere on the front end.
              • +
            • Description – this is a field for administrator’s notes about the style sheet.
              • +
            • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
              • +
            • Enabled – this checkbox controls whether the style sheet is enabled or disabled.
            \ No newline at end of file Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/config.php =================================================================== diff -u -N -r1626 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/config.php (.../config.php) (revision 1626) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/config.php (.../config.php) (revision 2868) @@ -1,62 +1,52 @@ - \ No newline at end of file Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/util.php =================================================================== diff -u -N -r1415 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/util.php (.../util.php) (revision 1415) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/util.php (.../util.php) (revision 2868) @@ -1,4 +1,4 @@ - - - - - - -
            -
            - - - - -"> - - - - - - - - - -
            - -
            -

            - " class="button">   " class="button"> -

            -
            -
            - - - - - - + + + + + + +
            +
            + + + + +"> + + + + + + + + + +
            + +
            +

            + " class="button">   " class="button"> +

            +
            +
            + + + + + + \ No newline at end of file Index: trunk/kernel/admin/include/help/users.txt =================================================================== diff -u -N -r1231 -r2868 --- trunk/kernel/admin/include/help/users.txt (.../users.txt) (revision 1231) +++ trunk/kernel/admin/include/help/users.txt (.../users.txt) (revision 2868) @@ -1,4 +1,4 @@ -

            This section lists all In-portal users. It allows -managing users, setting primary group for a user, approving and -disabling users, banning users and sending out mass emails to the +

            This section lists all In-portal users. It allows +managing users, setting primary group for a user, approving and +disabling users, banning users and sending out mass emails to the users.

            \ No newline at end of file Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/commands.php =================================================================== diff -u -N -r2816 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/commands.php (.../commands.php) (revision 2816) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/commands.php (.../commands.php) (revision 2868) @@ -1,355 +1,317 @@ -" ; - - $oCurrentFolder = opendir( $sServerDir ) ; - - while ( $sFile = readdir( $oCurrentFolder ) ) - { - if ( $sFile != '.' && $sFile != '..' && $sFile != 'CVS' && is_dir( $sServerDir . $sFile ) ) - echo '' ; - } - - closedir( $oCurrentFolder ) ; - - // Close the "Folders" node. - echo "" ; -} -/* -function GetCmsTree() -{ - - $conn = GetADODbConnection(); - $query="SELECT st.* , wb.eng_content AS page_title - FROM structure_templates st - LEFT JOIN working_blocks AS wb - ON (st.st_id = wb.template_id) AND (wb.block_type = 3) WHERE st_id != '5' AND st_path != '/cms' GROUP BY st_id ORDER BY st_lastupdate desc"; - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - $ret = ""; - while($rs && !$rs->EOF) { - $ret.= ''; - //echo $rs->fields['page_title']."
            "; - $rs->MoveNext(); - } - $ret.= '            '; - echo $ret; - } -} -*/ - -function GetCmsTree() -{ - global $Config; - $ret = ""; - - if (isset($Config['K4Mode'])) { - $ret.= K4ReadCmsTree(0); - } - else { - $ret.= ReadCmsTree(0); - } - $ret.= ""; - echo $ret; -} - -function K4ReadCmsTree($cat_id, $level = 0) -{ - $application =& kApplication::Instance(); - $application->Init(); - - $query = 'SELECT Path, Title FROM '.TABLE_PREFIX.'Pages'; - $pages = $application->DB->Query($query); - - $res = ''; - foreach ($pages as $page) { - $page_path = $page['Path'].'.html'; - $title = $page['Title'].' ('.$page_path.')'; - $res .= ''; - } - - return $res; -} - -function ReadCmsTree($st_id, $level = 0) -{ - $conn = GetADODbConnection(); - $query = "SELECT value FROM config WHERE name = 'default_lang_prefix'"; - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - $default_lang_prefix = $rs->fields['value']; - } - - $query = "SELECT value FROM config WHERE name = 'cms_direct_mode'"; - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - $cms_mode = $rs->fields['value']; - } - - $query = "SELECT value FROM config WHERE name = 'email_templates_folder_id'"; - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - $email_templates_folder_id = $rs->fields['value']; - } -/* - $query = "SELECT value FROM config WHERE name = 'custom_cms'"; - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - $custom_cms = $rs->fields['value']; - } -*/ - if ( $email_templates_folder_id == "" ) $email_templates_folder_id = 0; - - - if ( $cms_mode == 1 ) { - $query = " - SELECT st.*, - IF(lb.".$default_lang_prefix."_content='' OR lb.".$default_lang_prefix."_content IS NULL, - st.st_path, - lb.".$default_lang_prefix."_content - ) AS page_title - FROM - structure_templates AS st - LEFT JOIN - live_blocks AS lb - ON - (st.st_id = lb.template_id) AND (lb.block_type = 3) - WHERE st.st_parent_id = ".$st_id." - AND st_id != ".$email_templates_folder_id." - AND st_path != '/cms' - ORDER BY st.st_order"; - } - else { - $query = " - SELECT st.*, - IF(wb.".$default_lang_prefix."_content='' OR wb.".$default_lang_prefix."_content IS NULL, - st.st_path, - wb.".$default_lang_prefix."_content - ) AS page_title - FROM - structure_templates AS st - LEFT JOIN - working_blocks AS wb - ON - (st.st_id = wb.template_id) AND (wb.block_type = 3) - WHERE - st.st_parent_id = ".$st_id." - AND st_id != ".$email_templates_folder_id." - AND st_path != '/cms%' - ORDER BY st.st_order"; - - } - //echo $query."
            "; - - $rs = $conn->Execute($query); - if ($rs && !$rs->EOF) - { - while ($rs && !$rs->EOF) - { - $page_path = ltrim($rs->fields['st_path'], '/'); - //$page_path = SERVER_NAME.BASE_PATH.'/index.php?t='.$page_path; - //$page_path = $page_path; - $prefix=''; - for ($i = 0; $i < $level; $i++) - $prefix .= '--'; - if ($level > 0) - $prefix=$prefix.'- '; - $page = ereg_replace("&","&",$rs->fields['page_title']); - $page = ereg_replace("\"",""",$page); - $page = ereg_replace("'","'",$page); - $page = ereg_replace("<","<",$page); - $page = ereg_replace(">",">",$page); -// echo $page."
            "; - //$page = htmlentities($rs->fields['page_title'],ENT_QUOTES); - $page = $rs->fields['page_title']; - $page = ereg_replace("ã","a",$page); - $res .= ''; - $res .= ReadCmsTree($rs->fields['st_id'], $level+1); - - $rs->MoveNext(); - } - return $res; - } -} -/* - $res .= ' - - <![CDATA['.$prefix.$page.']]> - fields['st_id'].']]> - - '; - -*/ -function GetFoldersAndFiles( $resourceType, $currentFolder ) -{ - // Map the virtual path to the local server path. - $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; - - // Initialize the output buffers for "Folders" and "Files". - $sFolders = '' ; - $sFiles = '' ; - - $oCurrentFolder = opendir( $sServerDir ) ; - - while ( $sFile = readdir( $oCurrentFolder ) ) - { - if ( $sFile != '.' && $sFile != '..' && $sFile != 'CVS') - { - if ( is_dir( $sServerDir . $sFile ) ) - $sFolders .= '' ; - else - { - $iFileSize = filesize( $sServerDir . $sFile ) ; - if ( $iFileSize > 0 ) - { - $iFileSize = round( $iFileSize / 1024 ) ; - if ( $iFileSize < 1 ) $iFileSize = 1 ; - } - - $sFiles .= '' ; - } - } - } - - echo $sFolders ; - // Close the "Folders" node. - echo '' ; - - echo $sFiles ; - // Close the "Files" node. - echo '' ; -} - -function CreateFolder( $resourceType, $currentFolder ) -{ - $sErrorNumber = '0' ; - $sErrorMsg = '' ; - - if ( isset( $_GET['NewFolderName'] ) ) - { - $sNewFolderName = $_GET['NewFolderName'] ; - - // Map the virtual path to the local server path of the current folder. - $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; - - if ( is_writable( $sServerDir ) ) - { - $sServerDir .= $sNewFolderName ; - - $sErrorMsg = CreateServerFolder( $sServerDir ) ; - - switch ( $sErrorMsg ) - { - case '' : - $sErrorNumber = '0' ; - break ; - case 'Invalid argument' : - case 'No such file or directory' : - $sErrorNumber = '102' ; // Path too long. - break ; - default : - $sErrorNumber = '110' ; - break ; - } - } - else - $sErrorNumber = '103' ; - } - else - $sErrorNumber = '102' ; - - // Create the "Error" node. - echo '' ; -} - -function FileUpload( $resourceType, $currentFolder ) -{ - $sErrorNumber = '0' ; - $sFileName = '' ; - - if ( isset( $_FILES['NewFile'] ) && !is_null( $_FILES['NewFile']['tmp_name'] ) ) - { - $oFile = $_FILES['NewFile'] ; - - // Map the virtual path to the local server path. - $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; - - // Get the uploaded file name. - $sFileName = $oFile['name'] ; - $sOriginalFileName = $sFileName ; - $sExtension = substr( $sFileName, ( strrpos($sFileName, '.') + 1 ) ) ; - - global $Config ; - - $arAllowed = $Config['AllowedExtensions'][$resourceType] ; - $arDenied = $Config['DeniedExtensions'][$resourceType] ; - if ( ( count($arAllowed) == 0 || in_array( $sExtension, $arAllowed ) ) && ( count($arDenied) == 0 || !in_array( $sExtension, $arDenied ) ) ) - { - $iCounter = 0 ; - while ( true ) - { - $sFilePath = $sServerDir . $sFileName ; - - if ( is_file( $sFilePath ) ) - { - $iCounter++ ; - $sFileName = RemoveExtension( $sOriginalFileName ) . '(' . $iCounter . ').' . $sExtension ; - $sErrorNumber = '201' ; - } - else - { - move_uploaded_file( $oFile['tmp_name'], $sFilePath ) ; - - if ( is_file( $sFilePath ) ) - { - $oldumask = umask(0) ; - chmod( $sFilePath, 0777 ) ; - umask( $oldumask ) ; - } - - break ; - } - } - } - else - $sErrorNumber = '202' ; - } - else - $sErrorNumber = '202' ; - - echo '' ; - - exit ; -} -?> \ No newline at end of file +" ; + $oCurrentFolder = opendir( $sServerDir ) ; + while ( $sFile = readdir( $oCurrentFolder ) ) + { + if ( $sFile != '.' && $sFile != '..' && $sFile != 'CVS' && is_dir( $sServerDir . $sFile ) ) + echo '' ; + } + closedir( $oCurrentFolder ) ; + // Close the "Folders" node. + echo "" ; +} +/* +function GetCmsTree() +{ + + $conn = GetADODbConnection(); + $query="SELECT st.* , wb.eng_content AS page_title + FROM structure_templates st + LEFT JOIN working_blocks AS wb + ON (st.st_id = wb.template_id) AND (wb.block_type = 3) WHERE st_id != '5' AND st_path != '/cms' GROUP BY st_id ORDER BY st_lastupdate desc"; + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + $ret = ""; + while($rs && !$rs->EOF) { + $ret.= ''; + //echo $rs->fields['page_title']."
            "; + $rs->MoveNext(); + } + $ret.= '            '; + echo $ret; + } +} +*/ +function GetCmsTree() +{ + global $Config; + $ret = ""; + + if (isset($Config['K4Mode'])) { + $ret.= K4ReadCmsTree(0); + } + else { + $ret.= ReadCmsTree(0); + } + $ret.= ""; + echo $ret; +} +function K4ReadCmsTree($cat_id, $level = 0) +{ + $application =& kApplication::Instance(); + $application->Init(); + + $query = 'SELECT Path, Title FROM '.TABLE_PREFIX.'Pages'; + $pages = $application->DB->Query($query); + + $res = ''; + foreach ($pages as $page) { + $page_path = $page['Path'].'.html'; + $title = $page['Title'].' ('.$page_path.')'; + $res .= ''; + } + + return $res; +} +function ReadCmsTree($st_id, $level = 0) +{ + $conn = GetADODbConnection(); + $query = "SELECT value FROM config WHERE name = 'default_lang_prefix'"; + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + $default_lang_prefix = $rs->fields['value']; + } + $query = "SELECT value FROM config WHERE name = 'cms_direct_mode'"; + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + $cms_mode = $rs->fields['value']; + } + $query = "SELECT value FROM config WHERE name = 'email_templates_folder_id'"; + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + $email_templates_folder_id = $rs->fields['value']; + } +/* + $query = "SELECT value FROM config WHERE name = 'custom_cms'"; + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + $custom_cms = $rs->fields['value']; + } +*/ + if ( $email_templates_folder_id == "" ) $email_templates_folder_id = 0; + if ( $cms_mode == 1 ) { + $query = " + SELECT st.*, + IF(lb.".$default_lang_prefix."_content='' OR lb.".$default_lang_prefix."_content IS NULL, + st.st_path, + lb.".$default_lang_prefix."_content + ) AS page_title + FROM + structure_templates AS st + LEFT JOIN + live_blocks AS lb + ON + (st.st_id = lb.template_id) AND (lb.block_type = 3) + WHERE st.st_parent_id = ".$st_id." + AND st_id != ".$email_templates_folder_id." + AND st_path != '/cms' + ORDER BY st.st_order"; + } + else { + $query = " + SELECT st.*, + IF(wb.".$default_lang_prefix."_content='' OR wb.".$default_lang_prefix."_content IS NULL, + st.st_path, + wb.".$default_lang_prefix."_content + ) AS page_title + FROM + structure_templates AS st + LEFT JOIN + working_blocks AS wb + ON + (st.st_id = wb.template_id) AND (wb.block_type = 3) + WHERE + st.st_parent_id = ".$st_id." + AND st_id != ".$email_templates_folder_id." + AND st_path != '/cms%' + ORDER BY st.st_order"; + } + //echo $query."
            "; + + $rs = $conn->Execute($query); + if ($rs && !$rs->EOF) + { + while ($rs && !$rs->EOF) + { + $page_path = ltrim($rs->fields['st_path'], '/'); + //$page_path = SERVER_NAME.BASE_PATH.'/index.php?t='.$page_path; + //$page_path = $page_path; + $prefix=''; + for ($i = 0; $i < $level; $i++) + $prefix .= '--'; + if ($level > 0) + $prefix=$prefix.'- '; + $page = ereg_replace("&","&",$rs->fields['page_title']); + $page = ereg_replace("\"",""",$page); + $page = ereg_replace("'","'",$page); + $page = ereg_replace("<","<",$page); + $page = ereg_replace(">",">",$page); +// echo $page."
            "; + //$page = htmlentities($rs->fields['page_title'],ENT_QUOTES); + $page = $rs->fields['page_title']; + $page = ereg_replace("ã","a",$page); + $res .= ''; + $res .= ReadCmsTree($rs->fields['st_id'], $level+1); + + $rs->MoveNext(); + } + return $res; + } +} +/* + $res .= ' + + <![CDATA['.$prefix.$page.']]> + fields['st_id'].']]> + + '; +*/ +function GetFoldersAndFiles( $resourceType, $currentFolder ) +{ + // Map the virtual path to the local server path. + $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; + // Initialize the output buffers for "Folders" and "Files". + $sFolders = '' ; + $sFiles = '' ; + $oCurrentFolder = opendir( $sServerDir ) ; + while ( $sFile = readdir( $oCurrentFolder ) ) + { + if ( $sFile != '.' && $sFile != '..' && $sFile != 'CVS') + { + if ( is_dir( $sServerDir . $sFile ) ) + $sFolders .= '' ; + else + { + $iFileSize = filesize( $sServerDir . $sFile ) ; + if ( $iFileSize > 0 ) + { + $iFileSize = round( $iFileSize / 1024 ) ; + if ( $iFileSize < 1 ) $iFileSize = 1 ; + } + $sFiles .= '' ; + } + } + } + echo $sFolders ; + // Close the "Folders" node. + echo '' ; + echo $sFiles ; + // Close the "Files" node. + echo '' ; +} +function CreateFolder( $resourceType, $currentFolder ) +{ + $sErrorNumber = '0' ; + $sErrorMsg = '' ; + if ( isset( $_GET['NewFolderName'] ) ) + { + $sNewFolderName = $_GET['NewFolderName'] ; + // Map the virtual path to the local server path of the current folder. + $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; + if ( is_writable( $sServerDir ) ) + { + $sServerDir .= $sNewFolderName ; + $sErrorMsg = CreateServerFolder( $sServerDir ) ; + switch ( $sErrorMsg ) + { + case '' : + $sErrorNumber = '0' ; + break ; + case 'Invalid argument' : + case 'No such file or directory' : + $sErrorNumber = '102' ; // Path too long. + break ; + default : + $sErrorNumber = '110' ; + break ; + } + } + else + $sErrorNumber = '103' ; + } + else + $sErrorNumber = '102' ; + // Create the "Error" node. + echo '' ; +} +function FileUpload( $resourceType, $currentFolder ) +{ + $sErrorNumber = '0' ; + $sFileName = '' ; + if ( isset( $_FILES['NewFile'] ) && !is_null( $_FILES['NewFile']['tmp_name'] ) ) + { + $oFile = $_FILES['NewFile'] ; + // Map the virtual path to the local server path. + $sServerDir = ServerMapFolder( $resourceType, $currentFolder ) ; + // Get the uploaded file name. + $sFileName = $oFile['name'] ; + $sOriginalFileName = $sFileName ; + $sExtension = substr( $sFileName, ( strrpos($sFileName, '.') + 1 ) ) ; + global $Config ; + $arAllowed = $Config['AllowedExtensions'][$resourceType] ; + $arDenied = $Config['DeniedExtensions'][$resourceType] ; + if ( ( count($arAllowed) == 0 || in_array( $sExtension, $arAllowed ) ) && ( count($arDenied) == 0 || !in_array( $sExtension, $arDenied ) ) ) + { + $iCounter = 0 ; + while ( true ) + { + $sFilePath = $sServerDir . $sFileName ; + if ( is_file( $sFilePath ) ) + { + $iCounter++ ; + $sFileName = RemoveExtension( $sOriginalFileName ) . '(' . $iCounter . ').' . $sExtension ; + $sErrorNumber = '201' ; + } + else + { + move_uploaded_file( $oFile['tmp_name'], $sFilePath ) ; + if ( is_file( $sFilePath ) ) + { + $oldumask = umask(0) ; + chmod( $sFilePath, 0777 ) ; + umask( $oldumask ) ; + } + break ; + } + } + } + else + $sErrorNumber = '202' ; + } + else + $sErrorNumber = '202' ; + echo '' ; + exit ; +} +?> Index: trunk/kernel/module_help/block_style_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/kernel/module_help/block_style_edit.txt (.../block_style_edit.txt) (revision 1713) +++ trunk/kernel/module_help/block_style_edit.txt (.../block_style_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -Each block style has the following properties:
            -
              -
            • Selector ID – internal, read-only ID of the selector.
              • -
            • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
              • -
            • Based On – the name of the base style, related to this block style.
              • -
            • Name – the name of the block style, used for internal reference by the administrator.
              • -
            • Description – this is a field for administrator’s notes about the style sheet.
              • -
            • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
              • -
            • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
              • +Each block style has the following properties:
              +
                +
              • Selector ID – internal, read-only ID of the selector.
                • +
              • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
                • +
              • Based On – the name of the base style, related to this block style.
                • +
              • Name – the name of the block style, used for internal reference by the administrator.
                • +
              • Description – this is a field for administrator’s notes about the style sheet.
                • +
              • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
                • +
              • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
              \ No newline at end of file Index: trunk/themes/inlink2/login/box_login.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/login/box_login.tpl (.../box_login.tpl) (revision 29) +++ trunk/themes/inlink2/login/box_login.tpl (.../box_login.tpl) (revision 2868) @@ -1,45 +1,45 @@ - - "> - - - - - - - - - - - - - - - - - - - -
              -
              - : - - -
              - : - - -
              - " class="button"> - - - -
              -   -
              - - - - +
              " class="floatbox-link"> - -
              + "> + + + + + + + + + + + + + + + + + + + +
              +
              + : + + +
              + : + + +
              + " class="button"> + + + +
              +   +
              + + + +
              " class="floatbox-link"> + +
              \ No newline at end of file Index: trunk/themes/inlink2/pop.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/pop.tpl (.../pop.tpl) (revision 650) +++ trunk/themes/inlink2/pop.tpl (.../pop.tpl) (revision 2868) @@ -1,76 +1,76 @@ - - - - - - -
              - -
              - - - - - - - -
              - -
              -
                - -
              -
              - -
              - -
              - - - - - - - + + + + + + +
              + +
              + + + + + + + +
              + +
              +
                + +
              +
              + +
              + +
              + + + + + + + Index: trunk/themes/inlink2/search_advanced_links.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/search_advanced_links.tpl (.../search_advanced_links.tpl) (revision 29) +++ trunk/themes/inlink2/search_advanced_links.tpl (.../search_advanced_links.tpl) (revision 2868) @@ -1,49 +1,49 @@ - - - - - - - - - - - -
              - - - - " class="search-advanced"> - - - - - " class="search-advanced"> - - - -
              - - - - - - - - - - - -
              - -
              - -
              - - -
              - - - - + + + + + + + + + + + +
              + + + + " class="search-advanced"> + + + + + " class="search-advanced"> + + + +
              + + + + + + + + + + + +
              + +
              + +
              + + +
              + + + + \ No newline at end of file Index: trunk/themes/inlink2/top.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/top.tpl (.../top.tpl) (revision 650) +++ trunk/themes/inlink2/top.tpl (.../top.tpl) (revision 2868) @@ -1,76 +1,76 @@ - - - - - - -
              - -
              - - - - - - - -
              - -
              -
                - -
              -
              - -
              - -
              - - - - - - - + + + + + + +
              + +
              + + + + + + + +
              + +
              +
                + +
              +
              + +
              + +
              + + + + + + + Index: trunk/themes/inlink2/box_subscribe.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/box_subscribe.tpl (.../box_subscribe.tpl) (revision 29) +++ trunk/themes/inlink2/box_subscribe.tpl (.../box_subscribe.tpl) (revision 2868) @@ -1,22 +1,22 @@ - - "> - - - - - - - - - - - - - -
              -
              - -
              -
              - " class="button">
              " class="button"> -
              + + "> + + + + + + + + + + + + + +
              +
              + +
              +
              + " class="button">
              " class="button"> +
              Index: trunk/themes/inlink2/favorites.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/favorites.tpl (.../favorites.tpl) (revision 29) +++ trunk/themes/inlink2/favorites.tpl (.../favorites.tpl) (revision 2868) @@ -1,10 +1,10 @@ - - -

              - -
              - - - - - + + +

              + +
              + + + + + Index: trunk/kernel/module_help/block_styles.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/kernel/module_help/block_styles.txt (.../block_styles.txt) (revision 1713) +++ trunk/kernel/module_help/block_styles.txt (.../block_styles.txt) (revision 2868) @@ -1,3 +1,3 @@ -Block Styles
              -
              +Block Styles
              +
              This tab lists all block styles of the style sheet. Block styles describe the look & feel of specific content blocks to be used in a theme. Each block style is based on a base style (see next tab); sometimes it overrides one or more properties of the base style. You can add, modify and delete block styles, as well as clone and reset them to the base styles they are related to. \ No newline at end of file Index: trunk/themes/inlink2/pick.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/pick.tpl (.../pick.tpl) (revision 650) +++ trunk/themes/inlink2/pick.tpl (.../pick.tpl) (revision 2868) @@ -1,76 +1,76 @@ - - - - - - -
              - -
              - - - - - - - -
              - -
              -
                - -
              -
              - -
              - -
              - - - - - - - + + + + + + +
              + +
              + + + + + + + +
              + +
              +
                + +
              +
              + +
              + +
              + + + + + + + Index: trunk/kernel/module_help/languages_edit_general.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/kernel/module_help/languages_edit_general.txt (.../languages_edit_general.txt) (revision 1716) +++ trunk/kernel/module_help/languages_edit_general.txt (.../languages_edit_general.txt) (revision 2868) @@ -1,14 +1,14 @@ -The general tab contains the cultural settings of the pack. -
                -
              • Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
                • -
              • Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
                • -
              • Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'
                • -
              • Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
                • -
              • Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
                • -
              • Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
                • -
              • Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.
                • -
              • Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.
                • -
              • Enabled - this field is the regional pack status flag.
                • -
              • Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.
                • -
              • Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
                • +The general tab contains the cultural settings of the pack. +
                  +
                • Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
                  • +
                • Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
                  • +
                • Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'
                  • +
                • Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
                  • +
                • Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
                  • +
                • Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
                  • +
                • Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.
                  • +
                • Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.
                  • +
                • Enabled - this field is the regional pack status flag.
                  • +
                • Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.
                  • +
                • Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
                \ No newline at end of file Index: trunk/themes/inlink2/statistics.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/statistics.tpl (.../statistics.tpl) (revision 626) +++ trunk/themes/inlink2/statistics.tpl (.../statistics.tpl) (revision 2868) @@ -1,10 +1,10 @@ - - - - - - - +
                 : :  - -
                + + + + + +
                 : :  + +
                \ No newline at end of file Index: trunk/core/module_help/base_style_edit.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/base_style_edit.txt (.../base_style_edit.txt) (revision 1713) +++ trunk/core/module_help/base_style_edit.txt (.../base_style_edit.txt) (revision 2868) @@ -1,10 +1,10 @@ -Each block style has the following properties:
                -
                  -
                • Selector ID – internal, read-only ID of the selector.
                  • -
                • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
                  • -
                • Based On – the name of the base style, related to this block style.
                  • -
                • Name – the name of the block style, used for internal reference by the administrator.
                  • -
                • Description – this is a field for administrator’s notes about the style sheet.
                  • -
                • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
                  • -
                • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
                  • +Each block style has the following properties:
                  +
                    +
                  • Selector ID – internal, read-only ID of the selector.
                    • +
                  • Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
                    • +
                  • Based On – the name of the base style, related to this block style.
                    • +
                  • Name – the name of the block style, used for internal reference by the administrator.
                    • +
                  • Description – this is a field for administrator’s notes about the style sheet.
                    • +
                  • Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
                    • +
                  • Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
                  \ No newline at end of file Index: trunk/kernel/admin/include/help/reviews.txt =================================================================== diff -u -N -r1231 -r2868 --- trunk/kernel/admin/include/help/reviews.txt (.../reviews.txt) (revision 1231) +++ trunk/kernel/admin/include/help/reviews.txt (.../reviews.txt) (revision 2868) @@ -1,19 +1,19 @@ -

                  The Reviews section provides a consolidated view -of the reviews for all items across different modules. The -administrator can perform all of the basic functions directly in this -section, without locating the item that any given review belongs to. -One of the most common ways to use the Reviews section is to find -pending reviews. To do this, simply use the View menu to filter only -Pending reviews. -

                  -

                  In this section, you can Approve, Deny, Edit and -Delete reviews, as well as search for a specific review, no matter -what item it may belong to.

                  -

                  On the summary list, below the details of each -review there is a link to the item, to which the review belongs to. -Clicking on that link will allow the administrator to quickly edit -the parent item. When the administrator saves or cancels the item -changes, he or she will appear back in the Reviews section.

                  -

                  The section is divided into tabs, a tab for each -module installed on your system. Each tab retains its individual +

                  The Reviews section provides a consolidated view +of the reviews for all items across different modules. The +administrator can perform all of the basic functions directly in this +section, without locating the item that any given review belongs to. +One of the most common ways to use the Reviews section is to find +pending reviews. To do this, simply use the View menu to filter only +Pending reviews. +

                  +

                  In this section, you can Approve, Deny, Edit and +Delete reviews, as well as search for a specific review, no matter +what item it may belong to.

                  +

                  On the summary list, below the details of each +review there is a link to the item, to which the review belongs to. +Clicking on that link will allow the administrator to quickly edit +the parent item. When the administrator saves or cancels the item +changes, he or she will appear back in the Reviews section.

                  +

                  The section is divided into tabs, a tab for each +module installed on your system. Each tab retains its individual filter settings (Search keyword and View menu options).

                  \ No newline at end of file Index: trunk/themes/inlink2/list_cats.tpl =================================================================== diff -u -N -r1355 -r2868 --- trunk/themes/inlink2/list_cats.tpl (.../list_cats.tpl) (revision 1355) +++ trunk/themes/inlink2/list_cats.tpl (.../list_cats.tpl) (revision 2868) @@ -1,9 +1,9 @@ -

                  -"> -" class="cat"> - - -(/)
                  -
                  - -

                  +

                  +"> +" class="cat"> + + +(/)
                  +
                  + +

                  Index: trunk/themes/inlink2/modify_link.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/modify_link.tpl (.../modify_link.tpl) (revision 29) +++ trunk/themes/inlink2/modify_link.tpl (.../modify_link.tpl) (revision 2868) @@ -1,14 +1,14 @@ - - - - - - -
                  - - -
                  - - - + + + + + + +
                  + + +
                  + + + \ No newline at end of file Index: trunk/themes/inlink2/show_cats.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/show_cats.tpl (.../show_cats.tpl) (revision 29) +++ trunk/themes/inlink2/show_cats.tpl (.../show_cats.tpl) (revision 2868) @@ -1,16 +1,16 @@ - - - - - - - -

                  - - - -                   		- - -
                  - + + + + + + + +

                  + + + +                   		+ + +
                  + Index: trunk/themes/inlink2/custom_field.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/custom_field.tpl (.../custom_field.tpl) (revision 29) +++ trunk/themes/inlink2/custom_field.tpl (.../custom_field.tpl) (revision 2868) @@ -1,5 +1,5 @@ -
        - :
        + :
        - - - -
        - - -
        - - - - - - - + + + + + + +
        + + +
        + + + + + + + \ No newline at end of file Index: trunk/kernel/module_help/email_messages_edit.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/kernel/module_help/email_messages_edit.txt (.../email_messages_edit.txt) (revision 1716) +++ trunk/kernel/module_help/email_messages_edit.txt (.../email_messages_edit.txt) (revision 2868) @@ -1,8 +1,8 @@ -An email notification has the following fields: -
          -
        • Subject - this field contains the subject of the email notification.
          • -
        • Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
          • -
        • Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
          • -
        • Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> '.
          • -
        +An email notification has the following fields: +
          +
        • Subject - this field contains the subject of the email notification.
          • +
        • Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
          • +
        • Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
          • +
        • Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> '.
          • +
        The other columns in the list display the information about the event itself, which cannot be changed from the Regional settings section. To change the event properties, please go to the appropriate Events section, for example, Structure & Data -> Email Setting for In-portal platform category events. \ No newline at end of file Index: trunk/kernel/admin/include/help/user_banlist.txt =================================================================== diff -u -N -r1231 -r2868 --- trunk/kernel/admin/include/help/user_banlist.txt (.../user_banlist.txt) (revision 1231) +++ trunk/kernel/admin/include/help/user_banlist.txt (.../user_banlist.txt) (revision 2868) @@ -1,77 +1,77 @@ -

        This section allows the administrator to manage -the ban rules. The ban rules are used to filter user registrations -automatically, using various criteria. This is useful, when the site -administrator does not want a certain person, or a group of people, -to register on the In-portal site, however does not want to review -all registrations manually. This seemly straightforward task is -actually very difficult to do on the Internet. There is no -bulletproof way to identify a real person when they are registering -online; one has only indirect information to rely on � the -information that the person submits or has the ability to change. -Therefore, the idea behind banning is to create as many accurate -rules as possible that would filter out the majority of the unwanted -people.

        -

        This section also allows the administrator to -execute selected rules on the existing user database, banning the -users, which fall under those rules, but registered before the rules -where created and enforced.

        -

        When a new user registration is banned, the -visitor will receive an error message, and will not be able to -complete the registration. When an existing user is banned, they are -disabled.

        -

        The ban rule form has the following fields:

        -
          -

        • Rule Type � this - field designated the type of the rule. There are �Deny� rules - and �Allow� rules. The �Deny� rules, when they match a user - record, deny the registration. The �Allow� rules work in the - opposite way � when such rule is matched with a user record, the - user registration is allowed. The conflicts between allow and deny - rules are resolved based on the priority of each rule. (Conflicts - occur, when one or more opposite rules match the same user record).

          -

        • Item Field � this - drop down selects the User attribute, which is going to be matched - against the rule value.

          -

        • Field Comparison � - this drop down selects the type of the match, in other words the - comparison operation that will be performed. The match types do - what their names mean. Please use the �Any� type with extra - caution. It does not perform a comparison, but instructs the rule - to match all user records, regardless of any other options.

          -

        • Field Value* - this - field contains the value that will be used when matching the rule.

          -

        • Error Tag � this - field contains the name of the language variable that contains the - text, which will be displayed on the front-end, when a user - registration is denied due to this rule. Leave it blank, if you do - not want to provide an error message. Please keep in mind, that it - is theoretically possible that a rule will deny registration to a - person you did not intend to be banned, and design the error - messages accordingly. -

          -

        • Priority � this - field sets the priority of the rule, which is used for resolving the - conflicts when more than one rule is matched with the same user - record.

          -

        • Status � this - field enables and disabled rules.

          -
        -

        For example, you as a site administrator, notice -that there is a person that registers with �ACME Corp� words in -their user name, email, first and last names, etc. You suspect that -this user is trying to advertise their company, and you want to -prevent them from using your site in that way. However, you are not -sure, what exact names this person will use in the future � all you -know is that they want to include the company name � ACME. In this -situation, you would set up three ban rules. They will be of type -�Deny�, on Item fields �User name�, �First name� and -�Last name�, using Field Comparison �Contains�, and the Field -Value �ACME�. Optionally, you can create a message for that -person, for example �Sorry, no ACME advertising allowed on this -site.� The priority is not important in this case, because a match -on any of the three fields is sufficient to ban the user. The status -should be set to �Enabled�. Now, that person will not be able to -register with the word �ACME� in their user name, or first or -last name. You may also want to run these three rules on your -existing user database, in case you missed some of the previous +

        This section allows the administrator to manage +the ban rules. The ban rules are used to filter user registrations +automatically, using various criteria. This is useful, when the site +administrator does not want a certain person, or a group of people, +to register on the In-portal site, however does not want to review +all registrations manually. This seemly straightforward task is +actually very difficult to do on the Internet. There is no +bulletproof way to identify a real person when they are registering +online; one has only indirect information to rely on � the +information that the person submits or has the ability to change. +Therefore, the idea behind banning is to create as many accurate +rules as possible that would filter out the majority of the unwanted +people.

        +

        This section also allows the administrator to +execute selected rules on the existing user database, banning the +users, which fall under those rules, but registered before the rules +where created and enforced.

        +

        When a new user registration is banned, the +visitor will receive an error message, and will not be able to +complete the registration. When an existing user is banned, they are +disabled.

        +

        The ban rule form has the following fields:

        +
          +

        • Rule Type � this + field designated the type of the rule. There are �Deny� rules + and �Allow� rules. The �Deny� rules, when they match a user + record, deny the registration. The �Allow� rules work in the + opposite way � when such rule is matched with a user record, the + user registration is allowed. The conflicts between allow and deny + rules are resolved based on the priority of each rule. (Conflicts + occur, when one or more opposite rules match the same user record).

          +

        • Item Field � this + drop down selects the User attribute, which is going to be matched + against the rule value.

          +

        • Field Comparison � + this drop down selects the type of the match, in other words the + comparison operation that will be performed. The match types do + what their names mean. Please use the �Any� type with extra + caution. It does not perform a comparison, but instructs the rule + to match all user records, regardless of any other options.

          +

        • Field Value* - this + field contains the value that will be used when matching the rule.

          +

        • Error Tag � this + field contains the name of the language variable that contains the + text, which will be displayed on the front-end, when a user + registration is denied due to this rule. Leave it blank, if you do + not want to provide an error message. Please keep in mind, that it + is theoretically possible that a rule will deny registration to a + person you did not intend to be banned, and design the error + messages accordingly. +

          +

        • Priority � this + field sets the priority of the rule, which is used for resolving the + conflicts when more than one rule is matched with the same user + record.

          +

        • Status � this + field enables and disabled rules.

          +
        +

        For example, you as a site administrator, notice +that there is a person that registers with �ACME Corp� words in +their user name, email, first and last names, etc. You suspect that +this user is trying to advertise their company, and you want to +prevent them from using your site in that way. However, you are not +sure, what exact names this person will use in the future � all you +know is that they want to include the company name � ACME. In this +situation, you would set up three ban rules. They will be of type +�Deny�, on Item fields �User name�, �First name� and +�Last name�, using Field Comparison �Contains�, and the Field +Value �ACME�. Optionally, you can create a message for that +person, for example �Sorry, no ACME advertising allowed on this +site.� The priority is not important in this case, because a match +on any of the three fields is sufficient to ban the user. The status +should be set to �Enabled�. Now, that person will not be able to +register with the word �ACME� in their user name, or first or +last name. You may also want to run these three rules on your +existing user database, in case you missed some of the previous registrations by that user.

        \ No newline at end of file Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/connector.php =================================================================== diff -u -N -r2816 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/connector.php (.../connector.php) (revision 2816) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/connector.php (.../connector.php) (revision 2868) @@ -1,112 +1,97 @@ - \ No newline at end of file + Index: trunk/themes/inlink2/registration.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/registration.tpl (.../registration.tpl) (revision 29) +++ trunk/themes/inlink2/registration.tpl (.../registration.tpl) (revision 2868) @@ -1,105 +1,105 @@ - - - - - - -
        - - -
        - - - "> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
         *
         *
         *
         *
         *
         *
        * ()
        -
        -
        - " class="button"> - " class="button"> -
        - - - - + + + + + + +
        + + +
        + + + "> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
         *
         *
         *
         *
         *
         *
        * ()
        +
        +
        + " class="button"> + " class="button"> +
        + + + + \ No newline at end of file Index: trunk/themes/inlink2/modify.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/modify.tpl (.../modify.tpl) (revision 29) +++ trunk/themes/inlink2/modify.tpl (.../modify.tpl) (revision 2868) @@ -1,74 +1,74 @@ - - - - - - -
        -
        - - - - - - - - -
        - - - - - - "> - - - - -
        - - (): ()
        -
        -

        - - - - - - - "> -

        -
        -
        - -
        -
          - -
        -
        - -
        - -
        - - - - + + + + + + +
        +
        + + + + + + + + +
        + + + + + + "> + + + + +
        + + (): ()
        +
        +

        + + + + + + + "> +

        +
        +
        + +
        +
          + +
        +
        + +
        + +
        + + + + \ No newline at end of file Index: trunk/themes/inlink2/send_password.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/send_password.tpl (.../send_password.tpl) (revision 650) +++ trunk/themes/inlink2/send_password.tpl (.../send_password.tpl) (revision 2868) @@ -1,59 +1,59 @@ - - - - - - -
        - - -
        -
        "> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        - (*)


        *
         
        *
         
          - " class="button"> -



        -
        - - - - + + + + + + +
        + + +
        +
        "> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        + (*)


        *
         
        *
         
          + " class="button"> +



        +
        + + + + \ No newline at end of file Index: trunk/themes/inlink2/show_related_cats.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/show_related_cats.tpl (.../show_related_cats.tpl) (revision 29) +++ trunk/themes/inlink2/show_related_cats.tpl (.../show_related_cats.tpl) (revision 2868) @@ -1,16 +1,16 @@ - - - - - -
        - - () -
        - - - -
        -
        -
        + + + + + +
        + + () +
        + + + +
        +
        +
        \ No newline at end of file Index: trunk/themes/inlink2/send_password_confirm.tpl =================================================================== diff -u -N -r650 -r2868 --- trunk/themes/inlink2/send_password_confirm.tpl (.../send_password_confirm.tpl) (revision 650) +++ trunk/themes/inlink2/send_password_confirm.tpl (.../send_password_confirm.tpl) (revision 2868) @@ -1,33 +1,33 @@ - - - - - - -
        - - -
        - - -"> - - - -
        -
        -

        - - - -

        -
        - " class="button"> - - -
        - - - - + + + + + + +
        + + +
        + + +"> + + + +
        +
        +

        + + + +

        +
        + " class="button"> + + +
        + + + + \ No newline at end of file Index: trunk/themes/inlink2/menu_navigation.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/menu_navigation.tpl (.../menu_navigation.tpl) (revision 626) +++ trunk/themes/inlink2/menu_navigation.tpl (.../menu_navigation.tpl) (revision 2868) @@ -1,27 +1,27 @@ -

        - - -  " class="nav-top-txt"> - | - - - | - - - | - - - | - - - | - - - - -
        -

        - - - - +

        + + +  " class="nav-top-txt"> + | + + + | + + + | + + + | + + + | + + + + +
        +

        + + + + Index: trunk/core/module_help/block_styles.txt =================================================================== diff -u -N -r1713 -r2868 --- trunk/core/module_help/block_styles.txt (.../block_styles.txt) (revision 1713) +++ trunk/core/module_help/block_styles.txt (.../block_styles.txt) (revision 2868) @@ -1,3 +1,3 @@ -Block Styles
        -
        +Block Styles
        +
        This tab lists all block styles of the style sheet. Block styles describe the look & feel of specific content blocks to be used in a theme. Each block style is based on a base style (see next tab); sometimes it overrides one or more properties of the base style. You can add, modify and delete block styles, as well as clone and reset them to the base styles they are related to. \ No newline at end of file Index: trunk/kernel/admin_templates/incs/colorselector.js =================================================================== diff -u -N -r1566 -r2868 --- trunk/kernel/admin_templates/incs/colorselector.js (.../colorselector.js) (revision 1566) +++ trunk/kernel/admin_templates/incs/colorselector.js (.../colorselector.js) (revision 2868) @@ -1,104 +1,104 @@ - // color Selector - - var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF'; - var $color_selector_field = ''; - - function InitColorSelector() - { - var $selector = document.getElementById('colorSelector_div'); - - if( !isset($selector) ) - { - var $selector = document.createElement('DIV'); - $selector.id = 'colorSelector_div'; - $selector.className = 'table_color1'; - $selector.style.width = '178px'; - $selector.style.borderWidth = '1px'; - $selector.style.borderColor = '#000000'; - $selector.style.display = 'none'; - $selector.style.position = 'absolute'; - $selector.style.borderStyle = 'solid'; - - var $s_table = document.createElement('TABLE'); - $s_table.id = 'colorSelector'; - $selector.appendChild($s_table); - document.body.appendChild($selector); - - var oTable = document.getElementById('colorSelector'); - var iCounter = 0; - aColors = aColors.split(','); - - while(iCounter < aColors.length) - { - var oRow = oTable.insertRow(-1); - for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++) - { - var $cell = document.createElement('TD'); - $cell.innerHTML = '
        '; - $cell.onmouseover = this.colorMouseOver; - $cell.onmouseout = this.colorMouseOut; - $cell.onclick = this.colorClick; - $cell.setAttribute('ColorIndex', iCounter); - var oDiv=oRow.insertCell(-1).appendChild($cell); - }; - } - } - } - - function updateColor($event,$color_id) - { - document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value; - } - - function colorMouseOver($e) - { - if(!$e) $e = window.event; - //print_pre(this); - this.parentNode.style.backgroundColor = '#C8D3E2'; - this.parentNode.style.borderColor = '#7196CC'; - - } - - function colorMouseOut($e, $element) - { - if(!$e) $e = window.event; - if(!$element) $element = this; - $element.parentNode.style.backgroundColor = '#F6F6F6'; - $element.parentNode.style.borderColor = '#F6F6F6'; - } - - function colorClick($e) - { - if(!$e) $e = window.event; - var $color = aColors[ this.getAttribute('ColorIndex') ]; - - document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color; - document.getElementById($color_selector_field).value = '#' + $color; - document.getElementById('colorSelector_div').style.display = 'none'; - - colorMouseOut($e, this); - } - - function openColorSelector($e, $field) - { - $color_selector_field = $field; - var $div = document.getElementById('colorSelector_div'); - - var posx = 0; - var posy = 0; - if (!$e) var $e = window.event; - if ($e.pageX || $e.pageY) - { - posx = $e.pageX; - posy = $e.pageY; - } - else if ($e.clientX || $e.clientY) - { - posx = $e.clientX + document.body.scrollLeft; - posy = $e.clientY + document.body.scrollTop; - } - - $div.style.left = posx; - $div.style.top = posy; - $div.style.display = 'block'; - } + // color Selector + + var aColors = '000000,993300,333300,003300,003366,000080,333399,333333,800000,FF6600,808000,808080,008080,0000FF,666699,808080,FF0000,FF9900,99CC00,339966,33CCCC,3366FF,800080,999999,FF00FF,FFCC00,FFFF00,00FF00,00FFFF,00CCFF,993366,C0C0C0,FF99CC,FFCC99,FFFF99,CCFFCC,CCFFFF,99CCFF,CC99FF,FFFFFF'; + var $color_selector_field = ''; + + function InitColorSelector() + { + var $selector = document.getElementById('colorSelector_div'); + + if( !isset($selector) ) + { + var $selector = document.createElement('DIV'); + $selector.id = 'colorSelector_div'; + $selector.className = 'table_color1'; + $selector.style.width = '178px'; + $selector.style.borderWidth = '1px'; + $selector.style.borderColor = '#000000'; + $selector.style.display = 'none'; + $selector.style.position = 'absolute'; + $selector.style.borderStyle = 'solid'; + + var $s_table = document.createElement('TABLE'); + $s_table.id = 'colorSelector'; + $selector.appendChild($s_table); + document.body.appendChild($selector); + + var oTable = document.getElementById('colorSelector'); + var iCounter = 0; + aColors = aColors.split(','); + + while(iCounter < aColors.length) + { + var oRow = oTable.insertRow(-1); + for(var i = 0; i < 8 && iCounter < aColors.length; i++, iCounter++) + { + var $cell = document.createElement('TD'); + $cell.innerHTML = '
        '; + $cell.onmouseover = this.colorMouseOver; + $cell.onmouseout = this.colorMouseOut; + $cell.onclick = this.colorClick; + $cell.setAttribute('ColorIndex', iCounter); + var oDiv=oRow.insertCell(-1).appendChild($cell); + }; + } + } + } + + function updateColor($event,$color_id) + { + document.getElementById('color_'+$color_id).style.backgroundColor = document.getElementById($color_id).value; + } + + function colorMouseOver($e) + { + if(!$e) $e = window.event; + //print_pre(this); + this.parentNode.style.backgroundColor = '#C8D3E2'; + this.parentNode.style.borderColor = '#7196CC'; + + } + + function colorMouseOut($e, $element) + { + if(!$e) $e = window.event; + if(!$element) $element = this; + $element.parentNode.style.backgroundColor = '#F6F6F6'; + $element.parentNode.style.borderColor = '#F6F6F6'; + } + + function colorClick($e) + { + if(!$e) $e = window.event; + var $color = aColors[ this.getAttribute('ColorIndex') ]; + + document.getElementById('color_'+$color_selector_field).style.backgroundColor = $color; + document.getElementById($color_selector_field).value = '#' + $color; + document.getElementById('colorSelector_div').style.display = 'none'; + + colorMouseOut($e, this); + } + + function openColorSelector($e, $field) + { + $color_selector_field = $field; + var $div = document.getElementById('colorSelector_div'); + + var posx = 0; + var posy = 0; + if (!$e) var $e = window.event; + if ($e.pageX || $e.pageY) + { + posx = $e.pageX; + posy = $e.pageY; + } + else if ($e.clientX || $e.clientY) + { + posx = $e.clientX + document.body.scrollLeft; + posy = $e.clientY + document.body.scrollTop; + } + + $div.style.left = posx; + $div.style.top = posy; + $div.style.display = 'block'; + } Index: trunk/core/module_help/languages_edit_general.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/core/module_help/languages_edit_general.txt (.../languages_edit_general.txt) (revision 1716) +++ trunk/core/module_help/languages_edit_general.txt (.../languages_edit_general.txt) (revision 2868) @@ -1,14 +1,14 @@ -The general tab contains the cultural settings of the pack. -
          -
        • Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
          • -
        • Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
          • -
        • Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'
          • -
        • Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
          • -
        • Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
          • -
        • Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
          • -
        • Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.
          • -
        • Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.
          • -
        • Enabled - this field is the regional pack status flag.
          • -
        • Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.
          • -
        • Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
          • +The general tab contains the cultural settings of the pack. +
            +
          • Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
            • +
          • Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
            • +
          • Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'
            • +
          • Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
            • +
          • Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
            • +
          • Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
            • +
          • Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.
            • +
          • Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.
            • +
          • Enabled - this field is the regional pack status flag.
            • +
          • Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.
            • +
          • Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
          \ No newline at end of file Index: trunk/kernel/admin/include/help/reports.txt =================================================================== diff -u -N -r1231 -r2868 --- trunk/kernel/admin/include/help/reports.txt (.../reports.txt) (revision 1231) +++ trunk/kernel/admin/include/help/reports.txt (.../reports.txt) (revision 2868) @@ -1,6 +1,6 @@ -

          This section provides the statistical information -about your In-portal platform and all installed modules. All of the -values are automatically updated as you enter the section. If you -want to see the most current value of any statistics, please use the -�Refresh� button (icon with two revolving green arrows). +

          This section provides the statistical information +about your In-portal platform and all installed modules. All of the +values are automatically updated as you enter the section. If you +want to see the most current value of any statistics, please use the +�Refresh� button (icon with two revolving green arrows).

          \ No newline at end of file Index: trunk/kernel/module_help/phrase_edit.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/kernel/module_help/phrase_edit.txt (.../phrase_edit.txt) (revision 1716) +++ trunk/kernel/module_help/phrase_edit.txt (.../phrase_edit.txt) (revision 2868) @@ -1,7 +1,7 @@ -A label has the following fields: -
            -
          • Phrase Id - this field is a read-only, unique and internal system language phrase ID.
            • -
          • Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
            • -
          • Value - this field contains the label value in the local language of the pack. That is where the translation goes.
            • -
          • Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism. There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button. As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
            • +A label has the following fields: +
              +
            • Phrase Id - this field is a read-only, unique and internal system language phrase ID.
              • +
            • Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
              • +
            • Value - this field contains the label value in the local language of the pack. That is where the translation goes.
              • +
            • Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism. There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button. As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
            \ No newline at end of file Index: trunk/themes/inlink2/sub_pages.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/sub_pages.tpl (.../sub_pages.tpl) (revision 29) +++ trunk/themes/inlink2/sub_pages.tpl (.../sub_pages.tpl) (revision 2868) @@ -1,26 +1,26 @@ - - - - - - -
            - -
            - - - - - - - - - -
            - - - - - - + + + + + + +
            + +
            + + + + + + + + + +
            + + + + + + \ No newline at end of file Index: trunk/themes/inlink2/display_cat_search.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/display_cat_search.tpl (.../display_cat_search.tpl) (revision 29) +++ trunk/themes/inlink2/display_cat_search.tpl (.../display_cat_search.tpl) (revision 2868) @@ -1,39 +1,39 @@ - - - - - - -
            -
            - - - - - - - - - - - - - - -
            - () -
            -
            -
              - -
            -
            - -
            - -
            - - - - + + + + + + +
            +
            + + + + + + + + + + + + + + +
            + () +
            +
            +
              + +
            +
            + +
            + +
            + + + + \ No newline at end of file Index: trunk/themes/inlink2/list_feature_links.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/list_feature_links.tpl (.../list_feature_links.tpl) (revision 29) +++ trunk/themes/inlink2/list_feature_links.tpl (.../list_feature_links.tpl) (revision 2868) @@ -1,38 +1,38 @@ -
          • -"> - - - - - - - - - - -
            - - -(: -, : -, : -, : -, : -, : -, : ) - - -
            - -" class="link-review">  -" class="link-rate">  - - - - - - -" class="link-review"> -  - -
            • +
          • +"> + + + + + + + - + + +
            + + +(: +, : +, : +, : +, : +, : +, : ) + + +
            + +" class="link-review">  +" class="link-rate">  + + + + + + +" class="link-review"> +  + +


            • \ No newline at end of file Index: trunk/themes/inlink2/error.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/error.tpl (.../error.tpl) (revision 29) +++ trunk/themes/inlink2/error.tpl (.../error.tpl) (revision 2868) @@ -1,31 +1,31 @@ - - - - - - -
            - - -
            - - -" > - - - -
            -
            -

            - - - -

            -
            - " class="button"> -
            - - - - + + + + + + +
            + + +
            + + +" > + + + +
            +
            +

            + + + +

            +
            + " class="button"> +
            + + + + \ No newline at end of file Index: trunk/admin/email/log.txt =================================================================== diff -u -N -r13 -r2868 --- trunk/admin/email/log.txt (.../log.txt) (revision 13) +++ trunk/admin/email/log.txt (.../log.txt) (revision 2868) @@ -41,7 +41,6 @@ Content-Transfer-Encoding: 8bit Welcome to In-portal! - Your user registration has been approved. Your user name is "tester". -------=815a5d07052bc2bc0b14d9351c5547b7-- @@ -97,7 +96,6 @@ Content-Transfer-Encoding: 8bit Welcome to In-portal! - Your user registration has been approved. Your user name is "tester". -------=93ebb602f383fb1cf52028f8c504f67a-- @@ -153,7 +151,6 @@ Content-Transfer-Encoding: 8bit Welcome to In-portal! - Your user registration has been approved. Your user name is "tester". -------=0ad82d0b8cba7e49a2027040a212e108-- @@ -209,7 +206,6 @@ Content-Transfer-Encoding: 8bit Welcome to In-portal! - Your user registration has been approved. Your user name is "tester". -------=f0a151bf3e5de4733cdfeb983e31b217-- Index: trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/basexml.php =================================================================== diff -u -N -r1415 -r2868 --- trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/basexml.php (.../basexml.php) (revision 1415) +++ trunk/admin/editor/cmseditor/editor/filemanager/browser/default/connectors/php/basexml.php (.../basexml.php) (revision 2868) @@ -1,4 +1,4 @@ - - - - - - -

            Stylesheets
            -
            -            The “Stylesheets” section of the Console lists all available style sheets. Here you can add, modify and delete the style sheets, as well as enable, disable and clone them. Remember, that to take effect, a style sheet must be enabled and attached to a theme.

            + + + + + + +

            Stylesheets
            +
            +            The “Stylesheets” section of the Console lists all available style sheets. Here you can add, modify and delete the style sheets, as well as enable, disable and clone them. Remember, that to take effect, a style sheet must be enabled and attached to a theme.

            When editing base and block styles, please don’t forget that the changes do not take effect until the entire style sheet is saved.

            \ No newline at end of file Index: trunk/themes/inlink2/list_links.tpl =================================================================== diff -u -N -r626 -r2868 --- trunk/themes/inlink2/list_links.tpl (.../list_links.tpl) (revision 626) +++ trunk/themes/inlink2/list_links.tpl (.../list_links.tpl) (revision 2868) @@ -1,38 +1,38 @@ -
          • -"> - - - - - - - - - - -
            - - -(: - -, : -, : -, : -, : -) - - -
            - -" class="link-review">  -" class="link-rate">  - - - - - - -" class="link-review"> -  - -
            • +
          • +"> + + + + + + + - + + +
            + + +(: + +, : +, : +, : +, : +) + + +
            + +" class="link-review">  +" class="link-rate">  + + + + + + +" class="link-review"> +  + +


            • \ No newline at end of file Index: trunk/themes/inlink2/box_suggest.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/box_suggest.tpl (.../box_suggest.tpl) (revision 29) +++ trunk/themes/inlink2/box_suggest.tpl (.../box_suggest.tpl) (revision 2868) @@ -1,20 +1,20 @@ - - "> - - - - - - - - - - - - - -
            -
            - -
            - " class="button">
            + + "> + + + + + + + + + + + + + +
            +
            + +
            + " class="button">
            Index: trunk/themes/inlink2/add_link.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/add_link.tpl (.../add_link.tpl) (revision 29) +++ trunk/themes/inlink2/add_link.tpl (.../add_link.tpl) (revision 2868) @@ -1,14 +1,14 @@ - - - - - - -
            - - -
            - - - + + + + + + +
            + + +
            + + + \ No newline at end of file Index: trunk/core/module_help/email_messages_edit.txt =================================================================== diff -u -N -r1716 -r2868 --- trunk/core/module_help/email_messages_edit.txt (.../email_messages_edit.txt) (revision 1716) +++ trunk/core/module_help/email_messages_edit.txt (.../email_messages_edit.txt) (revision 2868) @@ -1,8 +1,8 @@ -An email notification has the following fields: -
              -
            • Subject - this field contains the subject of the email notification.
              • -
            • Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
              • -
            • Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
              • -
            • Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> '.
              • -
            +An email notification has the following fields: +
              +
            • Subject - this field contains the subject of the email notification.
              • +
            • Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
              • +
            • Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
              • +
            • Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> '.
              • +
            The other columns in the list display the information about the event itself, which cannot be changed from the Regional settings section. To change the event properties, please go to the appropriate Events section, for example, Structure & Data -> Email Setting for In-portal platform category events. \ No newline at end of file Index: trunk/themes/inlink2/rate.tpl =================================================================== diff -u -N -r29 -r2868 --- trunk/themes/inlink2/rate.tpl (.../rate.tpl) (revision 29) +++ trunk/themes/inlink2/rate.tpl (.../rate.tpl) (revision 2868) @@ -1,18 +1,18 @@ - - - - - - -
            - - -
            - - - - - - - + + + + + + +
            + + +
            + + + + + + + \ No newline at end of file