<p>Please fill out the database connection information (server location is usually localhost , and you can find out the database name/user/password combination from your server administrator, or in the hosting account's Control Panel) . </p>
<p>You may then choose a table prefix that will be preceding all of database table names used by In-portal Platform and modules. This option is useful when you are installing more then one copy of the In-portal Platform on the same database, or if it is sharing the same database with another application and you want to prevent the table naming conflicts. </p>
<h3><a name="_Toc87037132"><li> Step 2 Select a License </a></h3>
<p>All life or production installations of the In-portal Platform and any modules require a valid license obtained from Intechnic Corporation. A local or development installation, which is not accessible from the Internet (has a non-routable IP) and is used only for demonstration or development purposes, does not require a license. For more details, please go to <a href="http://www.in-portal.net/">http://www.in-portal.net </a> or see the chapter 2 above. </p>
<p>There are two options for selecting a license: </p>
<p><li> Download from Intechnic: in order to download the license directly from Intechnic, you must have a registered account ( <a href="http://www.intechnic.com/myaccount">http://www.intechnic.com/myaccount </a>). If your server allows outbound Internet connections (most servers do), you can use the My Account login to download the license automatically. The installation script will guide you through the remaining process, if this option is selected. </p>
<p><li> Upload License File: you may upload the license file if you choose this option. The license file can be obtained from the My Web Sites section of the My Account ( <a href="http://www.intechnic.com/myaccount">http://www.intechnic.com/myaccount </a>). This option is useful if you are installing In-portal on your local server, without the access to the Internet. </p>
<p>This screen will show you all domains, which are valid for the license you have picked, or all local domains, which are available. Please select the domain where you want the In-portal site to re side . </p>
<p>In the other domain field, you may enter an IP address, if you do not wish to use a domain name, or a local computer name. </p>
<h3><a name="_Toc87037134"><li> Step 4 Set Root Password </a></h3>
<p>This screen of the installation script will prompt you to enter a root password for your In-portal system. The root access is the highest-level (superuser) access into the system. It is not designed for daily use, but rather reserved for the In-portal administrator to perform major system operations, and to create additional administrative users. </p>
<p>Please take extra care not to loose your root password. If you do so, and you do not have any other administrative users set up, you will permanently loose access to your Administrative Console. </p>
<p>The installation script will automatically determine which modules' program files are uploaded to your in-portal' directory and are available for installation. This screen will allow you to select the modules that you want installed at this time. </p>
<p>If the desired module is not listed, it is because you did not upload it to the correct location. Please double check that the module program files have been uploaded directly under your in-portal' directory. For example, the In-link module should be located in the in-portal/in-link' directory. It is also possible that you do not have the appropriate license for this module on this domain. </p>
<h3><a name="_Toc87037136"><li> Step 6 Language Packs </a></h3>
<p>This screen you will prompt you to select the regional packages you want to install. In-portal Platform version 1.0.4 comes with a default regional package. Additional regional packages may be available for download from our web site ( <a href="http://www.in-portal.net/">http://www.in-portal.net/ </a>). </p>
<p>You can add more regional packages through the Administrative Console later. Please see the section 5.2.5.3 of this manual for more information. Also, please note, that at least one regional package must be enabled during the initial installation; otherwise, you will not be able to operate your Administrative Console. </p>
<h3><a name="_Toc87037137"><li> Step 7 Select Default Language </a></h3>
<p>This step will allow you to select the default language for your system. You can change the default language from the Administration Console later. Please see the section 5.2.5.3 of this manual for more information. </p>
<p>The next few screens will allow you to configure the default options for the In-portal Platform and the modules you have installed. All of these settings can be changed later through the Administrative Console. </p>
<h4><li> In-portal Platform Settings, part 1 </h4>
<p><li> Web address: The full directory path where your In-portal system is located. It is the portion of the URL that comes directly after the domain name. Example: if the URL is <a href="http://www.in-portal.net/demo/">http://www.in-portal.net/demo/ </a>, then the full path is /demo/' . Please note, that the preceding and the trailing slashes are required. The installation script will detect the full path automatically and you only need to change it in the event of a non-standard web server configuration. </p>
<p><li> Website name: The title of your site that will appear in the browser title bar. For example, My Website, or any other arbitrary text. </p>
<p><li> Session Management Method: Choose between Query String', Cookies' or Automatic'. For more information, see section 5.2.5.1 of this manual. </p>
<p><li> Session Inactivity Timeout (seconds): Set the timeout (in seconds), after which all inactive users (both front-end and administrative) will be automatically logged out. This is an important security feature, and it is not recommended to set the session expiration to more than 3600 seconds (1 hour). </p>
<p><li> Time zone of the server: Please select the time zone of your server's location. You can find out this information from your server administrator. </p>
<p><li> Time zone of the site: Please select the time zone for your web site. Please note that this can be different from the time zone of the server, depending on your geographical location. This setting will allow you to see the accurate date/time stamps recorded by the system. </p>
<p><li> Mail Server Address: You need to set this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal. Leaving it blank will use your web server's default mail transport. </p>
<p><li> Port (e.g. port 25): Set the SMTP port of your external mail server. You need to set this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal. </p>
<p><li> Server Requires Authentication: Check this if your SMTP server requires a user name and a password to send mail through (this is common on the newer mail systems). You need to set this field only if you are planning to use an external mail server for the outgoing mail generated by In-portal. </p>
<p><li> Mail Server Username: Enter 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. </p>
<p><li> Mail Server Password: Enter 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. </p>
<p><li> Messages from Site Admin are from: Enter 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. </p>
<h4><li> In-portal Platform Settings, part 2 </h4>
<p><li> Allow new user registration: This designates how your new users will be registering through the front end. Instant' means that they will automatically be enabled after the registration. This option is useful for sites that anticipate a large user base, and do not need a high level of security. The Not Allowed' option will unconditionally deny registration on the front-end. The administrator will still be able to create front-end users through the Administrative Console. This is the highest security setting. The Upon Approval' option is for administrators who want to approve manually the user registrations. This is the default option. </p>
<p><li> Assign registered users to group: If you have allowed user registration in the above question, this option will designate a group, to which all newly registered users will be assigned. To learn more about groups, please see section 4.2.3 of this manual <a href="#_ftn1" name="_ftnref1">* </a>. </p>
<p><li> Assign users not logged in to group: In order to manage permissions for your site's visitors (people who have come to your site, but have not logged in), you will need to designate a group in this question. To learn more about groups, please see section 4.2.3 of this manual * . </p>
<p><li> Assign mailing list subscribers to group: Here you can choose which group will be designated for the users, who choose to use the subscribe' option on the front end * . </p>
<p><li> Assign password automatically: Checking 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. </p>
<p><li> 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. </p>
<p><li> 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. </p>
<h4><li> In-portal Platform Settings, part 3 </h4>
<p><li> Order categories by: This setting specifies the default primary sort order for categories in lists (both front end and Administrative Console). </p>
<p><li> And then by: This setting specifies the default secondary sort order for categories in lists (both front end and Administrative Console). </p>
<p><li> Number of categories per page: This setting specifies the default number of categories to be shown on one page. </p>
<p><li> Categories Per Page (Shortlist): This setting specifies the default number of categories to be shown on one page, when viewed as a short list on the front end. </p>
<p><li> Number of days for a cat. to be NEW: This setting specifies how many days a category will keep its new' status. The new' status can be individually changed for each category, but the default value is automatic', which will use this setting. </p>
<p><li> Display editor PICKs above regular categories: Checking this option will force the Editor's Pick categories to be listed above the regular categories. The Editor's Pick setting will take precedence over any other priority setting. </p>
<p><li> Root category name (language variable): Enter the name of a language variable, which will designate the name of the root category. The default variable name is lu_rootcategory_name', and in English it has a value of Home'. Usually you don't need to change the variable name, because you can change the value of the variable just as easily. For more information about languages, please see section 4.2.6 of this manual. </p>
<p><li> Default META Keywords: Enter text here that will be displayed as a default META keyword tag on the front-end pages. If a category will have its own META keyword tag, it will take precedence over this setting. You may also leave it blank. </p>
<p><li> Default META description: Enter text here that will be displayed as a default META description tag on the front-end pages. If a category will have its own META description tag, it will take precedence over this setting. You may also leave it blank. </p>
<h4><li> In-portal Platform Settings, part 4 </h4>
-<p><li> Default Theme: Choose the default theme. The only selection here will be the themes that you have already uploaded to your in-portal/themes' directory. The default installation of 1.0.4 comes with one theme called Default'. Additional themes may be available for download on our web site: <a href="http://www.in-portal.net/">http://www.in-portal.net/ </a></p>
+<p><li> Default Theme: Choose the default theme. The only selection here will be the themes that you have already uploaded to your in-portal/themes' directory. The default installation of 1.0.5 comes with one theme called Default'. Additional themes may be available for download on our web site: <a href="http://www.in-portal.net/">http://www.in-portal.net/ </a></p>
<p>Congratulations! You have completed your In-portal installation. Clicking Continue' will take you to your new Administrative Console. </p>
Please remember to log in with the user name root' and the password that you have assigned in the step 4.
<p><a href="#_ftnref1" name="_ftn1">* </a> You will be selecting from a predefined list of groups here. Later, in Administrative Console, you will be able to create your own groups, and change these settings, if necessary. </p>
Property changes on: trunk/kernel/admin/include/help/install.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.
+
+<p>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. </p>
+<p>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. The list of the administrative console permissions is as follows: </p>
+<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.
+<li> Read-Only Access To Database this permission will take away user's ability to modify any information in the database when using the Administrative Console. It is useful for demonstration purposes, as well as for setting up administrators who are only supposed to monitor information without actually changing it.
</ul>
- The list of the front-end permissions is as follows:
+<p>The list of the front-end permissions is as follows: </p>
<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.
+<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
-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:
+
+<p>The permissions tab allows the administrator to assign permissions to the group. This is the recommended way of managing user permissions. </p>
+<p>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. The list of the administrative console permissions is as follows: </p>
<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.
+<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.
+<li> Read-Only Access To Database this permission will take away user's ability to modify any information in the database when using the Administrative Console. It is useful for demonstration purposes, as well as for setting up administrators who are only supposed to monitor information without actually changing it.
</ul>
-
\ No newline at end of file
+<p>The list of the front-end permissions is as follows: </p>
+<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 Advanced View section allows you to manage categories and items across all categories. This is especially useful, when you are looking for a particular category or item, if you do not know their location (in which category they are located). One of the most common ways to use the Advanced View section is to review pending items. To do this, simply use the View menu to filter only Pending items of each type. </p>
+<p>In the Advanced View section, you can only manage existing items delete, edit, approve or deny them. All these actions are the same in this section as they are in the Catalog. To add a new item, please use the Catalog section. </p>
+<p>The Advanced View allows you to filter using the View menu and Search, similar to the Catalog section. The essential difference is that while in the Catalog the filtering options only apply to the current category you are looking at, in the Advanced View section they apply to all of the items of each type. </p>
+<p>The section is divided into tabs, a tab for Categories, and a tab for each module installed on your system. Each tab retains its individual filter settings (Search keyword and View menu options).
\ No newline at end of file
Property changes on: trunk/kernel/admin/include/help/advanced_view.txt