Index: trunk/kernel/admin/include/help/configure_lang.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/configure_lang.txt (revision 0)
+++ trunk/kernel/admin/include/help/configure_lang.txt (revision 55)
@@ -0,0 +1,9 @@
+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 4.2.6 of this manual.
+
+- "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.
+
+ - "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.
+
+ - Primary Region Package
+Every In-portal system has to have at least one regional package, and at least one pack must be designated as the primary one. The primary pack will be used for all visitors by default, until they choose a different language (if that option is offered by the system administrator). The primary pack setting is also used for the Administrative Console, but can be changed by the administrative users for each session.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/searchlog.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/searchlog.txt (revision 0)
+++ trunk/kernel/admin/include/help/searchlog.txt (revision 55)
@@ -0,0 +1,3 @@
+This section displays a list of all key words and phrases that have been searched for on the front-end. You can refresh this information by clicking the �Refresh' button, or delete one or more entries by clicking the �Reset' button (a recycling bin icon with a red x).
+The Search Type column specifies whether the keyword was used in the simple or in the advanced search form. The Keyword column contains the literal text that was searched, and the Frequency column shows the number of searches performed since the last time you have deleted this keyword or phrase from the log.
+The keywords are logged regardless of whether the search has found any results, or any further action was taken. The logging occurs the moment a front-end user clicks on the �Search' button.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/user_email.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/user_email.txt (revision 0)
+++ trunk/kernel/admin/include/help/user_email.txt (revision 55)
@@ -0,0 +1 @@
+This section lists all possible community 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
Index: trunk/kernel/admin/include/help/lang_email.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/lang_email.txt (revision 0)
+++ trunk/kernel/admin/include/help/lang_email.txt (revision 55)
@@ -0,0 +1,9 @@
+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.
+An email notification has the following fields:
+
+- Subject � this field contains the subject of the email notification.
+
- Send Email As � This flag designates the email to be either in Plain Text or in the HTML format. Some older email clients cannot display the HTML emails, although they can be formatted a lot better.
+
- Extra Mail Headers � this field contains additional email headers that you may want to add to the outgoing email notification. The mail headers need to be entered in exact accordance with the email regulations.
+
- Message � this field contains the body of the message. It is possible, and in many cases recommended, to use In-tags in side the email subject and body. The In-tags will allow you to create customized emails. For example, to create an email notification that will address the user by their first and last names, you would use the following In-tags: �Dear <inp:touser _Field="FirstName" /> <inp:touser _Field="LastName" /> �.
+
+The other columns in the list display the information about the event itself, which cannot be changed from the Regional settings section. To change the event properties, please go to the appropriate Events section, for example, Structure & Data -> Email Setting for In-portal platform category events.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/sessionlog.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/sessionlog.txt (revision 0)
+++ trunk/kernel/admin/include/help/sessionlog.txt (revision 55)
@@ -0,0 +1,10 @@
+This section shows the administrator all currently active sessions in the system. The administrator can refresh this information by pressing the �Refresh' button, or delete one or more sessions by pressing the �Reset' button (icon with an unplugged power plug.)
+Deleting the session will cause the user to be logged out as soon as they click on anything or refresh the page. All of the information they were working on will be lost. This function applies both to the front-end and administrative console user sessions, and it should be used with great caution, only in exceptional circumstances.
+Please note that root sessions (when the �root' user is logged in) are not displayed in this list; they cannot be deleted as well.
+
+- User name � this column shows the user name of the logged in user, or �Guest' for site visitors.
+
- Primary Group � this column shows the primary group of the logged in user, or �Guest Users' for site visitors.
+
- Status � in the current version of In-portal platform, the only session status is �Active'.
+
- IP Address � this column shows the IP address from which the user or site visitor is using the In-portal front-end or administrative console.
+
- Created On � this column shows the date when the session was created.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/theme_templates.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/theme_templates.txt (revision 0)
+++ trunk/kernel/admin/include/help/theme_templates.txt (revision 55)
@@ -0,0 +1,10 @@
+This tab lists all templates, which are a part of the theme, and allows the administrator to manage them. The button �Preview' (template icon with a magnifying glass) opens the front-end in a pop-up window, so that the administrator can preview the changes made. Since not all templates are describing entire pages, and some may even be not visible (a category element template, when there are no categories, for example), it is impossible to direct the preview to the specific template being modified.
+The template creation and edit form has the following fields:
+
+- File ID � this field is a read-only, unique and internal system template ID. It is also displayed in the URL as a part of the query string.
+
- File Name � this field contains the template file name. It is not possible to change the file name online. The name can be entered when creating a new template (it must be unique within the directory of the template), and it can be later changed via FTP or direct access to the web server.
+
- Description � this field contains the internal description of the template. It is not used on the front-end.
+
- Item Tags � this dropdown shows all available item attribute tags. An item attribute tag displays the value of the attribute for each given item in an element template. Not all attributes are applicable to all items.
+
- Global Tags � this dropdown shows all global system tags, for the In-portal platform and for each installed module. The global tags can be generally used in all templates, but in certain places they will not make sense.
+
- [Template Body] � this field has no label, but it is clear that it contains the actual body of the template.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/user_custom.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/user_custom.txt (revision 0)
+++ trunk/kernel/admin/include/help/user_custom.txt (revision 55)
@@ -0,0 +1,12 @@
+
+This section allows the administrator to manage the topic custom fields. The topic custom fields are useful when you need to store additional information about the topics. For example, the topics may have such custom fields, as the language of the topic, the safe audience rating, etc. All custom fields will be automatically used in the Administrative Console, in the Topic Management section. You will need to edit the theme templates for them to appear on the front-end.
+
+- Field Id � this is a read-only field displaying the unique system ID of the custom field.
+
- 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.
+
- 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.
+
- 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 topics. It is a short cut for frequently used custom fields. All settings below apply only when this is checked.
+
- Heading � this field contains the language variable of the section heading, under which the field appear on the general tab.
+
- Field Prompt � this field contains the language variable, which text will appear as the hint bind the field.
+
- 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.
+
- 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).
+
Index: trunk/kernel/admin/include/help/lang_export.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/lang_export.txt (revision 0)
+++ trunk/kernel/admin/include/help/lang_export.txt (revision 55)
@@ -0,0 +1 @@
+�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: trunk/kernel/admin/include/help/inlink_inport.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/inlink_inport.txt (revision 0)
+++ trunk/kernel/admin/include/help/inlink_inport.txt (revision 55)
@@ -0,0 +1,15 @@
+This section allows the administrator to import the data from other applications into your existing In-portal system.
+Step 1 of the import begins with a disclaimer that the data in your current system will be affected. Please ensure you understand the import process and the particular kind of import you are doing before proceeding.
+
+
+In-link 2 Import
+In the current version, only the import from In-link2 is available. The import is designed for In-link version 2.3.4, however it will work, or partially work, for most of the older In-link2 versions up to 2.0.10. If you have one of the older In-link2 versions and are experiencing problems, please upgrade your In-link2 to the version 2.3.4, and then run this import. It is not possible to use In-link2 import if you do not have In-link3 installed on your In-portal platform. Some In-link2 license holders are entitled to a complimentary In-link3 license, please go to your account at http://www.intechnic.com/myaccount for more information, or submit a support ticket.
+
+Step 3
+In this step, the administrator will be asked to enter all database information for the In-link2 data. The current version of In-portal only supports import from the MySQL databases of In-link2.
+Step 4
+In this step, the administrator will need to designate the options of the import � how the In-link2 data is supposed to be integrated into In-portal and In-link3.
+ Administrative Group � this field designates the In-portal administrative group (by default, �Admin'), into which the old In-link2 administrators should be imported. You can choose a different group for the import, and then designate the administrative users later. Clicking on the group button will pop up a list of In-portal groups.
+ Regular User Group - this field designates the In-portal group (by default, �Members'), into which the old In-link2 users (link owners) should be imported. It is recommended to import then into a group that will give them access to the front-end, and to modify their links. However, you can choose a different group for the import, and then manage the users later. Clicking on the group button will pop up a list of In-portal groups.
+ Initial Import Category � this field designates the In-portal category, which will serve as a root for the In-link2 import. This category will be the equivalent of the Home category in In-link2, and all of the sub-categories will be created underneath. Clicking on the category button (folder icon) will pop up a catalog navigator, where you can select the category.
+ Link Image Name � this field designates the link image field in the In-link2 database, which was used to store the link image name. By default, it is �link_image' , however many users have used a custom field for this purpose, in which case you should enter the custom field name here.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/modules.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/modules.txt (revision 0)
+++ trunk/kernel/admin/include/help/modules.txt (revision 55)
@@ -0,0 +1,4 @@
+This section provides the administrator with an overview of the modules installed on the In-portal Platform. It also contains sub-sections, one for each module, where the module-specific settings are located.
+To add a new module to your system, please upload the appropriate module program files into your �in-portal' directory and upload all of the module templates into the theme you are planning to use. Then click on the �Add Module' link. The page will show you a list of all modules, detected on your system, with a link to install the new one(s). Simply click the link, and the module will be installed.
+To disable or enable an installed module, follow the �Enable/Disable Modules' link. The page will show you a list of all modules installed on your In-portal platform, and in the toolbar you will find the buttons to enable and disable your modules. Please be careful when disabling a module � this option will hide all module-specific sections from your administrative console, and it will also disable all module's templates on the front-end, which may lead to undesired effects on your public web site.
+You can access the current In-tag library on this page as well. Click on the �Tag Library' link, and you will be taken to a page with a complete list of all In-tags currently supported by your system, description of their attributes and functionality.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/export.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/export.txt (revision 0)
+++ trunk/kernel/admin/include/help/export.txt (revision 55)
@@ -0,0 +1 @@
+There are no export wizards available in the current version. To export the data, please use your favorite SQL administration utility. One of the most popular utilities for MySQL can be downloaded from http://www.phpmyadmin.net.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/log_summary.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/log_summary.txt (revision 0)
+++ trunk/kernel/admin/include/help/log_summary.txt (revision 55)
@@ -0,0 +1 @@
+This section provides the statistical information about your In-portal platform and all installed modules. All of the values are automatically updated as you enter the section. If you want to see the most current value of any statistics, please use the �Refresh' button (icon with two revolving green arrows).
\ No newline at end of file
Index: trunk/admin/help/manual.pdf
===================================================================
diff -u -r49 -r55
Binary files differ
Index: trunk/kernel/admin/include/help/lang_general.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/lang_general.txt (revision 0)
+++ trunk/kernel/admin/include/help/lang_general.txt (revision 55)
@@ -0,0 +1,14 @@
+The general tab contains the cultural settings of the pack.
+
+- Language Id � this field is a read-only, unique and internal system regional package ID. It is also displayed in the URL as a part of the query string.
+
- Pack Name � this field contains the English name of a regional package, or any label the administrator wants to use for the pack.
+
- Local Name � this field contains the name of the regional package in the native language of the pack. For example, for a German regional pack, this field would be set to �Deutsch.�
+
- Icon URL � this field contains the URL of the image, which will be used to display the regional pack designator icon (usually a country flag, associated with the pack's language). This may be a remote URL, or a local URL, in which case it should be relative to the �in-portal/themes/[current theme]' directory. The icon is necessary for the language selector in the default theme on the front end.
+
- Date Format � this field contains the date format of the regional pack. The information should be entered using standard programming codes for various formats of days, months and years. For more information about the date codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current date. This example will update after you save the changes.
+
- Time Format - this field contains the time format of the regional pack. The information should be entered using standard programming codes for various formats of seconds, minutes and hours. For more information about the time codes, please refer to PHP's web site: http://us2.php.net/manual/en/function.date.php . The example to the right of the field shows the resulting format of the current time. This example will update after you save the changes.
+
- Decimal Point � this field contains the character that will be used for separating the decimal part from the whole number. For example, in the U.S. it is a period: �10.00� and in Europe , as well as other locals, it is a comma: �10,00�.
+
- Thousands Separator � this field contains the character that will be used for separating the thousands in numbers.
+
- Enabled � this field is the regional pack status flag.
+
- Primary � this flag indicates whether the pack is primary or not. If you check it while editing a non-primary pack, the pack that used to be primary will no longer be � only one primary pack can exist in a system.
+
- Copy Labels to this Language � this is not an actual attribute of the regional pack, like the other fields on this form. It is a function that will copy all language phrases from another pack, designated in the drop down, into the current pack. It is useful for creation of new regional packs.
+
\ No newline at end of file
Index: trunk/admin/help/help.php
===================================================================
diff -u -r49 -r55
--- trunk/admin/help/help.php (.../help.php) (revision 49)
+++ trunk/admin/help/help.php (.../help.php) (revision 55)
@@ -100,6 +100,7 @@
}
$help_data = file_exists($topic_path) ? file_get_contents($topic_path) : GetVar('help_content');
+if($section[0] == 'kernel') $section[0] = 'in-portal';
?>
Index: trunk/admin/import/import.php
===================================================================
diff -u -r27 -r55
--- trunk/admin/import/import.php (.../import.php) (revision 27)
+++ trunk/admin/import/import.php (.../import.php) (revision 55)
@@ -524,7 +524,7 @@
$oldcatid = $row->fields["cat_id"];
$pending = $row->fields["link_pend"];
#getting a new category id
- echo "HERE LOOK
";
+
$rs = $portalconn->Execute("SELECT nid FROM ".$TablePrefix."import WHERE ntname='Category' and oid=$oldcatid");
if ($rs && ! $rs->EOF)
{
Index: trunk/kernel/admin/include/help/restore.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/restore.txt (revision 0)
+++ trunk/kernel/admin/include/help/restore.txt (revision 55)
@@ -0,0 +1,2 @@
+On the first page of the Restore section, you will be asked to enter the root password of the system, and to confirm the disclaimer. The disclaimer indicates that the restore procedure will completely erase your existing data, and replace it with what is in the backup file. In the event the restore fails for some reason, you may be left without functioning In-portal data.
+Once you click next, you will be taken to the installation screen. It is not possible to be in the administrative console at the same time the restore is taking place, as all of the existing data, including the sessions and the user information, is erased.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/configure_users.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/configure_users.txt (revision 0)
+++ trunk/kernel/admin/include/help/configure_users.txt (revision 55)
@@ -0,0 +1,14 @@
+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: trunk/kernel/admin/include/help/configure_general.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/configure_general.txt (revision 0)
+++ trunk/kernel/admin/include/help/configure_general.txt (revision 55)
@@ -0,0 +1,19 @@
+This section allows the administrator to update the system settings of the In-portal platform.
+
+- Web address � this field contains t he 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).
+
- 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 .
+
- 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.
+
- 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.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/navmenu.php
===================================================================
diff -u -r41 -r55
--- trunk/kernel/admin/include/navmenu.php (.../navmenu.php) (revision 41)
+++ trunk/kernel/admin/include/navmenu.php (.../navmenu.php) (revision 55)
@@ -58,8 +58,8 @@
NULL,"in-portal:tools",NULL,"in-portal:restore",0,"",1,
NULL,"in-portal:tools",NULL,$admin."/icons/icon46_list_tool_backup.gif","la_performing_backup");
-$objSections->AddSection("in-portal:backup_toolbar",NULL,NULL,NULL,NULL,
- NULL,NULL,
+$objSections->AddSection("in-portal:backup_toolbar","la_tab_Backup","la_tab_Backup",NULL,NULL,
+ $admin."/icons/icon46_tool_backup.gif",$admin."/icons/icon24_tool_backup.gif",
NULL,NULL,NULL,NULL,0,"",1,
NULL,NULL,NULL,NULL);
$objSections->AddSection("in-portal:restore_toolbar",NULL,NULL,NULL,NULL,
@@ -110,13 +110,28 @@
NULL, "in-portal:system", "in-portal:configure_general", "in-portal:configure_lang",0,"",1,
NULL,NULL,NULL,$admin."/icons/icon46_list_conf_themes.gif");
+
+
+
+$objSections->AddSection( "in-portal:template_editor",
+ "la_tab_Themes",
+ "la_tab_Themes",
+ '',
+ '',
+ $admin."/icons/icon46_conf_themes.gif",
+ $admin."/icons/icon24_conf_themes.gif",
+ NULL, NULL, NULL, NULL, 1,'',1,
+ 0,1,0,$admin."/icons/icon46_list_conf_themes.gif");
+
+
$objSections->AddSection("in-portal:configure_lang", "la_tab_Regional", "la_tab_Regional", $admin."/config/","config_lang.php",
$admin."/icons/icon46_conf_regional.gif", $admin."/icons/icon24_conf_regional.gif",
NULL, "in-portal:system", "in-portal:configure_themes", NULL,0,"",1,
NULL,NULL,NULL,$admin."/icons/icon46_list_conf_regional.gif");
/* theme tabs */
+
$objSections->AddSection("in-portal:theme_general", "la_tab_General", NULL, $admin."/config/",
"javascript:edit_submit('theme','ThemeEditStatus','".$admin."/config/addtheme.php',0);",
$admin."/icons/icon46_conf_themes.gif", $admin."/icons/icon24_conf_themes.gif",
Index: trunk/kernel/admin/include/help/lang_labels.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/lang_labels.txt (revision 0)
+++ trunk/kernel/admin/include/help/lang_labels.txt (revision 55)
@@ -0,0 +1,9 @@
+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.
+There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button.
+As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/backup_toolbar.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/backup_toolbar.txt (revision 0)
+++ trunk/kernel/admin/include/help/backup_toolbar.txt (revision 55)
@@ -0,0 +1,2 @@
+This page displays the backup progress. Depending on the size of the data, and the performance of the server, the backup can take a widely variable amount of time. The top progress bar shows which table is being currently backed up, and how many rows have been completed. The bottom progress bar shows the progress on the database level � how many tables have been back up out of the total number of tables.
+If you cancel the backup while it is in progress, you will not have a complete and reliable backup, therefore it is not recommended to do that.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/theme_general.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/theme_general.txt (revision 0)
+++ trunk/kernel/admin/include/help/theme_general.txt (revision 55)
@@ -0,0 +1,9 @@
+The general tab contains the information applicable to the entire theme.
+
+- Theme Id � this read-only field displays the internal unique system theme ID.
+
- Name � this field contains the theme name. The name is used to refer to the theme on the front-end. It also has to match the directory under �in-portal/themes' where all templates for this theme will be stored.
+
- Description � this field contains the description of the theme. It is primarily for the administrator's internal notes about the theme, however it can be also displayed on the front-end.
+
- Enabled � this is the theme status.
+
- Language Cache Timeout � The tags, cached on a page, expire after this period (specified in seconds). The language caching is implemented to reduce the server load and speed up the page download times. It caches the values of the language phrases used on a given template, and uses the cache instead of evaluating the languages dynamically. This also means that if you modify a template, and add or remove some language labels, your changes will not take effect until after the cache refreshes. To disable the caching, set this value to zero. Under normal circumstances, we recommend keeping the language cache timeout setting at its default value of 3600 seconds (1 hour).
+
- Primary � this flag indicates whether the theme is primary or not. If you check it while editing a non-primary theme, the theme that used to be primary will no longer be � only one primary theme can exist in a system.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/template_editor.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/template_editor.txt (revision 0)
+++ trunk/kernel/admin/include/help/template_editor.txt (revision 55)
@@ -0,0 +1,10 @@
+This tab lists all templates, which are a part of the theme, and allows the administrator to manage them. The button �Preview' (template icon with a magnifying glass) opens the front-end in a pop-up window, so that the administrator can preview the changes made. Since not all templates are describing entire pages, and some may even be not visible (a category element template, when there are no categories, for example), it is impossible to direct the preview to the specific template being modified.
+The template creation and edit form has the following fields:
+
+- File ID � this field is a read-only, unique and internal system template ID. It is also displayed in the URL as a part of the query string.
+
- File Name � this field contains the template file name. It is not possible to change the file name online. The name can be entered when creating a new template (it must be unique within the directory of the template), and it can be later changed via FTP or direct access to the web server.
+
- Description � this field contains the internal description of the template. It is not used on the front-end.
+
- Item Tags � this dropdown shows all available item attribute tags. An item attribute tag displays the value of the attribute for each given item in an element template. Not all attributes are applicable to all items.
+
- Global Tags � this dropdown shows all global system tags, for the In-portal platform and for each installed module. The global tags can be generally used in all templates, but in certain places they will not make sense.
+
- [Template Body] � this field has no label, but it is clear that it contains the actual body of the template.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/phrase_editor.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/phrase_editor.txt (revision 0)
+++ trunk/kernel/admin/include/help/phrase_editor.txt (revision 55)
@@ -0,0 +1,9 @@
+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.
+There are two ways to edit multiple labels at once. The first way is to edit one label, and then to use the blue Previous and Next buttons to go back and forth between the labels. The same order as in the list will be used in this case. The second way is to select multiple labels at once, and click the edit button.
+As with any other second-level list, it is very important to remember, that your changes are not actually saved, until the regional package is saved. If you make changes to the labels, and then move to a different section without hitting Save on the regional package level, your changes will be lost.
+
\ No newline at end of file
Index: trunk/kernel/admin/include/help/backup.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/backup.txt (revision 0)
+++ trunk/kernel/admin/include/help/backup.txt (revision 55)
@@ -0,0 +1,3 @@
+In Step 1, the administrator is asked to choose the path where the backup file will be stored. By default, it is the �in-portal/admin/backupdata' directory, but it can be any other location on the server, to which the web server has write-access. If you change the backup destination path, please be aware that the Restore function, described below, and the Install function both look in the predefined directory for the backup files, therefore none of the other backups will be listed. Click the update button, if you have modified the path.
+
+Step 3 will be shown after the backup has been completed. Here you will see a full path and file name of the backup file created, as well as its size. This is important information if you wish to download the backup file to another computer, as recommended for additional reliability.
Index: trunk/kernel/admin/include/help/lang_import.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/lang_import.txt (revision 0)
+++ trunk/kernel/admin/include/help/lang_import.txt (revision 55)
@@ -0,0 +1 @@
+�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: trunk/kernel/admin/include/help/sql_query.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/sql_query.txt (revision 0)
+++ trunk/kernel/admin/include/help/sql_query.txt (revision 55)
@@ -0,0 +1 @@
+This section is for advanced administrators who are familiar with the SQL database language. The �SQL Query' field on this page takes a full (and properly written) SQL query to be performed against your In-portal database. Clicking �Save' will run the query and display the results on the next page, where you will get a chance to edit the query and run it again. Please use extreme caution when using this function, because it does not provide any safeguards for the data, otherwise available in the rest of the administrative console. You can easily erase, or corrupt your In-portal data with a wrong query. It is also possible to cause the MySQL server to �freeze�, or stop responding, in extreme cases. We recommend making a full database backup (see section 5.2.6.5 ) before running any UPDATE, DELETE, INSERT, ALTER or DROP queries.
\ No newline at end of file
Index: trunk/kernel/admin/include/help/configure_themes.txt
===================================================================
diff -u
--- trunk/kernel/admin/include/help/configure_themes.txt (revision 0)
+++ trunk/kernel/admin/include/help/configure_themes.txt (revision 55)
@@ -0,0 +1 @@
+This section allows the administrator to manage themes of the In-portal platform. For more information about themes and templates, please read the section 4.2.5 of this manual.
\ No newline at end of file