+This section allows the administrator to manage the category custom fields. The category custom fields are useful when you need to store additional information about the categories. In the earlier example about a directory of cars, the categories may have such custom fields, as the engine displacement range, price range, years of manufacturing of the model, etc. All custom fields will be automatically used in the administrative console, in the Category Management section. You will need to edit the theme templates for them to appear on the front-end.
+<ul>
+ <li> Field Id this is a read-only field displaying the unique system ID of the custom field.
+ <li> Field Name sets the internal name of the custom field. This is the name you would use to refer to the custom field in the In-tags when designing templates.
+ <li> Field Label this is a read-only field, which displays the language variable name associated with the label of that field, and the value of the variable in the current language (after the colon). The label is used on the front end, and in the administrative console, to describe the field to the user who is entering information into it.
+ <li> Show on the general tab this setting controls whether the custom field will be also displayed on the General tab in the administrative console, when editing the categories. It is a short cut for frequently used custom fields. All settings below apply only when this is checked.
+ <li> Heading this field contains the language variable of the section heading, under which the field appear on the general tab.
+ <li> Field Prompt this field contains the language variable, which text will appear as the hint bind the field.
+ <li> Input Type this drop down allows the administrator to designate the type of the information stored in the custom field, by specifying the HTML control to be used on the General form.
+ <li> List of Values this field contains all choices for the above HTML controls of type radio button' or drop down'. The choices must be in the format: value1 = language variabe1, value2=language variable2. For example, to create a drop down with three choices (One, Two, Three) and their respective numerical values, this field would contain the following: 1=la_one,2=la_two,3=la_three).
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/configuration_custom.txt
+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
Property changes on: trunk/kernel/admin/include/help/editcategory_relations.txt
+This section will provide you with a page-by-page walkthrough of the administrative console of the In-portal platform, describing the purpose of each page and the fields on it.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/site.txt
+ 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
Property changes on: trunk/kernel/admin/include/help/editcategory_images.txt
+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
Property changes on: trunk/kernel/admin/include/help/user_list.txt
+This tab contains all images associated with the user. 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.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_images.txt
+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
Property changes on: trunk/kernel/admin/include/help/editcategory_custom.txt
+ This section lists all possible In-portal platform category events. Each event has a description, a type User' or Admin', a status Enabled', Front-end Only', and a From/To User'. The description hints about when the event occurs. The type indicates whether the email notification will be sent to the front-end user, or the administrator. The status Enabled' signifies that the email notifications for this event are enabled for both the front-end and the administrative console. The Front-end Only' status means that the notifications will be sent only when the event occurs on the front end. The Disabled' status means no notifications will be sent when this event occurs. The From/To User' field specifies the From' email for front-end user notifications, and the To' email for the administrative notifications. The other, matching pair of addresses (To' for the front, and From' for the admin) is automatically determined by the system based on who initiated the event. The event notification status can be changed by clicking on the toolbar buttons Enable' to enable the notification, Disable' to disable it, and Front Only' (icon with a monitor) to set to Front-end Only' status.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/configuration_email.txt
+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
Property changes on: trunk/kernel/admin/include/help/editcategory_permissions.txt
+The custom tab displays all custom fields defined for users, and allows the administrator to edit them. The custom fields are set up on the Custom Fields page, described in the section V.2.2.5 of this manual.
+ The only information that can be entered for a custom field is the "Value".
+
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_custom.txt
+The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it.
+ The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user red means unset, and the green set. This is especially useful in for the inherited permissions you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is.<br><br> The list of the administrative console permissions is as follows:
+<ul>
+ <li> Admin Login this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution.
+ <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
+ <li> Change User Profiles this permission will allow the user to view and change other users' profiles on the front end.
+ <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
+ <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
+ <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
+</ul>
+ The list of the front-end permissions is as follows:
+<ul>
+ <li> Allow Login this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to Pending' or Disabled'. The only difference is for users with administrative privileges Pending' or Disabled' user will not be able to log into the administrative console as well, regardless of their Admin Login' permission setting.
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_permissions.txt
+<li> Enable HTML? this check box enables or disables HTML code in the category name and the category description. When checked, it will render the HTML (for example, a <B> tag will actually make the text bold). When unchecked, it will display the HTML as regular text (the <B> tag will appear exactly as <B>'). This is very important, since some HTML tags can break the page layout, and in some instances can be a security weakness (the Java Script, for example).
+<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> 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
Property changes on: trunk/kernel/admin/include/help/editcategory_general.txt
+ <li> Username* - this field contains the unique user name.
+ <li> Password this field contains the user password. When editing an existing user, the password field will be blank. Leave it blank, if you do not want to change the password. For extra protection, nobody can see the user's existing password, including the administrator. The password can only be reset (either in this from, or from the front end, the Forgot Password' function.)
+ <li> Repeat Password this field is used when resetting the user's password. Please re-type the password entered in the field above. If the passwords don't match, an error will occur and you will not be able to save the form.
+ <li> First Name this field contains user's first name.
+ <li> Last Name this field contains user's last name.
+ <li> Email* - this field contains user's email address. It is a required field, because without it the user will not be able to reset their password and receive the system email notifications.
+ <li> Date of Birth* - this field contains the user's date of birth. It is a required field, due to United States COPPA regulations, which state that all persons under the age of 13 must obtain parental consent before submitting their personal information on a web site. For more information about COPPA, please visit <a href="http://www.ftc.gov/bcp/conline/pubs/buspubs/coppa.htm">http://www.ftc.gov/bcp/conline/pubs/buspubs/coppa.htm </a>. The date can be either entered manually, in accordance with the date format of the current regional package, or selected with the help of the calendar tool to the right of the field.
+ <li> Phone - this field contains user's phone number.
+ <li> Street - this field contains user's street address.
+ <li> City - this field contains user's city.
+ <li> State - this field contains user's state or province.
+ <li> Zip - this field contains user's postal code.
+ <li> Country - this field contains user's country.
+ <li> Status this flag contains the user's status enabled, disabled or pending.
+ <li> Created On - this field contains the date when the user was created. The date can be either entered manually, in accordance with the date format of the current regional package, or selected with the help of the calendar tool to the right of the field.
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_general.txt
+This tab allows the administrator to assign the user to one or more groups. It also lists all groups to which the user is currently assigned, along with the user count in each group.
+ To assign a new group, click on the Add User to Group' button (user icon with a green arrow to the right). This button will pop-up a group selector.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_groups.txt
+This tab lists all group members. It also allows to add a new member to the group and to remove the existing members. To add a new member, click on the Add User to Group' button. A new page with a list of all users will pop up.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/editgroup_users.txt
+This tab lists all items owned by the user. Each item's name and type is displayed. It is not possible to add or remove items on this tab it must be done through the "Edit" form of each specific item. The link on the item's name will pop up the "Edit" form as a short cut.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_items.txt
+ <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>
Property changes on: trunk/kernel/admin/include/help/edituser_image.txt
+This section allows the administrator to define the default values for various In-portal platform settings.
+<ul>
+ <li> Order categories by this setting specifies the default primary sort order for category listings. It applies both on the front end, and in the administrative console in the catalog. The first dropdown allows to select the field (an attribute of the category element), and the second dropdown the direction.
+ <li> And then by this setting specifies the default secondary sort order. It is set in the same way as the primary, and used when the primary order values are ambiguous. For example, when the primary sort value is Category Name', the secondary order will be used to sort among categories with the same name.
+ <li> Number of categories per page specifies the default number of categories shown per page. This value applies both to the front end and to the administrative console. In the latter, this value can be changed for each session through the View menu.
+ <li> Categories Per Page (Shortlist) this setting is similar to the Number of categories per page', but it applies to the front end, short category lists only. It can be overridden by setting the tag attributes in the appropriate templates.
+ <li> Number of days for a cat. to be NEW specifies the number of days, from the date of creation, during which the category will be automatically marked New' by the system. This setting will only apply to the categories with the New' flag set to Automatic'.
+ <li> Display editor PICKs above regular categories this setting will force all categories, marked as Editor's pick' to be displayed above the other categories, regardless of their priority or sort order. Among themselves, Editor's pick' categories will be sorted according to the regular rules.
+ <li> Root category name (language variable) this setting specifies the name of the language variable which contains the name of the root category. By default, the root category name is Home' in English, and the label name is lu_rootcategory_name'. There is rarely a need to change the name of the variable since the name of the category itself can be simply changed by changing the value of the variable.
+ <li> Default META Keywords this field contains the default META keywords value, which is displayed on the home page, or whenever a category does not have them defined. For more information, see the section describing General Category settings - V.2.1.1.1.1 .
+ <li> Default META description - this field contains the default META description value, which is displayed on the home page, or whenever a category does not have them defined. For more information, see the section describing General Category settings - V.2.1.1.1.1 .
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/configure_categories.txt
+This section allows the administrator to configure the front end search options, and the advanced search options.
+ At the top, this section lists all fields, representing category attributes. Next to each field, there is a Simple Search' checkbox, which includes this field in the simple search query. By default, only the Name' and the Description' fields are included. In general, it makes sense to include only the fields, which may contain text in them, otherwise when a visitor searches for a text keyword, the non-textual fields will be not searchable. Next there is a Weight' text box, in which the administrator can designate the importance of each field during a search. The fields with a larger weight will be more important then the fields with the lower weight. This is used when calculating the category relevance to the search keyword, for sorting of the results. The last column is the Advanced Search' check. It designated whether a particular field should be displayed on the Advanced Search' page, and should the visitors be able to search on it. By default, all fields are included.
+ Below the list of fields are the Category Relevance settings.
+<ul>
+ <li> Increase importance if field contains a required keyword by this specifies the percentage by which the weight of a field will increase, when a required keyword is found in that field. A required keyword is one that is preceded with a +' in the search key phrase.
+ <li> Search Relevance depends on _ % keyword the percentage of relevance that comes from the keyword being found in that category.
+ <li> Search Relevance depends on _ % popularity - the percentage of relevance that is based on the category popularity.
+ <li> Search Relevance depends on _ % rating - the percentage of relevance that is based on the category rating.
+</ul>
+ Below, the same forms repeat for user fields and for category custom fields, along with their respective relevance settings. Some of the search settings are not used in the current version they are reserved for a future use.
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/configuration_search.txt
+The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it.
+ The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user red means unset, and the green set. This is especially useful in for the inherited permissions you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is.<br><br> The list of the administrative console permissions is as follows:
+<ul>
+ <li> Admin Login this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution.
+ <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
+ <li> Change User Profiles this permission will allow the user to view and change other users' profiles on the front end.
+ <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
+ <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
+ <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
+</ul>
+ The list of the front-end permissions is as follows:
+<ul>
+ <li> Allow Login this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to Pending' or Disabled'. The only difference is for users with administrative privileges Pending' or Disabled' user will not be able to log into the administrative console as well, regardless of their Admin Login' permission setting.
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/edituser_permission.txt
+The permissions tab allows the administrator to assign permissions to the group. This is the recommended way of managing user permissions.
+ The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The "Access" check box shows whether a permission is set or unset for the current group. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the group red means unset, and the green set. <br><br>The list of the administrative console permissions is as follows:
+<ul>
+<li> Admin Login this permission allows the group member to log in, and to use the administrative console. This permission should be assigned with caution.
+ <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
+ <li> Change User Profiles this permission will allow the group member to view and change other users' profiles on the front end.
+ <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
+ <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
+ <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
+</ul>
+ The list of the front-end permissions is as follows:
+<ul>
+ <li> Allow Login this permission will allow the group member to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to "Pending" or "Disabled". The only difference is for users with administrative privileges "Pending" or "Disabled" user will not be able to log into the administrative console as well, regardless of their "Admin Login" permission setting.
+</ul>
+
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/editgroup_permissions.txt
+The general tab lists all general group information.
+<ul>
+ <li> Group Name* - this field contains the required name of the group. Everywhere in the administrative console, the groups are referred to by their names. The group name must be unique.
+ <li> Comments this field contains notes, visible only to the administrator and only on this page. They are useful for keeping short descriptions about the group and its purpose.
+</ul>
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/editgroup_general.txt
-<li> Enable HTML? this check box enables or disables HTML code in the category name and the category description. When checked, it will render the HTML (for example, a <B> tag will actually make the text bold). When unchecked, it will display the HTML as regular text (the <B> tag will appear exactly as <B>'). This is very important, since some HTML tags can break the page layout, and in some instances can be a security weakness (the Java Script, for example).
-<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> 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
Property changes on: trunk/admin/help/topics/in-portal@editcategory_general.txt
-This section will provide you with a page-by-page walkthrough of the administrative console of the In-portal platform, describing the purpose of each page and the fields on it.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@site.txt
-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
Property changes on: trunk/admin/help/topics/in-portal@user_list.txt
-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
Property changes on: trunk/admin/help/topics/in-portal@editcategory_relations.txt
-The custom tab displays all custom fields defined for users, and allows the administrator to edit them. The custom fields are set up on the Custom Fields page, described in the section V.2.2.5 of this manual.
- The only information that can be entered for a custom field is the "Value".
-
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_custom.txt
- <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>
Property changes on: trunk/admin/help/topics/in-portal@edituser_image.txt
- 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
Property changes on: trunk/admin/help/topics/in-portal@editcategory_images.txt
-This tab allows the administrator to assign the user to one or more groups. It also lists all groups to which the user is currently assigned, along with the user count in each group.
- To assign a new group, click on the Add User to Group' button (user icon with a green arrow to the right). This button will pop-up a group selector.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_groups.txt
-The general tab lists all general group information.
-<ul>
- <li> Group Name* - this field contains the required name of the group. Everywhere in the administrative console, the groups are referred to by their names. The group name must be unique.
- <li> Comments this field contains notes, visible only to the administrator and only on this page. They are useful for keeping short descriptions about the group and its purpose.
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@editgroup_general.txt
-The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it.
- The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user red means unset, and the green set. This is especially useful in for the inherited permissions you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is.<br><br> The list of the administrative console permissions is as follows:
-<ul>
- <li> Admin Login this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution.
- <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
- <li> Change User Profiles this permission will allow the user to view and change other users' profiles on the front end.
- <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
- <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
- <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
-</ul>
- The list of the front-end permissions is as follows:
-<ul>
- <li> Allow Login this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to Pending' or Disabled'. The only difference is for users with administrative privileges Pending' or Disabled' user will not be able to log into the administrative console as well, regardless of their Admin Login' permission setting.
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_permissions.txt
-This tab lists all items owned by the user. Each item's name and type is displayed. It is not possible to add or remove items on this tab it must be done through the "Edit" form of each specific item. The link on the item's name will pop up the "Edit" form as a short cut.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_items.txt
-This tab lists all group members. It also allows to add a new member to the group and to remove the existing members. To add a new member, click on the Add User to Group' button. A new page with a list of all users will pop up.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@editgroup_users.txt
-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
Property changes on: trunk/admin/help/topics/in-portal@editcategory_custom.txt
-This section allows the administrator to define the default values for various In-portal platform settings.
-<ul>
- <li> Order categories by this setting specifies the default primary sort order for category listings. It applies both on the front end, and in the administrative console in the catalog. The first dropdown allows to select the field (an attribute of the category element), and the second dropdown the direction.
- <li> And then by this setting specifies the default secondary sort order. It is set in the same way as the primary, and used when the primary order values are ambiguous. For example, when the primary sort value is Category Name', the secondary order will be used to sort among categories with the same name.
- <li> Number of categories per page specifies the default number of categories shown per page. This value applies both to the front end and to the administrative console. In the latter, this value can be changed for each session through the View menu.
- <li> Categories Per Page (Shortlist) this setting is similar to the Number of categories per page', but it applies to the front end, short category lists only. It can be overridden by setting the tag attributes in the appropriate templates.
- <li> Number of days for a cat. to be NEW specifies the number of days, from the date of creation, during which the category will be automatically marked New' by the system. This setting will only apply to the categories with the New' flag set to Automatic'.
- <li> Display editor PICKs above regular categories this setting will force all categories, marked as Editor's pick' to be displayed above the other categories, regardless of their priority or sort order. Among themselves, Editor's pick' categories will be sorted according to the regular rules.
- <li> Root category name (language variable) this setting specifies the name of the language variable which contains the name of the root category. By default, the root category name is Home' in English, and the label name is lu_rootcategory_name'. There is rarely a need to change the name of the variable since the name of the category itself can be simply changed by changing the value of the variable.
- <li> Default META Keywords this field contains the default META keywords value, which is displayed on the home page, or whenever a category does not have them defined. For more information, see the section describing General Category settings - V.2.1.1.1.1 .
- <li> Default META description - this field contains the default META description value, which is displayed on the home page, or whenever a category does not have them defined. For more information, see the section describing General Category settings - V.2.1.1.1.1 .
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@configure_categories.txt
-This section allows the administrator to configure the front end search options, and the advanced search options.
- At the top, this section lists all fields, representing category attributes. Next to each field, there is a Simple Search' checkbox, which includes this field in the simple search query. By default, only the Name' and the Description' fields are included. In general, it makes sense to include only the fields, which may contain text in them, otherwise when a visitor searches for a text keyword, the non-textual fields will be not searchable. Next there is a Weight' text box, in which the administrator can designate the importance of each field during a search. The fields with a larger weight will be more important then the fields with the lower weight. This is used when calculating the category relevance to the search keyword, for sorting of the results. The last column is the Advanced Search' check. It designated whether a particular field should be displayed on the Advanced Search' page, and should the visitors be able to search on it. By default, all fields are included.
- Below the list of fields are the Category Relevance settings.
-<ul>
- <li> Increase importance if field contains a required keyword by this specifies the percentage by which the weight of a field will increase, when a required keyword is found in that field. A required keyword is one that is preceded with a +' in the search key phrase.
- <li> Search Relevance depends on _ % keyword the percentage of relevance that comes from the keyword being found in that category.
- <li> Search Relevance depends on _ % popularity - the percentage of relevance that is based on the category popularity.
- <li> Search Relevance depends on _ % rating - the percentage of relevance that is based on the category rating.
-</ul>
- Below, the same forms repeat for user fields and for category custom fields, along with their respective relevance settings. Some of the search settings are not used in the current version they are reserved for a future use.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@configuration_search.txt
- <li> Username* - this field contains the unique user name.
- <li> Password this field contains the user password. When editing an existing user, the password field will be blank. Leave it blank, if you do not want to change the password. For extra protection, nobody can see the user's existing password, including the administrator. The password can only be reset (either in this from, or from the front end, the Forgot Password' function.)
- <li> Repeat Password this field is used when resetting the user's password. Please re-type the password entered in the field above. If the passwords don't match, an error will occur and you will not be able to save the form.
- <li> First Name this field contains user's first name.
- <li> Last Name this field contains user's last name.
- <li> Email* - this field contains user's email address. It is a required field, because without it the user will not be able to reset their password and receive the system email notifications.
- <li> Date of Birth* - this field contains the user's date of birth. It is a required field, due to United States COPPA regulations, which state that all persons under the age of 13 must obtain parental consent before submitting their personal information on a web site. For more information about COPPA, please visit <a href="http://www.ftc.gov/bcp/conline/pubs/buspubs/coppa.htm">http://www.ftc.gov/bcp/conline/pubs/buspubs/coppa.htm </a>. The date can be either entered manually, in accordance with the date format of the current regional package, or selected with the help of the calendar tool to the right of the field.
- <li> Phone - this field contains user's phone number.
- <li> Street - this field contains user's street address.
- <li> City - this field contains user's city.
- <li> State - this field contains user's state or province.
- <li> Zip - this field contains user's postal code.
- <li> Country - this field contains user's country.
- <li> Status this flag contains the user's status enabled, disabled or pending.
- <li> Created On - this field contains the date when the user was created. The date can be either entered manually, in accordance with the date format of the current regional package, or selected with the help of the calendar tool to the right of the field.
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_general.txt
-This section allows the administrator to manage the category custom fields. The category custom fields are useful when you need to store additional information about the categories. In the earlier example about a directory of cars, the categories may have such custom fields, as the engine displacement range, price range, years of manufacturing of the model, etc. All custom fields will be automatically used in the administrative console, in the Category Management section. You will need to edit the theme templates for them to appear on the front-end.
-<ul>
- <li> Field Id this is a read-only field displaying the unique system ID of the custom field.
- <li> Field Name sets the internal name of the custom field. This is the name you would use to refer to the custom field in the In-tags when designing templates.
- <li> Field Label this is a read-only field, which displays the language variable name associated with the label of that field, and the value of the variable in the current language (after the colon). The label is used on the front end, and in the administrative console, to describe the field to the user who is entering information into it.
- <li> Show on the general tab this setting controls whether the custom field will be also displayed on the General tab in the administrative console, when editing the categories. It is a short cut for frequently used custom fields. All settings below apply only when this is checked.
- <li> Heading this field contains the language variable of the section heading, under which the field appear on the general tab.
- <li> Field Prompt this field contains the language variable, which text will appear as the hint bind the field.
- <li> Input Type this drop down allows the administrator to designate the type of the information stored in the custom field, by specifying the HTML control to be used on the General form.
- <li> List of Values this field contains all choices for the above HTML controls of type radio button' or drop down'. The choices must be in the format: value1 = language variabe1, value2=language variable2. For example, to create a drop down with three choices (One, Two, Three) and their respective numerical values, this field would contain the following: 1=la_one,2=la_two,3=la_three).
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@configuration_custom.txt
-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
Property changes on: trunk/admin/help/topics/in-portal@editcategory_permissions.txt
- This section lists all possible In-portal platform category events. Each event has a description, a type User' or Admin', a status Enabled', Front-end Only', and a From/To User'. The description hints about when the event occurs. The type indicates whether the email notification will be sent to the front-end user, or the administrator. The status Enabled' signifies that the email notifications for this event are enabled for both the front-end and the administrative console. The Front-end Only' status means that the notifications will be sent only when the event occurs on the front end. The Disabled' status means no notifications will be sent when this event occurs. The From/To User' field specifies the From' email for front-end user notifications, and the To' email for the administrative notifications. The other, matching pair of addresses (To' for the front, and From' for the admin) is automatically determined by the system based on who initiated the event. The event notification status can be changed by clicking on the toolbar buttons Enable' to enable the notification, Disable' to disable it, and Front Only' (icon with a monitor) to set to Front-end Only' status.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@configuration_email.txt
-The permissions tab allows the administrator to assign individual permissions to the user. This is recommended only for exceptional situations, as it complicates user permission management. The standard way of assigning permissions, is to configure a group with the desired set of permissions, and then assign the user to it.
- The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The Inherited' check box specifies that a particular permission is inherited from a group that this user belongs to, and therefore cannot be defined for this user. The Access' check box shows whether a permission is set or unset for the current user. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the user red means unset, and the green set. This is especially useful in for the inherited permissions you do not have to look up all of the groups this user belongs to, to find out what the value of a particular permission is.<br><br> The list of the administrative console permissions is as follows:
-<ul>
- <li> Admin Login this permission allows the user to log in, and to use the administrative console. This permission should be assigned with caution.
- <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
- <li> Change User Profiles this permission will allow the user to view and change other users' profiles on the front end.
- <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
- <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
- <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
-</ul>
- The list of the front-end permissions is as follows:
-<ul>
- <li> Allow Login this permission will allow a registered user to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to Pending' or Disabled'. The only difference is for users with administrative privileges Pending' or Disabled' user will not be able to log into the administrative console as well, regardless of their Admin Login' permission setting.
-</ul>
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_permission.txt
-The permissions tab allows the administrator to assign permissions to the group. This is the recommended way of managing user permissions.
- The permissions are broken down by type, one for the In-portal administrative console permissions, and one for the front-end. The "Access" check box shows whether a permission is set or unset for the current group. Next to the check box, you will also see a green or a red circle. These circles indicate the active permission state for the group red means unset, and the green set. <br><br>The list of the administrative console permissions is as follows:
-<ul>
-<li> Admin Login this permission allows the group member to log in, and to use the administrative console. This permission should be assigned with caution.
- <li> Append phpinfo to all pages (Debug) All permissions, marked with (debug) are used for testing purposes when the code has been modified. They are not necessary, and sometimes distracting, for the daily usage of the console. This permission will display the PHP info page at the top of each page.
- <li> Change User Profiles this permission will allow the group member to view and change other users' profiles on the front end.
- <li> Display Item List Queries (Debug) this debug permission will display the SQL queries above on each list page, after each list operation is performed.
- <li> Display Item Queries (Debug) this debug permission will display the SQL queries for all other actions.
- <li> Show Language Tags this permission will show undefined language variables in the administrative console as links. The link will open up a pop-up for creation of that language variable in the current regional pack. This is a useful permission for enhancing and debugging translations.
-</ul>
- The list of the front-end permissions is as follows:
-<ul>
- <li> Allow Login this permission will allow the group member to log into the front end of the In-portal site. It is equivalent, for all intents and purposes, to setting a front-end only user's status to "Pending" or "Disabled". The only difference is for users with administrative privileges "Pending" or "Disabled" user will not be able to log into the administrative console as well, regardless of their "Admin Login" permission setting.
-</ul>
-
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@editgroup_permissions.txt
-This tab contains all images associated with the user. 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.
\ No newline at end of file
Property changes on: trunk/admin/help/topics/in-portal@edituser_images.txt