Table of Contents
Known Escenic Bugs
Lucy 2.0-3
* The admin pages for this plugin doesn't handle more than one index :(
Core
* Sometimes the SectionHierarchy? table is corrupted. The effect of this is that you cannot search for articles in the corrupted section. The article:list tag will not list articles from this section either. There is a fix for this [here|SectionHierarchyFix?]
ArticleListCache? (Version 4.1-4b)
* There seem to be an issue with the ArticleListCache? is not updated when articles change sections and are republished. We got articles listen in latest "innenriks" even though they where no longer in this section. Flushing the ArticleListCache? fixes the problem, so we set ArticleListCache?.validSeconds to 1800 so at least the cached list is flushed every 30 minutes.
Article relations and <relation:articles>
* Consider this situation:
article(#1) <--(relation)--> article(#2) <--(relation)--> article(#3)
When we do an <article:use articleId="1"/>, the ArticleXmlCache is filled with article #1, and also with the articles related, in this case article #2. This is something which was to be expected. Now consider this code:
<article:use articleId="1">
<relation:articles id="rel">
<util:valueof param="rel"/><br/>
</relation:articles>
</article:use>
This code correctly prints the related article(#2), but when we check the ArticleXmlCache, it is also filled with all articles related to article(#2), in this case article (#3). Note: Even if we exclude certain article types in the <relation:articles> tag with the excludeArticleTypes attribute, the cache is filled with the transitively related articles to those excluded articles! This all causes database traffic in case the articles weren't found in the cache.
In our ([telegraaf.nl|http://www.telegraaf.nl]) situation of many, many related articles, this has an incredible impact on the performance of our system. We thought about relating user feedback articles not directly to the article, but to an intermediate related article, which did not work since all relations to that related article were retrieved anyway once an <article:relation> tag was used.
Forum 1.1-3e41
If you save a forum article as deleted in Studio, then it will not be listed in the forum plugin web admin interface. But it will be returned as part of the Collection from the forum tags like <forum:groups>. Escenic has promissed to fix this in the next release of the plugin.
Content Studio and F-Secure Client Security 6.0
This is not a bug in Escenic, but nevertheless a potential gotcha for Studio users. The HTTP scanning module of F-Secure Client Security 6.00 and 6.01 disconnects Content Studio whenever the user tries to perform a search or upload a picture. The workaround is to disable the HTTP scanning functionality in F-Secure Client Security.
Article list 30 day limit
When using the article:list tag, the result are limited to articles that have been published in the past 30 days. Older articles will not appear in the list. This can be overriden in the features.properties files by using:
# 8760 = 1 year article.list.age.max=8760 # 720 = 30 days article.list.age.default=720
Another way to show older articles in a section is directly using the API. For example:
RelationLoader.getArticleIdsInHomeSection
RelationLoader relationLoader = IOAPI.getAPI().getRelationLoader();
PresentationLoader presentationLoader = PresentationLoader.getInstance();
int[] articleIds = relationLoader.getArticleIdsInHomeSection(thisSection);
PresentationArticle article;
for(int i=0; i<articleIds.length; i++) {
article = presentationLoader.getArticle(articleIds~[i]);
}
Problems with import of eventInstance - (ece 4.1-6 and oracle)
This dosent work on OracleDB but seems to work on other DBs. This could be driver-dependent.
A workaround is to add a empty scheduleId feeld on the eventInstance-tag, like this:
<eventInstance scheduleId="">
The other attributes like start and endtime should be as normal.
