- $import_steps['groups']['count_sql'] = 'SELECT COUNT(DISTINCT g.group_id) FROM '.$bb_prefix.'groups g, '.$bb_prefix.'auth_access aa WHERE (g.group_id = aa.group_id)';
- $sql = 'SELECT ParentId, MIN(Priority) AS MinPri FROM '.$objCatList->SourceTable.' WHERE ParentId IN ('.implode(',', $all_cats) .') GROUP BY ParentId';
- $rs = $dst_db->Execute($sql);
- while(!$rs->EOF)
- {
- $rec =& $rs->fields;
- $MinPri = $rec['MinPri'];
- $sql = 'UPDATE '.$objCatList->SourceTable.' SET Priority = Priority + ABS('.$MinPri.') WHERE ParentId = '.$rec['ParentId'];
- $dst_db->Execute($sql);
- $rs->MoveNext();
- }
- return $recs_count;
- }
-
-
- function import_forums_perms()
- {
- global $cache, $current_step, $db, $bb_prefix, $import_steps, $import_category_id, $perm_mappings, $user_regular;
-This section allows the administrator to configure the censorship options. It lists all defined censorship rules, and allows the administrator to manage them. A censorship rule consists of:
-<ul>
-<li> Censorship Id this is the read-only, unique system ID of a censorship rule. It is empty for new rules.
-<li> Censorship Word this field contains the bad word text to be replaced. It can be any combination of letters in any language, numbers or special characters.
-<li> Replacement Word this field contains the replacement text. It can be any combination of letters in any language, numbers or special characters.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/admin/include/help/configuration_censorship.txt
-This section allows the administrators to manage the emoticons, or smileys, available for users to use in posts. By default, Intechnic ships In-bulletin with a predefined set of smileys.
-A smiley has the following attributes:
-<ul>
-<li> Emotion Id this is the read-only, unique system ID of a smiley. It is empty for new smileys.
-<li> Name this field contains the smiley name, which should be descriptive and designate the nature of the smiley. It appears in the alt tag on the post form, explaining to the users its purpose.
-<li> Key Stroke this field contains the shortcut keystroke that corresponds to the smiley. When used in a post text, this keystroke will be automatically replaces with the image of the smiley. Familiar keystroke example is : )', signifying the smiling face.
-<li> Enabled this field is the enabled flag of the smiley.
-<li> Location this field can contain either a remote URL of the smiley's image, or it can be used to upload an image from your workstation.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/admin/include/help/configuration_emoticon.txt
-<p>This import tool is designed to copy the data from your existing phpBB 2.x installation into In-portal Platform and In-bulletin. It will not work without In-bulletin module installed. </p>
-The current version transfers the users, forums, topics and posts. It also copies the basic permission structure for the forums and creates user custom fields to hold the additional information available in phpBB. The import will only copy phpBB information that is compatible with the current version of In-bulletin. For this reason, for example, the private messages are not copied over.
-<br><br>
-
-<b>Step 4 </b>
-<p>In this step, the administrator will need to designate the options of the import how the phpBB data is supposed to be integrated into In-portal and In-bulletin. </p>
-<ul>
-<li> Regular User Group - this field designates the In-portal group (by default, Members'), into which the all phpBB users should be imported. It is recommended to import then into a group that will give them access to the front-end, and to own their topics. 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. All other security groups that exist in phpBB installation will be automatically created during the import.
-<li> Initial Import Category this field designates the In-portal category, which will serve as a root for the phpBB import. This category will be the equivalent of the index page in phpBB, and all of the categories and forums will be created underneath. Clicking on the category button (folder icon) will pop up a catalog navigator, where you can select the category.
-<li>Table Name Prefix this field designates the table prefix for the phpBB tables.
-</ul>
Property changes on: trunk/in-bulletin/admin/include/help/phpbb.txt
-INSERT INTO ConfigurationAdmin VALUES ('Topic_SortField', 'la_Text_Topics', 'la_topic_sortfield_prompt', 'select', '', 'TopicText=la_Topic_Text,Posts=la_Number_of_Posts,CreatedOn=la_CreatedOn,LastPostDate=la_LastUpdate,Views=la_Topic_Views,CachedRating=la_Rating,LastPoser=la_Poster,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 3) AND (IsSystem = 0)</SQL>', 10.01, 1, 1);
-INSERT INTO ConfigurationAdmin VALUES ('Topic_SortField2', 'la_Text_Topics', 'la_topic_sortfield2_prompt', 'select', '', 'TopicText=la_Topic_Text,Posts=la_Number_of_Posts,CreatedOn=la_CreatedOn,LastPostDate=la_LastUpdate,Views=la_Topic_Views,CachedRating=la_Rating,LastPoser=la_Poster,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 3) AND (IsSystem = 0)</SQL>', 10.02, 1, 1);
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.VIEW', 'lu_PermName_Topic.View_desc', 'lu_PermName_Topic.View_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.ADD', 'lu_PermName_Topic.Add_desc', 'lu_PermName_Topic.Add_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.ADD.PENDING', 'lu_PermName_Topic.Add.Pending_desc', 'lu_PermName_Topic.Add.Pending_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.DELETE', 'lu_PermName_Topic.Delete_desc', 'lu_PermName_Topic.Delete_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.MODIFY', 'lu_PermName_Topic.Modify_desc', 'lu_PermName_Topic.Modify_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.DELETE', 'lu_PermName_Topic.Reply.Delete_desc', 'lu_PermName_Topic.Reply.Delete_desc', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.VIEW', 'lu_PermName_Topic.Reply.View_desc', 'lu_PermName_Topic.Reply.View_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.ADD', 'lu_PermName_Topic.Reply.Add_desc', 'lu_PermName_Topic.Reply.Add_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.MODIFY', 'lu_PermName_Topic.Reply.Modify_desc', 'lu_PermName_Topic.Reply.Modify_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.RATE', 'lu_PermName_Topic.Rate_desc', 'lu_PermName_Topic.Rate_desc', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REVIEW', 'lu_PermName_Topic.Review_desc', 'lu_PermName_Topic.Review_desc', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.OWNER.MODIFY', 'lu_PermName_Topic.Reply.Owner.Modify_desc', 'lu_PermName_Topic.Reply.Owner.Modify_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.REPLY.OWNER.DELETE', 'lu_PermName_Topic.Reply.Owner.Delete_desc', 'lu_PermName_Topic.Reply.Owner.Delete_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.OWNER.DELETE', 'lu_PermName_Topic.Owner.Delete_desc', 'lu_PermName_Topic.Owner.Delete_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.MODIFY.PENDING', 'lu_PermName_Topic.Modify.Pending_desc', 'lu_PermName_Topic.Modify.Pending_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.OWNER.MODIFY.PENDING', 'lu_PermName_Topic.Owner.Modify.Pending_desc', 'lu_PermName_Topic.Owner.Modify.Pending_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.OWNER.MODIFY', 'lu_PermName_Topic.Owner.Modify_desc', 'lu_PermName_Topic.Owner.Modify_error', 'In-Bulletin');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'TOPIC.LOCK', 'lu_PermName_Topic.Lock_desc', 'lu_PermName_Topic.Lock_error', 'In-Bulletin');
-
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT count(*) FROM <%prefix%>Topic WHERE Status=1', NULL, 'la_prompt_ActiveTopics', 0, 1);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS TotalTopics FROM <%prefix%>Topic', NULL, 'la_prompt_TopicsTotal', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS ActiveTopics FROM <%prefix%>Topic WHERE Status = 1', NULL, 'la_prompt_TopicsActive', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS PendingTopics FROM <%prefix%>Topic WHERE Status = 2', NULL, 'la_prompt_TopicsPending', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS DisabledTopics FROM <%prefix%>Topic WHERE Status = 0', NULL, 'la_prompt_TopicsDisabled', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS NewTopics FROM <%prefix%>Topic WHERE (NewItem = 1) OR ( (UNIX_TIMESTAMP() - CreatedOn) <= <%m:config name="Topic_NewDays"%>*86400 AND (NewItem = 2) )', NULL, 'la_prompt_NewTopics', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) FROM <%prefix%>Topic WHERE EditorsPick = 1', NULL, 'la_prompt_EditorsPickTopics', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS HotTopics FROM <%prefix%>Topic WHERE (HotItem = 1) OR (Posts >= <%m:config name="Topic_MaxHotNumber"%> AND (HotItem = 2) )', NULL, 'la_prompt_HotTopics', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS PopularTopics FROM <%prefix%>Topic WHERE (PopItem = 1) OR ( (CachedRating >= <%topic:hit_count type="top"%>) AND <%topic:hit_count type="top"%> AND (PopItem = 2) )', NULL, '(*) la_prompt_PopularTopics', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="AVG(CachedRating)" type="currency" precision="2"%> FROM <%prefix%>Topic WHERE CachedRating > 0', NULL, 'la_prompt_TopicAverageRating', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT MAX(Views) AS MaxTopicHits FROM <%prefix%>Topic', NULL, 'la_prompt_MaxTopicHits', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT MAX(CachedVotesQty) AS MaxTopicVotes FROM <%prefix%>Topic', NULL, 'la_prompt_MaxTopicVotes', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(CreatedOn)" type="date"%> FROM <%prefix%>Topic', NULL, 'la_prompt_NewestTopicDate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(CreatedOn)" type="time"%> FROM <%prefix%>Topic', NULL, 'la_prompt_NewestTopicTime', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(Modified)" type="date"%> FROM <%prefix%>Topic', NULL, 'la_prompt_LastUpdatedTopicDate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(Modified)" type="time"%> FROM <%prefix%>Topic', NULL, 'la_prompt_LastUpdatedTopicTime', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) FROM <%prefix%>ItemReview WHERE Module = \'<%modules:get_current%>\'', NULL, 'la_prompt_TopicReviews', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT COUNT(*) AS TotalPosts FROM <%prefix%>Posting', NULL, 'la_prompt_PostsTotal', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(CreatedOn)" type="date"%> FROM <%prefix%>Posting', NULL, 'la_prompt_NewestPostDate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(CreatedOn)" type="time"%> FROM <%prefix%>Posting', NULL, 'la_prompt_NewestPostTime', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(Modified)" type="date"%> FROM <%prefix%>Posting', NULL, 'la_prompt_LastUpdatedPostDate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-Bulletin', 'SELECT <%m:post_format field="MAX(Modified)" type="time"%> FROM <%prefix%>Posting', NULL, 'la_prompt_LastUpdatedPostTime', 0, 2);
- New tag implemented in the default theme, which renders all categories, up to a given depth, as a "map" of the site. This feature is very useful for spiders, which need to crawl your entire site. It's slighly different from the convential concept of site map, in that it does not show content and auxiliary pages (register, about us, etc), only In-portal categories.
-
-- Off-site Rating
- This feature displays the HTML code that is necessary to rate an In-portal item on another site. For example, it is useful for link owner who want to promote their links. They can copy/paste that HTML code onto their sites, and ask their visitors to rate the items. Same rating rules as on the In-portal site will apply to the off-site rating.
-
-Bug Fixes:
-- Wrong signature displayed in certain circumstances
-- Misc. template fixes in the Default theme
Property changes on: trunk/in-bulletin/admin/install/upgrades/readme_1_0_11.txt
-UPDATE ConfigurationAdmin SET ValueList = 'TopicText=la_Topic_Text,Posts=la_Number_of_Posts,CreatedOn=la_CreatedOn,LastPostDate=la_LastUpdate,Views=la_Topic_Views,CachedRating=la_Rating,LastPoser=la_Poster,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 3) AND (IsSystem = 0)</SQL>' WHERE VariableName IN ('Topic_SortField', 'Topic_SortField2');
-
-UPDATE Modules SET Version = '1.2.0' WHERE Name = 'In-Bulletin';
\ No newline at end of file
Property changes on: trunk/in-bulletin/admin/install/upgrades/inportal_upgrade_v1.2.0.sql
-This release is necessary to support the new features introduced in In-portal Platform 1.2.1 (such as Section Permissions in the Administrative Console).
-Please refer to the release notes for In-portal Platform 1.2.1 for more information.
Property changes on: trunk/in-bulletin/admin/install/upgrades/readme_1_2_1.txt
-This release is necessary to support the new features introduced in In-portal Platform 1.2.0 (such as Section Permissions in the Administrative Console).
-Please refer to the release notes for In-portal Platform 1.2.0 for more information.
-
-Bug fixes:
- - The ability to send private messages has been disabled for Guest users
\ No newline at end of file
Property changes on: trunk/in-bulletin/admin/install/upgrades/readme_1_2_0.txt
-This is a maintenance release to support new features introduced in In-portal Platform 1.1.8 such as Category and Item Templates and custom field mechanism refactoring.
-Please refer to the release notes for In-portal Platform 1.1.8
Property changes on: trunk/in-bulletin/admin/install/upgrades/readme_1_1_6.txt
-UPDATE ConfigurationValues SET ModuleOwner = 'In-Bulletin', Section = 'in-bulletin:configuration_search' WHERE VariableName LIKE 'SearchRel_%_topics' OR VariableName = 'Search_ShowMultiple_topic';
-UPDATE ConfigurationValues SET ModuleOwner = 'In-Bulletin', Section = 'in-bulletin:configuration_search' WHERE VariableName LIKE 'SearchRel_%_posts';
-UPDATE ConfigurationValues SET VariableName = 'Search_ShowMultiple_topics' WHERE VariableName = 'Search_ShowMultiple_topic';
-CREATE TABLE PrivateMessageBody (PMBodyId int(11) unsigned NOT NULL auto_increment, Subject varchar(255) NOT NULL default '', Body text NOT NULL, Options tinyint(3) unsigned NOT NULL default '0', ReferenceCount smallint(5) unsigned NOT NULL default '0', PRIMARY KEY (PMBodyId) );
-CREATE TABLE PrivateMessages (PmId int(11) unsigned NOT NULL auto_increment, FromId int(11) unsigned NOT NULL default '0', ToId int(11) unsigned NOT NULL default '0', FolderId tinyint(3) NOT NULL default '0', Status tinyint(1) unsigned NOT NULL default '0', PMBodyId int(11) unsigned NOT NULL default '0', CreatedOn int(11) unsigned NOT NULL default '0', PRIMARY KEY (PmId), KEY FromId (FromId), KEY CreatedOn (CreatedOn), KEY ToId (ToId) );
-ALTER TABLE Topic ADD TodayDate DATE NOT NULL, ADD TodayPosts INT(11) NOT NULL;
-
-UPDATE SearchConfig SET Priority = 1 WHERE FieldName = 'TopicText' AND TableName = 'Topic';
-UPDATE ConfigurationAdmin SET ValueList = 'TopicText=la_Topic_Text,Posts=la_Number_of_Posts,CreatedOn=la_CreatedOn,LastPostDate=la_LastUpdate,Views=la_Topic_Views,<SQL>SELECT FieldLabel as OptionName, FieldName as OptionValue FROM <PREFIX>CustomField WHERE Type=3</SQL>' WHERE VariableName = 'Topics_Sortfield';
-UPDATE ConfigurationValues SET VariableValue = 'LastPostDate' WHERE VariableName = 'Topics_Sortfield' AND ModuleOwner = 'In-Bulletin'
-UPDATE ConfigurationValues SET VariableValue = 'b:;i:;u:;ul:type|align;font:color|face|size;url:href;img:src|border' WHERE VariableName = 'BBTags';
- FROM '.$this->SourceTable.' AS pm LEFT JOIN '.$prefix.'PrivateMessageBody AS pmb ON pm.PMBodyId = pmb.PMBodyId LEFT JOIN '.$prefix.'PortalUser AS pu ON '.$join_clause.'
- WHERE '.$where;
-
- $this->QueryItemCount = QueryCount($sql);
-
- $sql .= " ".$OrderBy;
-
- return $this->Query_Item($sql, $limit);
- }
-
- function Query_Item($sql,$limit = null, $fix_method = 'set_first')
- @description:Displays the post relevance in search results
- @attrib:_displaymode:: How the relevance should be displayed<br>
- <UL>
- <LI>"Numerical": Show the decimal value
- <LI>"Bar": Show the HTML representing the relevance. Returns two HTML cells ≶td< with specified background colors
- <LI>"Graphical":Show image representing the relevance
- </UL>
- @attrib:_onimage::Zero relevance image shown in graphical display mode. Also used as prefix to build other images (i.e. prefix+"_"+percentage+".file_extension"
- @attrib:_OffBackGroundColor::Off background color of HTML cell in bar display mode
- @attrib:_OnBackGroundColor::On background color of HTML cell in bar display mode
- */
-
- }
- if(!strlen($ret))
- {
- $ret = parent::ParseObject($element);
- }
- }
- else
- {
- $fcall = $element->Execute();
- if(substr($fcall,0,8)=="{Unknown")
- {
- $ret = $this->parsetag($element->name);
- }
- else
- $ret = $fcall;
- }
- return $ret;
- }
-
-/*
- function parsetag($tag)
- {
- global $objConfig, $objUsers, $m_var_list_update, $bb_var_list_update, $var_list_update, $objSession, $bb_var_list, $bbperm;
- Grids['<inp2:m_param name="prefix"/>'].SetDependantToolbarButtons( new Array('edit','delete','approve','decline','sep3','cut','copy','move_up','move_down','sep6'));
- @description: Returns a page navigation link set for this topic, assuming the current page of the post list is page 1. If less that one page full of posts exists, nothing is returned
- @attrib:_DestTemplate:tpl: Template the links should point to
- @attrib:_PagesToList:int: Number of pages listed in the bar
- $sql = "UPDATE ".$objCountCache->SourceTable." SET Value=".(int)$PostCount.",LastUpdate=".adodb_date("U")." WHERE ItemType=30 AND ListType=30 AND ExtraId=$CatId";
- $this->adodbConnection->Execute($sql);
- }
-
- function &AddPost($PosterAlias,$Pending, $PostingText, $Subject="")
- $sql = "SELECT CachedRating FROM ".GetTablePrefix()."Topic WHERE CachedVotesQty > ".(int)$objConfig->Get("Topic_MinPopVotes")." ORDER BY CachedRating DESC,CachedVotesQty DESC LIMIT 0,".(int)$objConfig->Get("Topic_MinPopRating");
- $sql = 'SELECT '.$s.'.*,lp.PosterAlias as LastPoster,lp.CreatedOn as PLastPostDate FROM '.$s.' INNER JOIN '.$pre.'CategoryItems ON ('.$pre.'CategoryItems.ItemResourceId='.$s.'.ResourceId) ';
- $sql .= ' LEFT JOIN '.$pre.'Posting as lp ON (lp.PostingId='.$s.'.LastPostId) WHERE ';
-This tab lists all reviews of the topic, and allows the administrator to manage them. Reviews are user responses to the topic, they are similar to posts and in some instances they are redundant. However, they can be used to collect feedback from the front-end users, to provide details of the ratings, and for a few other purposes.
-Reviews have their own status, independent from the topic. They can be active, pending or disabled. The idea is very similar to the topic status only active reviews are displayed on the post listing page, or wherever specified in the theme design. The category permissions specify the status of a new review created on the front-end.
-<ul>
-<li> Enable HTML? this check box enables or disables HTML code in the review body. When checked, it will render the HTML (for example, a <B> tag will actually make the text bold). When unchecked, it will display the HTML as regular text (the <B> tag will appear exactly as <B>'). This is a very important setting, since some HTML tags can break the page layout, and in some instances can be a security concern (the Java Script, for example).
-<li> Review ID -this field is a read-only unique system ID of the review.
-<li> Created by* - this field contains the name of the user who submitted the review. This information will be displayed, along with the text of the review and the date, on the front-end, unless specified otherwise in the active theme. The administrator may change the review author by entering a different user name in this field, or by selecting it through a user picker (shortcut to a user icon will pop up the picker in a new window).
-<li> Review Text* - this field contains the main body of the review. To use the online HTML editor, click on the Editor' button next to this field.
-<li> Status - this is the status field of the review.
-<li> Priority this field contains the numerical priority of the review.
-<li> Created on this field contains the creation date of the review. It is automatically set by the system when the review is submitted, however it can be changed by the administrator. The date can be entered directly into the field, or by using the visual calendar tool.
-<li> Created at - this field contains the creation time of the review. It is automatically set by the system when the review is submitted, however it can be changed by the administrator.
-</ul>
Property changes on: trunk/in-bulletin/module_help/topics_reviews.txt
- <li> 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. </li>
- <li> 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, topics can be related to categories, links (if In-link is installed) and articles (if In-newz is installed). </li>
- <li> 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 topic to the item. </li>
- <li> Enabled – this field is the status flag of the relation. </li>
- <li> Priority – this field is the numerical priority of the relation. </li>
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/relations_edit.txt
-<p>This tab manages the categories of the topic. The list shows all categories to which this topic belongs. The administrator can add and remove additional categories on this list. At least one category must be listed, and exactly one category must be designated as the primary. The primary category determines the permissions for the topic. To designate the primary category of the topic, select the category and click on the Primary Category icon in the toolbar. The primary' marker will move from the previous Primary Category to the one you have selected. </p>
-<p>The topic will appear in all of the categories it belongs to, in the Administrative Console as well as on the front-end. </p>
Property changes on: trunk/in-bulletin/module_help/topics_categories.txt
-This section allows the administrator to specify the default values for various topic and post settings in In-bulletin.
-<ul>
-<li> Sort topics by this setting specifies the default primary sort order for the topic 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 topic), and the second dropdown the direction of the sort.
-<li> And then by this setting specifies the default secondary sort order. It is set in the same way as the primary, and used when the primary order values are ambiguous. For example, when the primary sort value is Topic Name', the secondary order will be used to sort among topics with the same name (subject).
-<li> Number of topics per page specifies the default number of topics shown per page. This value applies both to the front-end and to the Administrative Console. In the latter, this value can be changed for each session through the View menu.
-<li> Topics Per Page (Shortlist) this setting is similar to the Number of topics per page', but it applies to the front-end short topic lists only. It can be overridden by setting the tag attributes in the appropriate templates.
-<li> New Topics (Days) this setting specifies the number of days, from the date of creation, during which the topic will be automatically marked New' by the system. This setting will only apply to the topics with the New' flag set to Automatic'.
-<li> Minimum rating for a topic to be POP this setting specifies the minimum rating of a topic for it to be automatically marked Popular by the system. This setting will only apply to the topics with the Popularity flag set to Automatic. Note, that for an article to be popular it will need to meet the minimum votes requirement set below.
-<li> Maximum number of HOT topics this setting specifies the maximum number hot topics in the database. A hot topic is the one that has more views than the other topics. For example, if this option is set to 2, the In-portal system will pick the two topics with the most views and mark them as hot. (Of course, this will change real-time as the topics view counters are updated, or as this setting changes). Please note, if more than one topic has the maximum number of views, the system will still enforce the maximum number requirement; therefore, there may be situations when a topic with the most views is not marked as hot.
-<li> Minimum number of votes to consider a topic to be popular this setting specifies the minimum number of votes required for the topic rating to be effective. Usually, when only a small number of users have voted on a topic, its rating will not be statistically accurate - it is likely, that only biased users have voted. When a larger number of users vote, the rating becomes more accurate. This setting affects the popularity property of a topic topics with less than required number of votes will not be considered popular, even if their rating is high enough.
-<li> Display editor picks above regular topics this setting will force all topics, marked as Editor's pick' to be displayed above the other topics, regardless of their priority or sort order. This is very similar to the sticky' feature of other bulletin boards. Among themselves, Editor's pick' articles will be sorted according to the regular rules.
-<li> Allow Duplicate Reviews this setting specifies the period during which the same user cannot submit another review on the same topic. The time can be entered in seconds, minutes, hours, days, months or years. If it is set to zero, the users can submit reviews without this limitation. Please note, that regardless of this setting, the same user will be able to submit a review on another topic immediately after the first review.
-<li> Allow Duplicate Rating Votes - this setting specifies the period during which the same user cannot rate the same topic again. The time can be entered in seconds, minutes, hours, days, months or years. If it is set to zero, the users can rate topics without this limitation. Please note, that regardless of this setting, the same user will be able to rate another topic immediately after the first rating.
-<li> Posts to lock this setting specifies how many posts in a single topic will it take to automatically lock that topic. If it is set to zero, the topics will never be locked automatically.
-<li> Number of posts per page - specifies the number of posts shown per page inside a topic. This value applies only to the front-end.
-<li> New posts (days) - this setting specifies the number of days, from the date of posting, during which the topic will be automatically marked as having new posts in it.
-</ul>
Property changes on: trunk/in-bulletin/module_help/config_list_output.txt
-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.
-<ul>
-<li> Field Id this is a read-only field displaying the unique system ID of the custom field.
-<li> Field Name sets the internal name of the custom field. This is the name you would use to refer to the custom field in the In-tags when designing templates.
-<li> Field Label this is a read-only field, which displays the language variable name associated with the label of that field, and the value of the variable in the current language (after the colon). The label is used on the front end, and in the Administrative Console, to describe the field to the user who is entering information into it.
-<li> Show on the general tab this setting controls whether the custom field will be also displayed on the General tab in the Administrative Console, when editing the topics. It is a short cut for frequently used custom fields. All settings below apply only when this is checked.
-<li> Heading this field contains the language variable of the section heading, under which the field appear on the general tab.
-<li> Field Prompt this field contains the language variable, which text will appear as the hint bind the field.
-<li> Input Type this drop down allows the administrator to designate the type of the information stored in the custom field, by specifying the HTML control to be used on the General form.
-<li> List of Values this field contains all choices for the above HTML controls of type radio button' or drop down'. The choices must be in the format: value1 = language variabe1, value2=language variable2. For example, to create a drop down with three choices (One, Two, Three) and their respective numerical values, this field would contain the following: 1=la_one,2=la_two,3=la_three).
-</ul>
Property changes on: trunk/in-bulletin/module_help/custom_fields_list.txt
-This section contains general In-bulletin settings, which are not related to the topics. In the current version, it has only one setting. Select Module Root Category' allows the administrator to specify the module root category of In-bulletin. Clicking on the folder shortcut button will pop up a category picker.
-The module root category is used in several ways. On the front-end, in the Default theme, the top menu links each module to its module root category. Therefore, the Forums' menu item will open this category and its contents. In the Administrative Console, this setting provides a faster way to navigate in the module, as it presets the category for module-specific actions.
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/config_list_general.txt
-This section lists all possible In-bulletin 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.
Property changes on: trunk/in-bulletin/module_help/email_settings_list.txt
-This tab contains all images associated with the topic. 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 specify the image details.
-<ul>
-<li> Image ID a read-only field, the internal system ID of the image, guaranteed to be unique throughout the system. It is blank when a new image is created.
-<li> Name this field contains the image name, used on the front-end, in side the In-tags to refer to this image.
-<li> Alt Value this field contains the text value, which will be displayed in the alt' tag of the image on the front end, in side the page HTML code, and when a mouse pointer hovers over the image (in Internet Explorer).
-<li> Status this field contains the status of the image, enabled or disabled.
-<li> Primary this flag designates the primary image. There can be only one primary image per list (for one topic). When you check this box on an image, the previous primary image is unset (if there is more than one image in the list).
-<li> Priority this field contains the numerical priority of the image.
-<li> Thumbnail location (upload from PC) Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the in-portal/kernel/images' directory.
-<li> Thumbnail location (remote URL) Here you can enter a remote URL address of an image. It will be linked from the remote server.
-<li> Same As Thumbnail This check box sets the full-size image to be the same as the thumbnail image. When this option is checked, you cannot upload a full-size image.
-<li> Thumbnail location (upload from PC) - Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the in-portal/kernel/images' directory.
-<li> Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/images_edit.txt
-This tab contains the main attributes of the topic.
-<ul>
-<li> Enable HTML? - this check box enables or disables HTML code in the topic name. It does not affect the posts in this topic. When checked, it will render the HTML (for example, a <B> tag will actually make the text bold). When unchecked, it will display the HTML as regular text (the <B> tag will appear exactly as <B>'). This is a very important setting, since some HTML tags can break the page layout, and in some instances can be a security concern (the Java Script, for example).
-<li> Topic ID this read-only field displays the unique internal system ID of the topic.
-<li> Name * - this field contains the topic name, or subject.
-<li> Posted by* - this field contains the name of the user who started the topic by posting the first message in it. This information will be displayed on the first post of the topic on the front-end, unless specified otherwise in the active theme. The administrator may change the topic author, by entering a different user name or by selecting it through a user pop up (shortcut to a user icon).
-<li> Topic Locked this field toggles the topic lock attribute. When a topic is locked, it is not possible to make new posts in it.
-<li> Status this field contains the topic status.
-<li> New this field controls how the topic new' status is calculated by In-bulletin.
-<li> Hot this field controls how the topics hot status is calculated by In-bulletin. In automatic mode, In-bulletin will consider as hot the X number of topics with the most views. X is defined under the In-bulletin Output options.
-<li> Popularity this field controls how the topics pop status is calculated by In-bulletin. In automatic mode, In-bulletin will consider those topics as popular, which have at least X number of votes and have a rating above the predefined threshold. The number of votes and rating threshold are defined in the Output options section.
-<li> Editor's Pick this flags sets the Editor's Pick attribute of the topic. This is very similar to the sticky' feature of other bulletin boards.
-<li> Priority - this field contains the numeric topic priority.
-<li> Created on * - this field contains the creation date of the topic. It is automatically set by the system when the topic is created, however it can be changed by the administrator. The date can be entered directly into the field, or by using the visual calendar tool.
-<li> Created at - this field contains the creation time of the topic. It is automatically set by the system when the first post is submitted, however it can be changed by the administrator.
-<li> Modified on * - this field contains the modification date of the topic. It is automatically set by the system when the topic is changed, or any posts in it have changed, however it can be changed by the administrator. The date can be entered directly into the field, or by using the visual calendar tool.
-<li> Modified at - this field contains the modification time of the topic. It is automatically set by the system when the topic is changed, or any posts in it have changed, however it can be changed by the administrator.
-<li> Rating this field contains the numeric rating of the topic. The rating is calculated as the average value of all ratings selected by users for this topic. The range of the value is predefined, and displayed to the right as a hint. The administrator can manually change the rating if necessary.
-<li> Votes this field contains the number of votes for the topic. Each time a user votes (selects rating) for the topic on the front-end, this value is incremented by one. This value is important for the rating calculating, it is used in the formula to calculate the average. The administrator can manually change the number of votes if necessary.
-<li> Views this field contains the number of topic's views. This value is incremented each time a user views the topic. The administrator can manually change the number of views if necessary.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/topics_edit.txt
-This tab contains a list of all relations of this topic. To create a new relation, click the New' button (two opposite green arrows with a little sun). This will pop up an item picker, where you can choose one category or item of any module that supports relations.
-<ul>
-<li> 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.
-<li> 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, topics can be related to categories, links (if In-link is installed) and articles (if In-newz is installed).
-<li> 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 topic to the item.
-<li> Enabled this field is the status flag of the relation.
-<li> Priority this field is the numerical priority of the relation.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/topics_relations.txt
-This section allows the administrator to configure the front-end search options, and the advanced search options.
-This section lists all fields representing topic attributes. Next to each field, there is a Simple Search' checkbox, which includes this field in the simple search query. By default, only the Topic Text' field is included. In general, it makes sense to include only the fields, which may contain text in them, otherwise when a visitor searches for a text keyword, the non-textual fields will be not searchable. Next, there is a Weight' text box, in which the administrator can designate the importance of each field during a search. The fields with a larger weight will be more important then the fields with the lower weight. This is used when calculating the topic's relevance to the search keyword, for sorting of the results. The last column is the Advanced Search' check. It designates whether a particular field should be displayed on the Advanced Search' page and be searchable by the visitors. By default, all fields are included.
-Below the list of fields are the Topic Relevance settings.
-<ul>
-<li> Increase importance if field contains a required keyword by this specifies the percentage by which the weight of a field will increase, when a required keyword is found in that field. A required keyword is one that is preceded with a +' in the search key phrase.
-<li> Search Relevance depends on _ % keyword the percentage of relevance that comes from the keyword being found in that topic.
-<li> Search Relevance depends on _ % popularity - the percentage of relevance that is based on the topic's popularity.
-<li> Search Relevance depends on _ % rating - the percentage of relevance that is based on the topic's rating.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/config_list_search.txt
-This tab lists all reviews of the topic, and allows the administrator to manage them. Reviews are user responses to the topic, they are similar to posts and in some instances they are redundant. However, they can be used to collect feedback from the front-end users, to provide details of the ratings, and for a few other purposes.
-Reviews have their own status, independent from the topic. They can be active, pending or disabled. The idea is very similar to the topic status only active reviews are displayed on the post listing page, or wherever specified in the theme design. The category permissions specify the status of a new review created on the front-end.
-<ul>
-<li> Enable HTML? this check box enables or disables HTML code in the review body. When checked, it will render the HTML (for example, a <B> tag will actually make the text bold). When unchecked, it will display the HTML as regular text (the <B> tag will appear exactly as <B>'). This is a very important setting, since some HTML tags can break the page layout, and in some instances can be a security concern (the Java Script, for example).
-<li> Review ID -this field is a read-only unique system ID of the review.
-<li> Created by* - this field contains the name of the user who submitted the review. This information will be displayed, along with the text of the review and the date, on the front-end, unless specified otherwise in the active theme. The administrator may change the review author by entering a different user name in this field, or by selecting it through a user picker (shortcut to a user icon will pop up the picker in a new window).
-<li> Review Text* - this field contains the main body of the review. To use the online HTML editor, click on the Editor' button next to this field.
-<li> Status - this is the status field of the review.
-<li> Priority this field contains the numerical priority of the review.
-<li> Created on this field contains the creation date of the review. It is automatically set by the system when the review is submitted, however it can be changed by the administrator. The date can be entered directly into the field, or by using the visual calendar tool.
-<li> Created at - this field contains the creation time of the review. It is automatically set by the system when the review is submitted, however it can be changed by the administrator.
-</ul>
Property changes on: trunk/in-bulletin/module_help/reviews_edit.txt
-This tab contains all images associated with the topic. 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 specify the image details.
-<ul>
-<li> Image ID a read-only field, the internal system ID of the image, guaranteed to be unique throughout the system. It is blank when a new image is created.
-<li> Name this field contains the image name, used on the front-end, in side the In-tags to refer to this image.
-<li> Alt Value this field contains the text value, which will be displayed in the alt' tag of the image on the front end, in side the page HTML code, and when a mouse pointer hovers over the image (in Internet Explorer).
-<li> Status this field contains the status of the image, enabled or disabled.
-<li> Primary this flag designates the primary image. There can be only one primary image per list (for one topic). When you check this box on an image, the previous primary image is unset (if there is more than one image in the list).
-<li> Priority this field contains the numerical priority of the image.
-<li> Thumbnail location (upload from PC) Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the in-portal/kernel/images' directory.
-<li> Thumbnail location (remote URL) Here you can enter a remote URL address of an image. It will be linked from the remote server.
-<li> Same As Thumbnail This check box sets the full-size image to be the same as the thumbnail image. When this option is checked, you cannot upload a full-size image.
-<li> Thumbnail location (upload from PC) - Using this control, you can upload an image from the workstation you are at to the In-portal server. The image will be stored in the in-portal/kernel/images' directory.
-<li> Thumbnail location (remote URL) - Here you can enter a remote URL address of an image. It will be linked to from the remote server.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-bulletin/module_help/topics_images.txt