-INSERT INTO ConfigurationAdmin VALUES ('News_SortField', 'la_Text_Articles', 'la_news_sortfield_pompt', 'select', '', 'Title=la_Article_Title,Excerpt=la_Article_Excerpt,Author=la_Article_Author,CreatedOn=la_Article_Date,Hits=la_Article_Hits,CachedRating=la_Article_Rating,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 2) AND (IsSystem = 0)</SQL>', 10.01, 1, 1);
-INSERT INTO ConfigurationAdmin VALUES ('News_SortField2', 'la_Text_Articles', 'la_news_sortfield2_pompt', 'select', '', 'Title=la_Article_Title,Excerpt=la_Article_Excerpt,Author=la_Article_Author,CreatedOn=la_Article_Date,Hits=la_Article_Hits,CachedRating=la_Article_Rating,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 2) AND (IsSystem = 0)</SQL>', 10.02, 1, 1);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT count(*) FROM <%prefix%>News WHERE Status=1', NULL, 'la_prompt_ActiveArticles', 0, 1);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS TotalArticles FROM <%prefix%>News', NULL, 'la_prompt_ArticlesTotal', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS ActiveArticles FROM <%prefix%>News WHERE Status = 1', NULL, 'la_prompt_ArticlesActive', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS PendingArticles FROM <%prefix%>News WHERE Status = 2', NULL, 'la_prompt_ArticlesPending', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS DisabledArticles FROM <%prefix%>News WHERE Status = 0', NULL, 'la_prompt_DisabledArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS ArchivedArticles FROM <%prefix%>News WHERE Archived = 1', NULL, 'la_prompt_ArticlesArchived', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS NewArticles FROM <%prefix%>News WHERE (NewItem = 1) OR ( (UNIX_TIMESTAMP() - CreatedOn) <= <%m:config name="News_CatNewDays"%>*86400 AND (NewItem = 2) )', NULL, 'la_prompt_NewArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) FROM <%prefix%>News WHERE EditorsPick = 1', NULL, 'la_prompt_EditorsPickArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS HotArticles FROM <%prefix%>News WHERE (HotItem = 1) OR (Hits >= <%m:config name="News_MaxHotNumber"%> AND (HotItem = 2) )', NULL, 'la_prompt_HotArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) FROM <%prefix%>News WHERE LeadStory = 1', NULL, 'la_prompt_LeadStoryArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) FROM <%prefix%>News WHERE LeadCatStory = 1', NULL, 'la_prompt_CategoryLeadStoryArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT <%m:post_format field="AVG(CachedRating)" type="currency" precision="2"%> FROM <%prefix%>News WHERE CachedRating > 0', NULL, 'la_prompt_ArticleAverageRating', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) AS PopularArticles FROM <%prefix%>News WHERE (PopItem = 1) OR ( (CachedRating >= <%article:hit_count type="top"%>) AND <%article:hit_count type="top"%> AND (PopItem = 2) )', NULL, '(*) la_prompt_PopularArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT MAX(Hits) AS MaxHitsArticles FROM <%prefix%>News', NULL, 'la_prompt_MaxHitsArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT MAX(CachedVotesQty) AS MaxVotesArticles FROM <%prefix%>News', NULL, 'la_prompt_MaxVotesArticles', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT <%m:post_format field="MAX(CreatedOn)" type="date"%> FROM <%prefix%>News', NULL, 'la_prompt_NewestArticleDate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT <%m:post_format field="MAX(Modified)" type="date"%> FROM <%prefix%>News', NULL, 'la_prompt_LastArticleUpdate', 0, 2);
-INSERT INTO StatItem VALUES (DEFAULT, 'In-News', 'SELECT COUNT(*) FROM <%prefix%>ItemReview WHERE Module = \'<%modules:get_current%>\'', NULL, 'la_prompt_ArticleReviews', 0, 2);
-
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.VIEW', 14, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.VIEW', 14, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.VIEW', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.ADD.PENDING', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'FAVORITES', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.VIEW', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.RATE', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.REVIEW', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY.PENDING', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.DELETE', 13, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.VIEW', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.ADD', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.DELETE', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.MODIFY', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'FAVORITES', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.VIEW', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.DELETE', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.MODIFY', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.RATE', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.REVIEW', 11, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'CATEGORY.VIEW', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'FAVORITES', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.VIEW', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.RATE', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.REVIEW.PENDING', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD.PENDING', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY.PENDING', 12, 1, 0, {NewsCatId});
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.VIEW', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.DELETE', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.MODIFY', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.RATE', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.REVIEW', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.REVIEW.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.MODIFY.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.DELETE', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:innews_general.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:innews_general.edit', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_output.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_output.edit', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_search.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_search.edit', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_email.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_email.edit', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_custom.view', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_custom.add', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_custom.edit', 11, 1, 1, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'in-news:configuration_custom.delete', 11, 1, 1, 0);
-UPDATE ConfigurationAdmin SET ValueList = 'Title=la_Article_Title,Excerpt=la_Article_Excerpt,Author=la_Article_Author,CreatedOn=la_Article_Date,Hits=la_Article_Hits,CachedRating=la_Article_Rating,<SQL>SELECT Prompt AS OptionName, CONCAT("cust_", FieldName) AS OptionValue FROM <PREFIX>CustomField WHERE (Type = 2) AND (IsSystem = 0)</SQL>' WHERE VariableName IN ('News_SortField', 'News_SortField2');
-
-UPDATE Modules SET Version = '1.2.0' WHERE Name = 'In-News';
\ No newline at end of file
Property changes on: trunk/in-news/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-news/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.
-
-New In-newz features:
- - Added RSS support - importing and exporting In-newz articles into the RSS format
\ No newline at end of file
Property changes on: trunk/in-news/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
\ No newline at end of file
Property changes on: trunk/in-news/admin/install/upgrades/readme_1_1_6.txt
-UPDATE ConfigurationValues SET ModuleOwner = 'In-News', Section = 'in-news:configuration_search' WHERE VariableName LIKE 'SearchRel_%_article' OR VariableName = 'Search_ShowMultiple_article';
-UPDATE ConfigurationAdmin SET ValueList = 'ReviewText=la_common_ReviewText,CreatedOn=la_common_CreatedOn' WHERE VariableName IN ('News_SortReviews', 'News_SortReviews2');
-
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'NEWS.ADD.PENDING', 'lu_PermName_News.Add.Pending_desc', 'lu_PermName_News.Add.Pending_error', 'In-News');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'NEWS.MODIFY.PENDING', 'lu_PermName_News.Modify.Pending_desc', 'lu_PermName_News.Modify.Pending_desc', 'In-News');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'NEWS.OWNER.MODIFY', 'lu_PermName_News.Owner.Modify_desc', 'lu_PermName_News.Owner.Modify_error', 'In-News');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'NEWS.OWNER.MODIFY.PENDING', 'lu_PermName_News.Owner.Modify.Pending_desc', 'lu_PermName_News.Owner.Modify.Pending_error', 'In-News');
-INSERT INTO PermissionConfig VALUES (DEFAULT, 'NEWS.OWNER.DELETE', 'lu_PermName_News.Owner.Delete_desc', 'lu_PermName_News.Owner.Delete_error', 'In-News');
-
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.ADD.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.MODIFY.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.MODIFY.PENDING', 15, 0, 0, 0);
-INSERT INTO Permissions VALUES (DEFAULT, 'NEWS.OWNER.DELETE', 15, 0, 0, 0);
- 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:
-- Misc. template fixes in the Default theme
\ No newline at end of file
Property changes on: trunk/in-news/admin/install/upgrades/readme_1_0_10.txt
-UPDATE SearchConfig SET Priority = 2 WHERE FieldName = 'Title' AND TableName = 'News';
-UPDATE SearchConfig SET Priority = 1 WHERE FieldName = 'Excerpt' AND TableName = 'News';
-UPDATE SearchConfig SET Priority = 1 WHERE FieldName = 'Author' AND TableName = 'News';
-UPDATE SearchConfig SET Priority = 1 WHERE FieldName = 'Body' AND TableName = 'News';
-
-UPDATE ConfigurationAdmin SET ValueList='Title=la_Article_Title,Excerpt=la_Article_Excerpt,Author=la_Article_Author,CreatedOn=la_Article_Date,Hits=la_Article_Hits,CachedRating=la_Article_Rating,<SQL>SELECT FieldLabel as OptionName, FieldName as OptionValue FROM <PREFIX>CustomField WHERE Type=2</SQL>' WHERE VariableName='News_Sortfield';
-UPDATE ConfigurationAdmin SET ValueList='Title=la_Article_Title,Excerpt=la_Article_Excerpt,Author=la_Article_Author,CreatedOn=la_Article_Date,Hits=la_Article_Hits,CachedRating=la_Article_Rating,<SQL>SELECT FieldLabel as OptionName, FieldName as OptionValue FROM <PREFIX>CustomField WHERE Type=2</SQL>' WHERE VariableName='News_Sortfield2';
-
-UPDATE Modules SET Version = '1.0.7' WHERE Name = 'In-News';
\ No newline at end of file
Property changes on: trunk/in-news/admin/install/upgrades/inportal_upgrade_v1.0.7.sql
-This tab contains the main attributes of the article.
-<ul>
-<li> News Article Id this read-only field displays the unique internal system ID of the article.
-<li> Title * - this field contains the article name.
-<li> Author* - this field contains the name of the user who is the designated author of the article. It can be an In-portal user, or somebody else this field accepts plain text as well as user names. By default, the article author is the user who creates the article. The administrator may change the article author, by entering a different user name, by selecting it through a user pop up (shortcut to a user icon), or by entering any other text in this field.
-<li> Article Body* this field contains the main body of the article. The shortcut to the HTML editor next to this field will open a pop-up with an online HTML editor
-<li> Article Excerpt - this field contains the summary of the article body. It should be significantly shorter then the main text. The option to Generate from the article body' will automatically take a portion of the main text and insert it into the excerpt when you save the article.
-<li>Automatic Filename specifies whether the Filename used for mod_rewrite should be generated automatically from the article name, or entered manually. If checked, the Filename will be generated from the article name, replacing all special characters ( !@#$%^&*()+|\=-~`{}][:;,./?>< ) by the underscore character (_), and all multiple underscores with a single underscore. If the resulting name ends with an underscore followed by number, an additional letter will be appended, since the names ending with a number are reserved for system use. The resulting name will also be checked for uniqueness, and if its not unique, additional letters will be appended to the end of the name
-<li>Custom Filename the filename used for the URL generation when using mod_rewrite. The field is disabled if Automatic Filename is On. If Automatic Filename is Off, the administrator may enter the filename manually, however it will still be checked for uniqueness, special characters and whether it ends with a number. In such cases the Filename will be automatically corrected before saving.
-<li> Status this field contains the article status.
-<li> New this field controls how the article new' status is calculated by In-newz.
-<li> Hot this field controls how the articles hot status is calculated by In-newz. In automatic mode, In-newz will consider as hot the X number of articles with the most views. X is defined under the In-newz Output options.
-<li> Popularity this field controls how the articles pop status is calculated by In-newz. In automatic mode, In-newz will consider those articles 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 article.
-<li> Site Lead Story this flags sets the Site Lead attribute of the article. The default theme is designed for one Site Lead articles, but you may change that depending on your implementation needs.
-<li> Category Lead Story this flags sets the Category Lead attribute of the article. The default theme is designed for three lead articles in each category, but you may change that depending on your implementation needs.
-<li> Priority - this field contains the numeric article priority.
-<li> Created on * - this field contains the creation date of the article. It is automatically set by the system when the article 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> Start Date - this field contains the date starting on which the article should be displayed on the front-end. It is automatically set by the system to be the same as the creation date, 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> Archivation Date - this field contains the date when the article will be archived. Archived articles are not displayed on the front-end. This date is automatically set by the system when the article is created, using the creation date plus the predefined number of days, set in the In-newz configuration. It can be changed by the administrator, by being entered directly into the field, or by using the visual calendar tool.
-<li> Rating this field contains the numeric rating of the article. The rating is calculated as the average value of all ratings selected by users for this article. 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 article. Each time a user votes (selects rating) for the article 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> Hits this field contains the number of article's hits. This value is incremented each time a user views the article. The administrator can manually change the hits if necessary.
-</ul>
Property changes on: trunk/in-news/module_help/articles_edit.txt
-This tab contains a list of all relations of this article. 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, articles can be related to categories, links (if In-link is installed) and topics (if In-bulletin 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 article 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-news/module_help/relations_edit.txt
-This tab contains all images associated with the article. 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 article). 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>
Property changes on: trunk/in-news/module_help/articles_images.txt
-This section allows the administrator to specify the default values for various article settings in In-newz.
-<ul>
-<li> Order articles by this setting specifies the default primary sort order for the article 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 article), 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 Article Title', the secondary order will be used to sort among articles with the same title.
-<li> Number of articles per page specifies the default number of articles 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> Articles Per Page (Shortlist) this setting is similar to the Number of articles per page', but it applies to the front-end short article lists only. It can be overridden by setting the tag attributes in the appropriate templates.
-<li> Number of days for an article to be NEW this setting specifies the number of days, from the date of creation, during which the article will be automatically marked New' by the system. This setting will only apply to the articles with the New' flag set to Automatic'.
-<li> Minimum rating for an article to be POP this setting specifies the minimum rating of an article for it to be automatically marked Popular by the system. This setting will only apply to the articles 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 articles this setting specifies the maximum number hot articles in the database. A hot article is the one that has more views than the other articles. For example, if this option is set to 2, the In-portal system will pick the two articles with the most views and mark them as hot. (Of course, this will change real-time as the articles view counters are updated, or as this setting changes). Please note, if more than one article has the maximum number of hits, the system will still enforce the maximum number requirement; therefore, there may be situations when an article with the most views is not marked as hot.
-<li> Minimum # of votes for rating consideration this setting specifies the minimum number of votes required for the article rating to be effective. Usually, when only a small number of users have voted on an article, 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 an article articles 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 articles this setting will force all articles, marked as Editor's pick' to be displayed above the other articles, regardless of their priority or sort order. Among themselves, Editor's pick' articles will be sorted according to the regular rules.
-<li> Number of days to archive articles automatically this setting contains the number of days to be added to the article creation date to set the archivation date.
-<li> Allow Duplicate Reviews this setting specifies the period during which the same user cannot submit another review on the same article. 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 article immediately after the first review.
-<li> Allow Duplicate Rating Votes - this setting specifies the period during which the same user cannot rate the same article again. The time can be entered in seconds, minutes, hours, days, months or years. If it is set to zero, the users can rate articles without this limitation. Please note, that regardless of this setting, the same user will be able to rate another article immediately after the first rating.
-<li> Reviews Per Page - specifies the default number of reviews shown per page. This value applies both to the front-end and to the Administrative Console.
-<li> Sort reviews by - this setting specifies the default primary sort order for the review listings. It applies both on the front-end, and in the Administrative Console in the article management section, Reviews tab. The first dropdown allows to select the field (an attribute of the review), 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 Review Text', the secondary order will be used to sort among reviews with the same body.
-</ul>
Property changes on: trunk/in-news/module_help/config_list_output.txt
-This tab contains a list of all relations of this article. 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, articles can be related to categories, links (if In-link is installed) and topics (if In-bulletin 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 article 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-news/module_help/articles_relations.txt
-This section allows the administrator to manage the article custom fields. The article custom fields are useful when you need to store additional information about the articles. For example, the articles may have such custom fields, as the language of the article, the safe audience rating, the country where the even occurred, etc. All custom fields will be automatically used in the Administrative Console, in the Article 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 articles. 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>
\ No newline at end of file
Property changes on: trunk/in-news/module_help/custom_fields_list.txt
-This section contains general In-newz settings, which are not related to articles. In the current version, it has only one setting. Select Module Root Category' allows the administrator to specify the module root category of In-newz. 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 News' 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.
-Logically, the module root category defines the portion of the catalog tree that is designated only for the In-newz categories. If you are using the categories to store items from multiple modules, this setting is not applicable to your situation.
\ No newline at end of file
Property changes on: trunk/in-news/module_help/config_list_general.txt
-This section lists all possible In-newz 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
Property changes on: trunk/in-news/module_help/email_settings_list.txt
-This tab contains all images associated with the article. 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 article). 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>
Property changes on: trunk/in-news/module_help/images_edit.txt
-<p>This tab manages the categories of the article. The list shows all categories to which this article 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 article. To designate the primary category of the article, 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>
-The article will appear in all of the categories it belongs to, in the Administrative Console as well as on the front-end. All of the article's attributes (such as the Category Lead Story) will be applied in all categories as well.
Property changes on: trunk/in-news/module_help/articles_categories.txt
-This section allows the administrator to configure the front-end search options, and the advanced search options.
-This section lists all fields representing article attributes. Next to each field, there is a Simple Search' checkbox, which includes this field in the simple search query. By default, only the Title, the Excerpt', the Author' and the Body' fields are 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 article'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 Article 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 article.
-<li> Search Relevance depends on _ % popularity - the percentage of relevance that is based on the article's popularity.
-<li> Search Relevance depends on _ % rating - the percentage of relevance that is based on the article's rating.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-news/module_help/config_list_search.txt
-This tab lists all reviews of the article, and allows the administrator to manage them. Reviews are user responses to the article. They can be used to collect feedback from the front-end users, to provide details of the ratings, and for many other purposes.
-Reviews have their own status, independent from the article. They can be active, pending or disabled. The idea is very similar to the article status only active reviews are displayed on the article detail 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. The date can be entered directly into the field, or by using the visual calendar tool.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-news/module_help/reviews_edit.txt
-This tab lists all reviews of the article, and allows the administrator to manage them. Reviews are user responses to the article. They can be used to collect feedback from the front-end users, to provide details of the ratings, and for many other purposes.
-Reviews have their own status, independent from the article. They can be active, pending or disabled. The idea is very similar to the article status only active reviews are displayed on the article detail 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. The date can be entered directly into the field, or by using the visual calendar tool.
-</ul>
\ No newline at end of file
Property changes on: trunk/in-news/module_help/articles_reviews.txt
- @description:Returns a URL setting the link to the article
- @attrib:_template:tpl:Template URL should point to
-*/
-/*
- @field:article.cat_link
- @description:Returns a URL setting the article to the current article and the article's category to the current category
- @attrib:_template:tpl:Template URL should point to
-*/
-/*
- @field:article.category
- @description:Return a category field from the article's category
- @attrib:_cattag::Category field to parse
-*/
-/*
- @field:article.reviews
- @description:Return the number of reviews for the article
- @attrib:_today:bool:Count reviews added today only
-*/
-/*
- @field:article.new
- @description:returns text if article's status is "new"
- @attrib:_label:lang: Text to return if status is new
-*/
-/*
- @field:article.pop
- @description:returns text if article's status is "popular"
- @attrib:_label:lang: Text to return if status is popular
-*/
-/*
- @field:article.hot
- @description:returns text if article's status is "hot"
- @attrib:_label:lang: Text to return if status is "hot"
-*/
-/*
- @field:article.pick
- @description:returns text if article's status is "hot"
- @attrib:_label:lang: Text to return if status is "hot"
-*/
-/*
- @field:article.rating
- @description:Displays the article rating
- @attrib:_displaymode:: How the rating should be displayed<br>
- <UL>
- <LI>"Numerical": Show the decimal value
- <LI>"Text": Show the text version
- <LI>"Graphical":Show images representing the rating
- </UL>
- @attrib:_onimage::on image tick shown in graphical display mode
- @attrib:_offimage::off image tick shown in graphical display mode
- @attrib:_separator::In graphical display mode, this html is placed between each tick image
-*/
-/*
- @field:article.custom
- @description:Returns a custom field
- @attrib:_customfield::field name to return
- @attrib:_default::default value
-*/
-/*
- @field:article.fullpath
- @description:The full category path of the item
-*/
-/*
- @field:article.relevance
- @description:Displays the article 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(!isset($ret) || !strlen($ret))
- $ret = parent::ParseObject($element);
- }
- else
- {
- $ret = $this->parsetag($element->name);
- }
- return $ret;
- }
-
-
- function parsetag($tag)
- {
- global $n_var_list, $var_list, $n_var_list_update, $var_list_update, $objConfig;
- $sql = "SELECT ".$this->SourceTable.".*, ".$ml_formatter->LangFieldName('CachedNavbar')." AS CachedNavbar,".GetTablePrefix()."Category.CategoryId as CategoryId FROM ".$this->SourceTable." ";
- $sql = "SELECT CreatedOn FROM ".GetTablePrefix()."News INNER JOIN ".GetTablePrefix()."CategoryItems AS cat ON (".GetTablePrefix()."News.ResourceId = cat.ItemResourceId) WHERE cat.CategoryId=$CategoryId AND CreatedOn>=$cutoffdate ORDER BY CreatedOn DESC ";
- $sql = "SELECT CachedRating FROM ".GetTablePrefix()."News WHERE CachedVotesQty > ".(int)$objConfig->Get("News_MinPopVotes")." ORDER BY CachedRating DESC,CachedVotesQty DESC LIMIT 0,".(int)$objConfig->Get("News_MaxHotNumber");
- ORDER BY Hits DESC LIMIT 0,'.$objConfig->Get('News_MaxHotNumber');
- $rs = $ado->Execute($sql);
-
- $cached_value = 0;
- while ($rs && !$rs->EOF) {
- if ($rs->fields['Hits'] > 0) {
- $cached_value = $rs->fields['Hits'];
- }
- $rs->MoveNext();
- }
- }
-
- return $cached_value;
- }
-}
-
-function News_Custom($ResourceId, $tag)
-{
- $adodbConnection = &GetADODBConnection();
-
- $fieldname= substr($tag, 7);
-
- $sql = "SELECT Value FROM ".GetTablePrefix()."CustomMetaData LEFT JOIN ".GetTablePrefix()."CustomField USING (CustomFieldId) where ".GetTablePrefix()."CustomMetaData.ResourceId=$ResourceId AND ".GetTablePrefix()."CustomField.FieldName='$fieldname'";
- Grids['<inp2:m_param name="prefix"/>'].SetDependantToolbarButtons( new Array('edit','delete','approve','decline','sep3','cut','copy','move_up','move_down','sep6'));
- if (strlen($carpconf['desctags'])) $this->top.=trim(preg_replace("#<(?!".$carpconf['desctags'].")(.*?)>#is","<\\1\\2>",$this->cdescription))."<p>\n";
- if (!($cfp=fopen($carpconf['cachepath']."/$cachefile",'w'))) {
- CaRPError("Unable to create/open RSS cache file.");
- xml_parser_free($xml_parser);
- return;
- }
- }
- $CaRPRedirs=array();
- if ($fp=OpenRSSFeed($url)) {
- if ($carpconf['maxdesc']) $rss_parser->truncdesc=$carpconf['truncdesc']?$carpconf['truncdesc']:($carpconf['maxdesc']-strlen($carpconf['posttruncdesc']));
- while ($data=preg_replace("/&(?!lt|gt|amp|apos|quot)(.*\b)/is","&\\1\\2",fread($fp,4096))) {
- if (!xml_parse($xml_parser,$data,feof($fp))) {
- CaRPError("XML error: ".xml_error_string(xml_get_error_code($xml_parser))." at line ".xml_get_current_line_number($xml_parser));