Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_properties.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_properties.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_properties.txt	(revision 5668)
@@ -0,0 +1,14 @@
+This tab controls module-specific category properties. The contents of the tab depends on the modules installed.<br/>
+In-newz module adds the following properties:
+RSS Feed Properties:
+<ul>
+<li>Source URL � this fields controls the RSS source URL used for populating current category with articles. The field also accepts multiple RSS source URLs separated by commas.
+<li>Update Interval � the time interval used for parsing the RSS source and populating the category with articles. 
+</ul>
+RSS Feed Articles Expiration
+<ul>
+<li>Default Expiration � the default expiration time of articles imported through RSS into the category.
+<li>Expiration Check Interval � the time interval controlling the frequency of checking the expired articles for the purpose of deleting it (see Delete Expired checkbox below)
+<li>Delete Expired � the checkbox controls whether expired articles should be completely deleted from the system, or simply marked as archived (expired).
+</ul>
+As of the current version, In-link, In-commerce and In-bulletin modules do not have any category-level properties.
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_images.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_images.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_images.txt	(revision 5668)
@@ -0,0 +1,15 @@
+
+  This tab contains all images associated with the category. To create a new image, click on the �New' button (the icon like the Windows GIF icon with a little sun). This will open a new page where you fill out the image details. 
+<ul>
+  <li> Image ID � a read-only field, the internal system ID of the image, guaranteed to be unique throughout the system. It is blank when a new image is created. 
+  <li> Name � this field contains the image name, used in In-tags to designate the image. 
+  <li> Alt Value � this field contains the text value, which will be displayed in the �alt' tag of the image on the front end, inside the page HTML code, and when a mouse pointer is hovered over the image (in Internet Explorer). 
+  <li> Status � this field contains the status of the image, enabled or disabled. 
+  <li> Primary � this flag designates the primary image. There can be only one primary image per list (for one category). When you check this box on an image, the previous primary image is unset (if there is more than one image in the list). 
+  <li> Priority � this field contains the numerical priority of the image. 
+  <li> Thumbnail location (upload from PC) � Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the �in-portal/kernel/images' directory. 
+  <li> Thumbnail location (remote URL) � Here you can enter a remote URL address of an image. It will be linked from the remote server. 
+  <li> Same As Thumbnail � This check box sets the full-size image to be the same as the thumbnail image. When this option is checked, you cannot upload a full-size image. 
+  <li> Thumbnail location (upload from PC) - Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the �in-portal/kernel/images' directory. 
+  <li> Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_images.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_images.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_images.txt	(revision 5668)
@@ -0,0 +1,15 @@
+
+  This tab contains all images associated with the category. To create a new image, click on the �New' button (the icon like the Windows GIF icon with a little sun). This will open a new page where you fill out the image details. 
+<ul>
+  <li> Image ID � a read-only field, the internal system ID of the image, guaranteed to be unique throughout the system. It is blank when a new image is created. 
+  <li> Name � this field contains the image name, used in In-tags to designate the image. 
+  <li> Alt Value � this field contains the text value, which will be displayed in the �alt' tag of the image on the front end, inside the page HTML code, and when a mouse pointer is hovered over the image (in Internet Explorer). 
+  <li> Status � this field contains the status of the image, enabled or disabled. 
+  <li> Primary � this flag designates the primary image. There can be only one primary image per list (for one category). When you check this box on an image, the previous primary image is unset (if there is more than one image in the list). 
+  <li> Priority � this field contains the numerical priority of the image. 
+  <li> Thumbnail location (upload from PC) � Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the �in-portal/kernel/images' directory. 
+  <li> Thumbnail location (remote URL) � Here you can enter a remote URL address of an image. It will be linked from the remote server. 
+  <li> Same As Thumbnail � This check box sets the full-size image to be the same as the thumbnail image. When this option is checked, you cannot upload a full-size image. 
+  <li> Thumbnail location (upload from PC) - Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the �in-portal/kernel/images' directory. 
+  <li> Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_relations.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_relations.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_relations.txt	(revision 5668)
@@ -0,0 +1,8 @@
+This page contains a list of all relations of this category. To create a new relation, click the �New' button (two opposite green arrows with a sun). This will pop up a category picker, where you can choose one category. 
+<ul>
+  <li> Relation ID � a read-only field, the internal system ID of the relation, guaranteed to be unique throughout the system. It is blank when a new relation is created. 
+  <li> Item � a read only field, the destination item type �category'. Categories can only be related to categories. 
+  <li> Type � �reciprocal' designates a two-way relation, and �one way' � a one-way relation. 
+  <li> Enabled � the status flag of the relation. 
+  <li> Priority � the numerical priority of the relation.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.3.2/core/kernel/utility/debugger/debugger.css
===================================================================
diff -u -r5659 -r5668
--- branches/unlabeled/unlabeled-1.3.2/core/kernel/utility/debugger/debugger.css	(.../debugger.css)	(revision 5659)
+++ branches/unlabeled/unlabeled-1.3.2/core/kernel/utility/debugger/debugger.css	(.../debugger.css)	(revision 5668)
@@ -81,8 +81,8 @@
 }
 
 .dbg-button {
-	background-color: Menu;
-	border: 1px solid Menu;
+	background-color: #D4D0C8;
+	border: 1px solid #D4D0C8;
 }
 
 .dbg-button:hover {
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.1.90/kernel/admin/include/help/editcategory_permissions.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.1.90/kernel/admin/include/help/editcategory_custom.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.1.90/kernel/admin/include/help/editcategory_images.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.1.90/kernel/admin/include/help/editcategory_relations.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_relations.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_relations.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_relations.txt	(revision 5668)
@@ -0,0 +1,8 @@
+This page contains a list of all relations of this category. To create a new relation, click the �New' button (two opposite green arrows with a sun). This will pop up a category picker, where you can choose one category. 
+<ul>
+  <li> Relation ID � a read-only field, the internal system ID of the relation, guaranteed to be unique throughout the system. It is blank when a new relation is created. 
+  <li> Item � a read only field, the destination item type �category'. Categories can only be related to categories. 
+  <li> Type � �reciprocal' designates a two-way relation, and �one way' � a one-way relation. 
+  <li> Enabled � the status flag of the relation. 
+  <li> Priority � the numerical priority of the relation.
+</ul>
\ No newline at end of file
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.3.2/kernel/admin/include/help/editcategory_general.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Fisheye: Tag 5668 refers to a dead (removed) revision in file `branches/unlabeled/unlabeled-1.2.2/kernel/admin/include/help/editcategory_items.txt'.
Fisheye: No comparison available.  Pass `N' to diff?
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_edit.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_edit.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_edit.txt	(revision 5668)
@@ -0,0 +1,17 @@
+<ul>
+<li> Category ID - this is a read-only field that displays the internal system ID. It is of a small importance, other than the fact that it's a truly unique identifier of a category � there can never be two categories with the same ID. 
+<li> Name - this is the category name 
+<li> Description - this is the category description 
+<li> Automatic Directory Name � specifies whether the Directory Name used for mod_rewrite should be generated automatically from the category name, or entered manually. If checked, the Directory Name will be generated from the category name, replacing all special characters ( !@#$%^&*()+|\=-~`{}][:��;,./?>< ) by the underscore character (�_�), and all multiple underscores with a single underscore. If the resulting name ends with an underscore followed by number, an additional letter will be appended, since the names ending with a number are reserved for system use. The resulting name will also be checked for uniqueness, and if it�s not unique, additional letters will be appended to the end of the name
+<li>Directory Name � the directory name used for the URL generation when using mod_rewrite. The field is disabled if Automatic Directory Name is On. If Automatic Directory Name is Off, the administrator may enter the directory name manually, however it will still be checked for uniqueness, special characters and whether it ends with a number. In such cases the Directory Name will be automatically corrected before saving.
+<li>Category Temple � the template file name used for displaying category index (item listing). If not explicitly set, the template filename will be inherited from the parent category, or taken from the URL if present. When used in conjunction with mod_rewrite, the template name will be eliminated from the URLs pointing to the category index, deduced by matching the category name from the URLs. The Category Template may be set to different values for different categories providing the ability to adjust the design of different categories.
+<li>Item Template � the template file name used for displaying items (such as links, products, articles etc) inside the given category. Works exactly the same way as the Category Template, except it�s used for URLs pointing to an item. 
+
+<li> �Editor' � this icon that looks like a notepad and a pen, will pop up the online HTML editor for the category description. It will only work if the Enable HTML check box is checked. 
+<li> Status � this is the category status 
+<li> New � this is the control for the �New' flag. The �auto' setting will let the system set the �new' flag automatically, based on the number of days since its creation and a setting; �always' will enable the flag, and �never' will disable it. 
+<li> Editor's Pick � this sets the Editor's pick flag 
+<li> Created on � this is the creation date. It can be either entered directly into the field, or you can use the calendar tool to select a date. The �Calendar' button is an icon to the right of the field that looks like a date book page. To the right of the �Calendar' button there is a hint that shows the current date format. This format may change, if a different Regional package is activated. 
+<li> META keywords � this field contains the META keywords that will be displayed on the front end of the In-portal site, in the special HTML �meta� tags. These particular keywords will be displayed when the current category is entered. 
+META description � similar to the META keywords, but for the META description HTML tag. Both are useful for search engine recognition of the page, as well as alternative descriptions of the category that will not be visible to a human visitor.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_edit.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_edit.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_edit.txt	(revision 5668)
@@ -0,0 +1,17 @@
+<ul>
+<li> Category ID - this is a read-only field that displays the internal system ID. It is of a small importance, other than the fact that it's a truly unique identifier of a category � there can never be two categories with the same ID. 
+<li> Name - this is the category name 
+<li> Description - this is the category description 
+<li> Automatic Directory Name � specifies whether the Directory Name used for mod_rewrite should be generated automatically from the category name, or entered manually. If checked, the Directory Name will be generated from the category name, replacing all special characters ( !@#$%^&*()+|\=-~`{}][:��;,./?>< ) by the underscore character (�_�), and all multiple underscores with a single underscore. If the resulting name ends with an underscore followed by number, an additional letter will be appended, since the names ending with a number are reserved for system use. The resulting name will also be checked for uniqueness, and if it�s not unique, additional letters will be appended to the end of the name
+<li>Directory Name � the directory name used for the URL generation when using mod_rewrite. The field is disabled if Automatic Directory Name is On. If Automatic Directory Name is Off, the administrator may enter the directory name manually, however it will still be checked for uniqueness, special characters and whether it ends with a number. In such cases the Directory Name will be automatically corrected before saving.
+<li>Category Temple � the template file name used for displaying category index (item listing). If not explicitly set, the template filename will be inherited from the parent category, or taken from the URL if present. When used in conjunction with mod_rewrite, the template name will be eliminated from the URLs pointing to the category index, deduced by matching the category name from the URLs. The Category Template may be set to different values for different categories providing the ability to adjust the design of different categories.
+<li>Item Template � the template file name used for displaying items (such as links, products, articles etc) inside the given category. Works exactly the same way as the Category Template, except it�s used for URLs pointing to an item. 
+
+<li> �Editor' � this icon that looks like a notepad and a pen, will pop up the online HTML editor for the category description. It will only work if the Enable HTML check box is checked. 
+<li> Status � this is the category status 
+<li> New � this is the control for the �New' flag. The �auto' setting will let the system set the �new' flag automatically, based on the number of days since its creation and a setting; �always' will enable the flag, and �never' will disable it. 
+<li> Editor's Pick � this sets the Editor's pick flag 
+<li> Created on � this is the creation date. It can be either entered directly into the field, or you can use the calendar tool to select a date. The �Calendar' button is an icon to the right of the field that looks like a date book page. To the right of the �Calendar' button there is a hint that shows the current date format. This format may change, if a different Regional package is activated. 
+<li> META keywords � this field contains the META keywords that will be displayed on the front end of the In-portal site, in the special HTML �meta� tags. These particular keywords will be displayed when the current category is entered. 
+META description � similar to the META keywords, but for the META description HTML tag. Both are useful for search engine recognition of the page, as well as alternative descriptions of the category that will not be visible to a human visitor.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_permissions.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_permissions.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_permissions.txt	(revision 5668)
@@ -0,0 +1,10 @@
+This tab allows you to control the permissions of the current category. The first list displays all groups, which have permissions already associated with this category. If a group is not shown, that means that its permissions will be inherited from the parent category. To add a new group definition, click on the �New Permission' button (icon with a yellow lock and a little sun). A new page will pop-up, prompting you to select the group which you want to add. Only those groups will be shown which don't yet exist in the group list. 
+  Once you add or edit a group, you will be directed to the page defining the permissions. The permissions are broken down by type, one for the In-portal platform permissions, and one for each of the installed modules. The �Inherited' check box specifies that a particular permission is inherited from the parent, and therefore cannot be defined for this category. The �Access' check box shows whether a permission is set or unset in the current category. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the category � red means unset, and the green � set. This is especially useful in for the inherited permissions � you don't have to look up the parent category to find out what the value of a particular permission is. The last column, �Inherited From', shows the category name and full path that defines the permission for the current category. It may be an immediate parent, or any other grandparent category in the tree � all the way up to the �Home' category. The �Home' category does not have the inheritance options, since it is the highest category in the tree, and does not have any other category to inherit the settings from. The list of In-portal platform permissions is as follows: 
+<ul>
+  <li> View Category � controls whether a user can view the subcategories in this category. 
+  <li> Add Category � controls whether a user can add categories inside this category. 
+  <li> Delete Category � controls whether a user can delete categories inside this category. 
+  <li> Add Pending Category � controls whether a user can add categories inside this category, but in pending mode � awaiting administrator's approval before they become active. 
+  <li> Modify Category � controls whether a user can modify categories inside this category. 
+  <li> Allow favorites � controls whether a user can utilize the Favorites function on the items in this category. The favorites feature works like a bookmark � it allows users to mark the items they find useful, and they will be displayed in �My Favorites' section in their account on the front end.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_permissions.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_permissions.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_permissions.txt	(revision 5668)
@@ -0,0 +1,10 @@
+This tab allows you to control the permissions of the current category. The first list displays all groups, which have permissions already associated with this category. If a group is not shown, that means that its permissions will be inherited from the parent category. To add a new group definition, click on the �New Permission' button (icon with a yellow lock and a little sun). A new page will pop-up, prompting you to select the group which you want to add. Only those groups will be shown which don't yet exist in the group list. 
+  Once you add or edit a group, you will be directed to the page defining the permissions. The permissions are broken down by type, one for the In-portal platform permissions, and one for each of the installed modules. The �Inherited' check box specifies that a particular permission is inherited from the parent, and therefore cannot be defined for this category. The �Access' check box shows whether a permission is set or unset in the current category. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the category � red means unset, and the green � set. This is especially useful in for the inherited permissions � you don't have to look up the parent category to find out what the value of a particular permission is. The last column, �Inherited From', shows the category name and full path that defines the permission for the current category. It may be an immediate parent, or any other grandparent category in the tree � all the way up to the �Home' category. The �Home' category does not have the inheritance options, since it is the highest category in the tree, and does not have any other category to inherit the settings from. The list of In-portal platform permissions is as follows: 
+<ul>
+  <li> View Category � controls whether a user can view the subcategories in this category. 
+  <li> Add Category � controls whether a user can add categories inside this category. 
+  <li> Delete Category � controls whether a user can delete categories inside this category. 
+  <li> Add Pending Category � controls whether a user can add categories inside this category, but in pending mode � awaiting administrator's approval before they become active. 
+  <li> Modify Category � controls whether a user can modify categories inside this category. 
+  <li> Allow favorites � controls whether a user can utilize the Favorites function on the items in this category. The favorites feature works like a bookmark � it allows users to mark the items they find useful, and they will be displayed in �My Favorites' section in their account on the front end.
+</ul>
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_custom.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_custom.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_custom.txt	(revision 5668)
@@ -0,0 +1,2 @@
+The custom tab displays all custom fields defined for categories, and allows the administrator to edit them. The custom fields are set up on the Custom Settings page, described in the section V.2.1.5 of this manual. 
+  The only information that can be entered for a custom field is the "Value".
\ No newline at end of file
Index: branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_properties.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_properties.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/kernel/module_help/categories_properties.txt	(revision 5668)
@@ -0,0 +1,14 @@
+This tab controls module-specific category properties. The contents of the tab depends on the modules installed.<br/>
+In-newz module adds the following properties:
+RSS Feed Properties:
+<ul>
+<li>Source URL � this fields controls the RSS source URL used for populating current category with articles. The field also accepts multiple RSS source URLs separated by commas.
+<li>Update Interval � the time interval used for parsing the RSS source and populating the category with articles. 
+</ul>
+RSS Feed Articles Expiration
+<ul>
+<li>Default Expiration � the default expiration time of articles imported through RSS into the category.
+<li>Expiration Check Interval � the time interval controlling the frequency of checking the expired articles for the purpose of deleting it (see Delete Expired checkbox below)
+<li>Delete Expired � the checkbox controls whether expired articles should be completely deleted from the system, or simply marked as archived (expired).
+</ul>
+As of the current version, In-link, In-commerce and In-bulletin modules do not have any category-level properties.
Index: branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_custom.txt
===================================================================
diff -u
--- branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_custom.txt	(revision 0)
+++ branches/unlabeled/unlabeled-1.1.2/core/module_help/categories_custom.txt	(revision 5668)
@@ -0,0 +1,2 @@
+The custom tab displays all custom fields defined for categories, and allows the administrator to edit them. The custom fields are set up on the Custom Settings page, described in the section V.2.1.5 of this manual. 
+  The only information that can be entered for a custom field is the "Value".
\ No newline at end of file