Index: trunk/kernel/admin/include/help/users.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/users.txt (revision 0) +++ trunk/kernel/admin/include/help/users.txt (revision 1231) @@ -0,0 +1,4 @@ +
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: trunk/kernel/admin/include/help/reviews.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/reviews.txt (revision 0) +++ trunk/kernel/admin/include/help/reviews.txt (revision 1231) @@ -0,0 +1,19 @@ +The Reviews section provides a consolidated view +of the reviews for all items across different modules. The +administrator can perform all of the basic functions directly in this +section, without locating the item that any given review belongs to. +One of the most common ways to use the Reviews section is to find +pending reviews. To do this, simply use the View menu to filter only +Pending reviews. +
+In this section, you can Approve, Deny, Edit and +Delete reviews, as well as search for a specific review, no matter +what item it may belong to.
+On the summary list, below the details of each +review there is a link to the item, to which the review belongs to. +Clicking on that link will allow the administrator to quickly edit +the parent item. When the administrator saves or cancels the item +changes, he or she will appear back in the Reviews section.
+The section is divided into tabs, 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 Index: trunk/kernel/admin/include/help/user_banlist.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/user_banlist.txt (revision 0) +++ trunk/kernel/admin/include/help/user_banlist.txt (revision 1231) @@ -0,0 +1,77 @@ +This section allows the administrator to manage +the ban rules. The ban rules are used to filter user registrations +automatically, using various criteria. This is useful, when the site +administrator does not want a certain person, or a group of people, +to register on the In-portal site, however does not want to review +all registrations manually. This seemly straightforward task is +actually very difficult to do on the Internet. There is no +bulletproof way to identify a real person when they are registering +online; one has only indirect information to rely on � the +information that the person submits or has the ability to change. +Therefore, the idea behind banning is to create as many accurate +rules as possible that would filter out the majority of the unwanted +people.
+This section also allows the administrator to +execute selected rules on the existing user database, banning the +users, which fall under those rules, but registered before the rules +where created and enforced.
+When a new user registration is banned, the +visitor will receive an error message, and will not be able to +complete the registration. When an existing user is banned, they are +disabled.
+The ban rule form has the following fields:
+Rule Type � this + field designated the type of the rule. There are �Deny� rules + and �Allow� rules. The �Deny� rules, when they match a user + record, deny the registration. The �Allow� rules work in the + opposite way � when such rule is matched with a user record, the + user registration is allowed. The conflicts between allow and deny + rules are resolved based on the priority of each rule. (Conflicts + occur, when one or more opposite rules match the same user record).
+Item Field � this + drop down selects the User attribute, which is going to be matched + against the rule value.
+Field Comparison � + this drop down selects the type of the match, in other words the + comparison operation that will be performed. The match types do + what their names mean. Please use the �Any� type with extra + caution. It does not perform a comparison, but instructs the rule + to match all user records, regardless of any other options.
+Field Value* - this + field contains the value that will be used when matching the rule.
+Error Tag � this + field contains the name of the language variable that contains the + text, which will be displayed on the front-end, when a user + registration is denied due to this rule. Leave it blank, if you do + not want to provide an error message. Please keep in mind, that it + is theoretically possible that a rule will deny registration to a + person you did not intend to be banned, and design the error + messages accordingly. +
+Priority � this + field sets the priority of the rule, which is used for resolving the + conflicts when more than one rule is matched with the same user + record.
+Status � this + field enables and disabled rules.
+For example, you as a site administrator, notice +that there is a person that registers with �ACME Corp� words in +their user name, email, first and last names, etc. You suspect that +this user is trying to advertise their company, and you want to +prevent them from using your site in that way. However, you are not +sure, what exact names this person will use in the future � all you +know is that they want to include the company name � ACME. In this +situation, you would set up three ban rules. They will be of type +�Deny�, on Item fields �User name�, �First name� and +�Last name�, using Field Comparison �Contains�, and the Field +Value �ACME�. Optionally, you can create a message for that +person, for example �Sorry, no ACME advertising allowed on this +site.� The priority is not important in this case, because a match +on any of the three fields is sufficient to ban the user. The status +should be set to �Enabled�. Now, that person will not be able to +register with the word �ACME� in their user name, or first or +last name. You may also want to run these three rules on your +existing user database, in case you missed some of the previous +registrations by that user.
\ No newline at end of file Index: trunk/kernel/admin/include/help/reports.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/reports.txt (revision 0) +++ trunk/kernel/admin/include/help/reports.txt (revision 1231) @@ -0,0 +1,6 @@ +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/kernel/admin/include/navmenu.php =================================================================== diff -u -r983 -r1231 --- trunk/kernel/admin/include/navmenu.php (.../navmenu.php) (revision 983) +++ trunk/kernel/admin/include/navmenu.php (.../navmenu.php) (revision 1231) @@ -380,5 +380,11 @@ $objSections->AddSection("in-portal:banuser","la_Text_BanUserFields","la_Text_BanUserFields", $admin."/users","banuser.php", $admin."/icons/icon46_community.gif", $admin."/icons/icon24_users.gif", - NULL,NULL,NULL,NULL,-1,"",1,0,0,1); + NULL,NULL,NULL,NULL,-1,"",1,0,0,1); + +$objSections->AddSection("in-portal:editreview_direct", "la_tab_Reviews", null,"", + "", + $admin."/icons/icon46_struct.gif", $admin."/icons/icon24_navigate.gif", + NULL, null, null, null, 1, '', 1, 0, 1); + ?> Index: trunk/kernel/admin/include/help/system.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/system.txt (revision 0) +++ trunk/kernel/admin/include/help/system.txt (revision 1231) @@ -0,0 +1,2 @@ +This section allows the administrator to update +the system settings of the In-portal platform.
\ No newline at end of file Index: trunk/kernel/admin/include/help/validation_list.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/validation_list.txt (revision 0) +++ trunk/kernel/admin/include/help/validation_list.txt (revision 1231) @@ -0,0 +1 @@ \ No newline at end of file Index: trunk/kernel/admin/include/help/root.txt =================================================================== diff -u --- trunk/kernel/admin/include/help/root.txt (revision 0) +++ trunk/kernel/admin/include/help/root.txt (revision 1231) @@ -0,0 +1 @@ +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