Index: branches/RC/core/module_help/dummy
===================================================================
diff -u -N
--- branches/RC/core/module_help/dummy (revision 8929)
+++ branches/RC/core/module_help/dummy (revision 0)
@@ -1 +0,0 @@
\ No newline at end of file
Index: branches/RC/core/module_help/base_style_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/base_style_edit.txt (revision 8929)
+++ branches/RC/core/module_help/base_style_edit.txt (revision 0)
@@ -1,10 +0,0 @@
-Each block style has the following properties:
-
- - Selector ID – internal, read-only ID of the selector.
- - Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
- - Based On – the name of the base style, related to this block style.
- - Name – the name of the block style, used for internal reference by the administrator.
- - Description – this is a field for administrator’s notes about the style sheet.
- - Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
- - Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
-
\ No newline at end of file
Index: branches/RC/core/module_help/block_style_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/block_style_edit.txt (revision 8929)
+++ branches/RC/core/module_help/block_style_edit.txt (revision 0)
@@ -1,10 +0,0 @@
-Each block style has the following properties:
-
- - Selector ID – internal, read-only ID of the selector.
- - Selector Name – the CSS name of the selector. All custom selectors usually start with a “.”, and HTML-specific selectors start with the element name, such as BODY, TABLE, TD, P, etc. The selector name is used in the “class” attributes of the HTML elements inside theme templates. Selectors that describe entire groups of elements (BODY, for example, describes the page body) are applied automatically.
- - Based On – the name of the base style, related to this block style.
- - Name – the name of the block style, used for internal reference by the administrator.
- - Description – this is a field for administrator’s notes about the style sheet.
- - Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
- - Style – this is the actual definition of the style for this selector. Clicking on the Editor icon next to the field label will bring up a pop-up window, which contains all of the style’s properties, which can be modified here. Once you are done with your changes and hit Save to close the window, you can see the actual CSS definition, and preview how the base style looks to the right.
-
\ No newline at end of file
Index: branches/RC/core/module_help/styles_list.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/styles_list.txt (revision 8929)
+++ branches/RC/core/module_help/styles_list.txt (revision 0)
@@ -1,14 +0,0 @@
-
-
-
-
-
-
-Stylesheets
-
-The “Stylesheets” section of the Console lists all available style sheets. Here you can add, modify and delete the style sheets, as well as enable, disable and clone them. Remember, that to take effect, a style sheet must be enabled and attached to a theme.
-When editing base and block styles, please don’t forget that the changes do not take effect until the entire style sheet is saved.
\ No newline at end of file
Index: branches/RC/core/module_help/base_styles.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/base_styles.txt (revision 8929)
+++ branches/RC/core/module_help/base_styles.txt (revision 0)
@@ -1,9 +0,0 @@
-
-
-
-
-
-Base Styles
-
-This tab lists all base styles of the style sheet. The base styles have exactly the same properties as the block styles (see above). They are also managed in the same way, and with the same forms, only there is no option to reset to base style for obvious reasons.
-The base styles define how the general page elements look, as opposed to specific content block styles.
\ No newline at end of file
Index: branches/RC/core/module_help/block_styles.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/block_styles.txt (revision 8929)
+++ branches/RC/core/module_help/block_styles.txt (revision 0)
@@ -1,3 +0,0 @@
-Block Styles
-
-This tab lists all block styles of the style sheet. Block styles describe the look & feel of specific content blocks to be used in a theme. Each block style is based on a base style (see next tab); sometimes it overrides one or more properties of the base style. You can add, modify and delete block styles, as well as clone and reset them to the base styles they are related to.
\ No newline at end of file
Index: branches/RC/core/module_help/stylesheets_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/stylesheets_edit.txt (revision 8929)
+++ branches/RC/core/module_help/stylesheets_edit.txt (revision 0)
@@ -1,10 +0,0 @@
-General
-
-The style sheet edit form contains the following fields:
-
- - Stylesheet ID – internal, read-only system ID of the style sheet.
- - Name – administrator-assigned friendly name of the style sheet. It is used to attach it to a theme, and it is not displayed anywhere on the front end.
- - Description – this is a field for administrator’s notes about the style sheet.
- - Advanced CSS – this field contains advanced CSS instructions, per CSS 2.1 specifications. It is optional.
- - Enabled – this checkbox controls whether the style sheet is enabled or disabled.
-
\ No newline at end of file
Index: branches/RC/core/module_help/events_list.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/events_list.txt (revision 8929)
+++ branches/RC/core/module_help/events_list.txt (revision 0)
@@ -1 +0,0 @@
- This tab contains the texts for email notifications sent out by the system when specific events occur. It contains all notification texts for the In-portal platform and the installed modules.
\ No newline at end of file
Index: branches/RC/core/module_help/email_messages_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/email_messages_edit.txt (revision 8929)
+++ branches/RC/core/module_help/email_messages_edit.txt (revision 0)
@@ -1,8 +0,0 @@
-An email notification has the following fields:
-
- - Subject - this field contains the subject of the email notification.
- - Send Email As - This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
- - Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
- - Message -this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: 'Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> '.
-
-The other columns in the list display the information about the event itself, which cannot be changed from the Regional settings section. To change the event properties, please go to the appropriate Events section, for example, Structure & Data -> Email Setting for In-portal platform category events.
\ No newline at end of file
Index: branches/RC/core/module_help/phrase_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/phrase_edit.txt (revision 8929)
+++ branches/RC/core/module_help/phrase_edit.txt (revision 0)
@@ -1,7 +0,0 @@
-A label has the following fields:
-
- - Phrase Id - this field is a read-only, unique and internal system language phrase ID.
- - Label - this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix 'lu_', and all labels to be used in the administrative console start with the prefix 'la_'. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
- - Value - this field contains the label value in the local language of the pack. That is where the translation goes.
- - Phrase Type - this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism. There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button. As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
-
\ No newline at end of file
Index: branches/RC/core/module_help/import_language.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/import_language.txt (revision 8929)
+++ branches/RC/core/module_help/import_language.txt (revision 0)
@@ -1 +0,0 @@
-'Import a regional pack' button (globe icon with a yellow arrow pointing down) allows the administrator to install a new pack, or update an existing one. Each pack can be downloaded and stored as a file. The format of the file is XML, and the name of the language pertaining to the pack is built into the file. Therefore, it is not necessary to select a pack when performing an import � its name will be automatically determined from the pack file. When importing a pack file, the administrator will need to upload it from the local computer by using the Browse button. Then the administrator should choose what types of phrases should be imported � �Front-end', �Administrator', or �Both'. In this case, �Both' does not mean �Front-end' and �Administrator', but it means the phrases of the type �Both' (which are used on the front-end and in the administrative console). The option �Overwrite Existing Phrases' will cause a replacement of all current phrases which are also found in the pack file being imported. It will not delete the language phrases, which are not found in the file. It is recommended to uncheck this option, to preserve any customized language values you may have. At the end of the import, a page with the result will be displayed. If a language import fails, this is usually due to the fact that there are not sufficient directory privileges on the �in-portal' directory, and the platform cannot upload the file for temporary use.
\ No newline at end of file
Index: branches/RC/core/module_help/languages_edit_general.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/languages_edit_general.txt (revision 8929)
+++ branches/RC/core/module_help/languages_edit_general.txt (revision 0)
@@ -1,14 +0,0 @@
-The general tab contains the cultural settings of the pack.
-
- - Language Id - this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
- - Pack Name - this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
- - Local Name - this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to 'Deutsch.'
- - Icon URL - this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the 'in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
- - Date Format - this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
- - Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
- - Decimal Point - this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: '10.00' and in Europe , as well as other locals, it is a comma: '10,00'.
- - Thousands Separator - this field contains the character that will be used for separating the thousands in numbers.
- - Enabled - this field is the regional pack status flag.
- - Primary - this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be - only one primary pack can exist in a system.
- - Copy Labels to this Language - this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
-
\ No newline at end of file
Index: branches/RC/core/module_help/export_language.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/export_language.txt (revision 8929)
+++ branches/RC/core/module_help/export_language.txt (revision 0)
@@ -1 +0,0 @@
-'Export' button (globe icon with a green arrow pointing out) allows the administrator to export a pack into a file. The file is first saved on the web server, and then it can be downloaded onto the workstation. The first field to enter is the file name. The full path is shown to the left of the file name input field. Please ensure that this directory is writable to the web server, otherwise the export will fail. Once the export is done, it will provide you with a link to download the file, or an error message, if the export failed.
\ No newline at end of file
Index: branches/RC/core/module_help/export_language_results.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/export_language_results.txt (revision 8929)
+++ branches/RC/core/module_help/export_language_results.txt (revision 0)
@@ -1 +0,0 @@
- 'Export' button (globe icon with a green arrow pointing out) allows the administrator to export a pack into a file. The file is first saved on the web server, and then it can be downloaded onto the workstation. The first field to enter is the file name. The full path is shown to the left of the file name input field. Please ensure that this directory is writable to the web server, otherwise the export will fail. Once the export is done, it will provide you with a link to download the file, or an error message, if the export failed.
\ No newline at end of file
Index: branches/RC/core/module_help/visits_list.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/visits_list.txt (revision 8929)
+++ branches/RC/core/module_help/visits_list.txt (revision 0)
@@ -1,24 +0,0 @@
-Visits (In-portal Platform)
-
-This section displays the log of all visits to your website. The visit is recorded when a user comes to your site. If the user logs in during his or her visit, the username will be updated in the visit record. If the user’s session expires during the visit, a new visit record will be created when he or she comes back to the site.
-The grid on this page displays the following columns:
-
- - Visit Date – Date and Time of the visit’s start
- - IP Address – the IP address of the visitor, as identified by the web server
- - Referrer – the URL the visitor came from, as reported by visitor’s browser
- - Username – the username of the visitor if he or she logs in during the visit
-
-
-Visits (with In-commerce installed)
-
-This section displays the log of all visits to your website. The visit is recorded when user comes to your site. If the user logs in during his or her visit, the username will be updated in the visit record. If the user’s session expires during the visit, a new visit record will be created when he or she comes back to the site.
-The grid on this page displays the following columns:
-
- - Visit Date – Date and Time of the visit’s start
- - IP Address – the IP address of the visitor, as identified by the web server
- - Referrer – the URL the visitor came from, as reported by visitor’s browser
- - Username – the username of the visitor if he or she logs in during the visit
- - Affiliate User – the username of affiliate who has referred the visitor
- - Order Total – the total amount of the orders made during this visit
- - Affiliate Commission – amount of affiliate commission received for the orders made during the visit
-
\ No newline at end of file
Index: branches/RC/core/module_help/languages_list.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/languages_list.txt (revision 8929)
+++ branches/RC/core/module_help/languages_list.txt (revision 0)
@@ -1 +0,0 @@
-This section allows the administrator to manage the regional packages (packs for short) of the In-portal platform. For more information about the packs, please read the section Concepts & Customization -> In-Portal Concepts -> Languages & Regional Settings of product manual.
\ No newline at end of file
Index: branches/RC/core/module_help/phrases_list.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/phrases_list.txt (revision 8929)
+++ branches/RC/core/module_help/phrases_list.txt (revision 0)
@@ -1,6 +0,0 @@
-This tab displays all language phrases, or labels, of the regional package being edited. A label has the following fields:
-• Phrase Id - this field is a read-only, unique and internal system language phrase ID.
-• Label – this field contains the system name of the language phrase. This name is used in all templates, and in some settings. For visual convenience, all labels to be used on the front-end start with the prefix ‘lu_’, and all labels to be used in the administrative console start with the prefix ‘la_’. The administrator may use their own conventions for naming the labels, however it is recommended to follow this naming rule to keep the regional pack compatible with the ones produced by Intechnic Corporation.
-• Value – this field contains the label value in the local language of the pack. That is where the translation goes.
-• Phrase Type – this field designates whether the label is to be used in the front-end, or in the administrative panel, or in both. Unlike the prefix of the label, this field must be set properly, as it drives the caching mechanism.
-
\ No newline at end of file
Index: branches/RC/core/module_help/tree_users.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/tree_users.txt (revision 8929)
+++ branches/RC/core/module_help/tree_users.txt (revision 0)
@@ -1,4 +0,0 @@
-This section lists all In-portal users. It allows
-managing users, setting primary group for a user, approving and
-disabling users, banning users and sending out mass emails to the
-users.
\ No newline at end of file
Index: branches/RC/core/module_help/tree_site.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/tree_site.txt (revision 8929)
+++ branches/RC/core/module_help/tree_site.txt (revision 0)
@@ -1 +0,0 @@
-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
Index: branches/RC/core/module_help/tree_root.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/tree_root.txt (revision 8929)
+++ branches/RC/core/module_help/tree_root.txt (revision 0)
@@ -1 +0,0 @@
-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
Index: branches/RC/core/module_help/tree_reports.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/tree_reports.txt (revision 8929)
+++ branches/RC/core/module_help/tree_reports.txt (revision 0)
@@ -1,6 +0,0 @@
-This section provides the statistical information
-about your In-portal platform and all installed modules. All of the
-values are automatically updated as you enter the section. If you
-want to see the most current value of any statistics, please use the
-�Refresh� button (icon with two revolving green arrows).
-
\ No newline at end of file
Index: branches/RC/core/module_help/tree_system.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/tree_system.txt (revision 8929)
+++ branches/RC/core/module_help/tree_system.txt (revision 0)
@@ -1,2 +0,0 @@
-This section allows the administrator to update
-the system settings of the In-portal platform.
\ No newline at end of file
Index: branches/RC/core/module_help/config_list_users.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/config_list_users.txt (revision 8929)
+++ branches/RC/core/module_help/config_list_users.txt (revision 0)
@@ -1,14 +0,0 @@
-This section allows the administrator to define the default values for various community settings.
-
-- Allow new user registration � this flag sets the user registration mode for the system. � Instant' setting will allow the visitors to register and become users automatically. This is useful for the web sites will a large amount of users, whose administrators do not want to control each individual user.
-
- Minimum user name length � this field sets the minimum user name length acceptable for the front-end registration. This restriction is not in effect when a user is created through the administrative console.
-
- Minimum password length � this field sets the minimum password length acceptable for the front-end registration. This restriction is not in effect when a user is created through the administrative console.
-
- Assign registered users to group � this dropdown allows to select the default group, to which all newly registered users are assigned.
-
- Assign users not logged in to group - this dropdown allows to select the default group, which manages permissions for all guests � site visitors who have not logged in.
-
- Assign mailing list subscribers to group - this dropdown allows to select the default group, to which all of the users who sign up for a mailing list will be assigned.
-
- Assign password automatically - this option will let the In-portal platform automatically generate random passwords for new users, and send them to the user in the registration email. This is a good way to verify the existence of a user's email � if they do not receive the email with the password, they will not be able to log in. The users will be able to set their own password later.
-
- Root Password � this field allows the administrator to change the root user's password. Leave this field blank to keep the existing password. Please remember that root user has the highest-level security access, and that his password cannot be retrieved. Please take extra caution not to forget or disclose this password.
-
- Verify Root Password � this field is used to verify the root password when it is being changed. If the text in this field does not match with the text in the �root password' field, the password will not be changed and an error will occur.
-
- Number of days to deny multiple votes from the same user - this setting controls how often the same user can vote on the same resource or item. For example, if you set it to 3 days, a user will not be able to vote on the same link for 3 days after their first vote.
-
- Number of days to deny multiple reviews from the same user - this setting controls how often the same user can create reviews for the same item. For example, if you set it to 3 days, a user will not be able to create a new review for the same link for 3 days after their first one.
-
\ No newline at end of file
Index: branches/RC/core/module_help/config_list_categories.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/config_list_categories.txt (revision 8929)
+++ branches/RC/core/module_help/config_list_categories.txt (revision 0)
@@ -1,12 +0,0 @@
-This section allows the administrator to define the default values for various In-portal platform settings.
-
- - 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.
-
- 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.
-
- 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.
-
- 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.
-
- 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'.
-
- 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.
-
- 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.
-
- 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 .
-
- 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 .
-
\ No newline at end of file
Index: branches/RC/core/module_help/config_list_general.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/config_list_general.txt (revision 8929)
+++ branches/RC/core/module_help/config_list_general.txt (revision 0)
@@ -1,55 +0,0 @@
-General
-
-
-
-This section allows the administrator to update the system settings of the In-portal platform.
-
-
-
-- Web address � this field contains the full directory path where your In-portal system is located. That�s the text that comes after the domain name in the URL where your In-portal system will be running. Example: if the URL is http://www.in-portal.net/demo/, then the full path is �/demo/�. Please note, that the beginning and the trailing slashes are required. If you are able to log into the administrative console and see this section, this means that this setting is setup correctly and does not need changes.
-
-
- Website name � this field contains the visual name of your site � it will appear in the browser title bar on the front end, and in your administration panel. You can choose anything you would like here.
-
-
- Session Management Method � this field specifies the session management mode for your In-portal system. The �Query String� method passes the session ID in all of the links on the site. This is the method, most compatible with the browsers, but it has a drawback � the session ID in the URL cannot be spidered by a search engine crawler. Therefore, if you want your site to be recognized by the search engines such as Google, MSN, etc. you will need to avoid this setting. The �Cookies� setting is the most search-engine friendly setting, but it will work only for browsers enabled with cookies. If a visitor comes to your site without the ability to store cookies, they will not be able to log in, or use any advanced functionality with this setting. The �Automatic� choice attempts to detect cookies and search engine spiders, and switch to the appropriate mode. Ideally, this would be the most convenient setting, however due to the unpublished search engine features, we cannot guarantee its accuracy.
-
-
- Session Inactivity Timeout (seconds) � this field contains your session expiration time. If a user (on the front-end or in the admin) is not active for longer then this period, they will be automatically logged out. This is an important security feature, and it is not recommended to change the session expiration to more than 3600 seconds (1 hour).
-
-
- Session Referrer Checking � this option controls if In-portal should check the HTTP referrer information and reject the session if the referrer does not match the current site. Keeping this option On increases the security of the session mechanism, but may prevent some users using Internet Security software (such as Norton) from accessing the parts of your In-portal-driven website that require login. This happens due to the fact that some of these software programs block the referrer information. In most programs, it is possible to disable blocking by adding the site to the �trusted� zone or by disabling the �block referrer� option, however it must be done on the individual computer of every user of the site.
-
-
- Enable Tag Caching � this setting controls the template caching mechanism utilized by the In-portal system. It is an experimental feature that will cache the HTML of a dynamically generated page and use it for a preset period instead of re-generating it on the fly for every user. The advantage of this function is a tremendous reduction in the server load (especially the database server), and a great improvement of the site load speeds, given the same web server hardware and software. The disadvantage is that some users will see information that may not be completely up to date (it could be delayed for up to an hour). If you have any further questions about this feature, or if you are experiencing unusual results while using this feature, please contact our support through My Account section located at http://www.intechnic.com/myaccount.
-
-
- Use non-blocking socket mode � this setting is applicable only to the Link Validation tool in the In-link module, for the current version of the In-portal Platform. Different versions of PHP scripting language require different socket settings for the timeout detection to work properly. During the installation, In-portal platform attempts to detect this automatically and set this setting to its appropriate value. In very rare occasions, this setting will need to be modified. For more information, or if you are experiencing a problem with the Link Validation tool, please contact our support through My Account section located at http://www.intechnic.com/myaccount.
-
-
- SSL Full URL � secure URL of the site, including the full path to the front-end. Normally it would be the same as regular URL, but in some shared hosting environments it may look like �https://secure_domain_name/~username/in-portal�. Please test the SSL URL using your browser and make sure your site is accessible by this URL before entering it here.
-
-
- Require SSL for login & checkout - if checked, the system will redirect all users to the secure URL for login & checkout process (if the In-commerce module is installed).
-
-
- Redirect to HTTP when SSL is not required - if �Require SSL for login & checkout� is turned on, this setting will force the system to redirect users back to regular (not secure) URL for all pages that do not require SSL. If the setting is off, the users will continue browsing using the SSL URL even when it�s not required. This option is useful for performance tuning on busy websites.
-
-
- Use mod_rewrite � enabling this option will instruct In-portal to generate URLs in a human-readable, search engine friendly format. This option may be enabled only for websites running on the Apache web server with the mod_rewrite module available and configured to allow directory-specific settings via .htaccess files. Please consult your hosting provider to make sure that your server meets these requirements. Before enabling this option, you should copy the .htaccess file from the /tools directory to the root directory of In-portal installation. Even when this option is enabled, In-portal will still recognize the default URL format and any old links or bookmarks will still work. However, with this option enabled, In-portal will always generate URLs in the new format when navigating the site, even if you started from an old-formatted URL.
-
- Use mod_rewrite with SSL � this option specifies whether the new URL format should be used when redirecting to an SSL connection (configured by Requre SSL for login & checkout option). Generally, this option should be off when using a shared SSL certificate.
-
- File not found (404) template � the template name relative to theme base folder, which will be displayed when requested URL is not found on the server.
-
- Use JavaScript redirection after login/logout (for IIS) - if set to on then JavaScript redirection is used instead of HTTP redirection after login, logout and session expiration. This setting is required when running In-portal on IIS web server, which is not able to set cookies and issue HTTP redirection in one request.
-
- Use Cron for Running Regular Events � controls if the system should use �cron� (a Linux daemon that executes scheduled commands) to perform regular activities such as checking the expiration dates, processing recurring orders etc. To setup In-portal to use the cron operation, the server should be configured to execute the �/tools/cron.php� script at least every 30 minutes. When this setting is off, the system will determine if there are any pending regular events to be executed on every page load (such as when navigating the site or accessing the administrative console). If such events are found, the system will execute them at that time.
- - Time zone of the server � this setting controls the time zone your server is located in. This refers to the system time that your server will report to In-portal scripts. You can find out this information from your server administrator.
-
-
- Time zone of the site � this setting controls your time zone. This will determine what time zone you will see on all of the date/time stamps issued by the system.
-
-
- Mail Server Address - You need to fill out this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal. Enter the full domain name of the mail server, without anything in front of if (e.g. �mail.mailserver.com�.) Leave it blank to use the default, built-in mail transport of your web server.
-
-
- Port (e.g. port 25) � this field contains the SMTP port of your external mail server. You need to fill out this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal.
-
-
- Server Required Authentication � the field tells In-portal if your SMTP server requires a user name and a password to send mail through it (this is common on the newer mail systems). You need to fill out this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal. In-portal currently supports plain text, cram-md5 and digest-md5 SMTP authentication schemes.
-
-
- Mail Server Username � this field contains the user name for your SMTP server. You need to fill out this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal.
-
-
- Mail Server Password � this field contains the password for your SMTP server. You need to fill out this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal.
-
-
- Send HTML email � this option will enable HTML email to be generated and sent by the In-portal system. You will also have an option to send plain text emails on individual basis, so it is recommended to leave the default setting � �On�.
-
-
- Additional Message Headers � this field contains additional email message headers that will be attached to all outgoing messages generated by In-portal. This is an advanced setting, and you need to know the exact formatting of the email headers to modify it.
-
-
- Messages from Site Admin are from � this field contains the email address that will appear as the FROM address on all automatically generated email messages. This should be a real email address to enable users to reply, and to receive failed message notifications. This field must be changed from its default value.
-
-
-
Index: branches/RC/core/module_help/categories_relations.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_relations.txt (revision 8929)
+++ branches/RC/core/module_help/categories_relations.txt (revision 0)
@@ -1,8 +0,0 @@
-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.
-
- - 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.
-
- Item � a read only field, the destination item type �category'. Categories can only be related to categories.
-
- Type � �reciprocal' designates a two-way relation, and �one way' � a one-way relation.
-
- Enabled � the status flag of the relation.
-
- Priority � the numerical priority of the relation.
-
\ No newline at end of file
Index: branches/RC/core/module_help/categories_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_edit.txt (revision 8929)
+++ branches/RC/core/module_help/categories_edit.txt (revision 0)
@@ -1,17 +0,0 @@
-
-- 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.
-
- Name - this is the category name
-
- Description - this is the category description
-
- 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
-
- 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.
-
- 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.
-
- 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.
-
-
- �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.
-
- Status � this is the category status
-
- 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.
-
- Editor's Pick � this sets the Editor's pick flag
-
- 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.
-
- 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.
-
\ No newline at end of file
Index: branches/RC/core/module_help/images_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/images_edit.txt (revision 8929)
+++ branches/RC/core/module_help/images_edit.txt (revision 0)
@@ -1,14 +0,0 @@
-
- - 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.
- - Name – this field contains the image name, used in In-tags to designate the image.
- - 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).
- - Status – this field contains the status of the image, enabled or disabled.
- - 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).
- - Priority – this field contains the numerical priority of the image.
- - 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.
- - Thumbnail location (remote URL) – Here you can enter a remote URL address of an image. It will be linked from the remote server.
- - 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.
- - 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.
- - Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
-
-
\ No newline at end of file
Index: branches/RC/core/module_help/categories_images.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_images.txt (revision 8929)
+++ branches/RC/core/module_help/categories_images.txt (revision 0)
@@ -1,15 +0,0 @@
-
- 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.
-
- - 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.
-
- Name � this field contains the image name, used in In-tags to designate the image.
-
- 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).
-
- Status � this field contains the status of the image, enabled or disabled.
-
- 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).
-
- Priority � this field contains the numerical priority of the image.
-
- 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.
-
- Thumbnail location (remote URL) � Here you can enter a remote URL address of an image. It will be linked from the remote server.
-
- 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.
-
- 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.
-
- Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
-
\ No newline at end of file
Index: branches/RC/core/module_help/categories_custom.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_custom.txt (revision 8929)
+++ branches/RC/core/module_help/categories_custom.txt (revision 0)
@@ -1,2 +0,0 @@
-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/RC/core/module_help/relations_edit.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/relations_edit.txt (revision 8929)
+++ branches/RC/core/module_help/relations_edit.txt (revision 0)
@@ -1,8 +0,0 @@
-
- - Relation ID – this is 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.
- - Item – this is a read-only field, displaying the name of the item that you are creating a relation to, and its type. In the current version, links can be related to categories, articles (if In-newz is installed) and topics (if In-bulletin is installed).
- - Type – this field designated the type of the relation. A ‘reciprocal’ type denotes a two-way relation, and ‘one way’ – a one directional relation, from the link to the item.
- - Enabled – this field is the status flag of the relation.
- - Priority – this field is the numerical priority of the relation.
-
-
\ No newline at end of file
Index: branches/RC/core/module_help/categories_permissions.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_permissions.txt (revision 8929)
+++ branches/RC/core/module_help/categories_permissions.txt (revision 0)
@@ -1,20 +0,0 @@
-This tab allows you to control the permissions of the current category. The first list displays all groups in the system. Below the groups list there are tabs for each of installed modules, including In-portal platform. Each tabs lists corresponding module permissions. The tab consists of a table with the following fields:
-
- - Description – permission description and name
- - Inherited – the checkbox specifies that a particular permission is inherited from the parent, and therefore cannot be defined for this category
- - 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.
- - Access - check box shows whether a permission is set or unset in the current category.
- - Effective – green or 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 do not have to look up the parent category to find out what the value of a particular permission is.
-
-
-The list of In-portal platform permissions is as follows:
-
- - View Category – controls whether a user can view the subcategories in this category.
- - Add Category – controls whether a user can add categories inside this category.
- - Delete Category – controls whether a user can delete categories inside this category.
- - 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.
- - Modify Category – controls whether a user can modify categories inside this category.
- - 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.
-
-
-
\ No newline at end of file
Index: branches/RC/core/module_help/categories_properties.txt
===================================================================
diff -u -N
--- branches/RC/core/module_help/categories_properties.txt (revision 8929)
+++ branches/RC/core/module_help/categories_properties.txt (revision 0)
@@ -1,14 +0,0 @@
-This tab controls module-specific category properties. The contents of the tab depends on the modules installed.
-In-newz module adds the following properties:
-RSS Feed Properties:
-
-- 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.
-
- Update Interval � the time interval used for parsing the RSS source and populating the category with articles.
-
-RSS Feed Articles Expiration
-
-- Default Expiration � the default expiration time of articles imported through RSS into the category.
-
- 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)
-
- Delete Expired � the checkbox controls whether expired articles should be completely deleted from the system, or simply marked as archived (expired).
-
-As of the current version, In-link, In-commerce and In-bulletin modules do not have any category-level properties.