2010-06-02 02:41 av Patric Jansson
En sommarhälsning från Maria Widegren, HR Manager på Polopoly
Polopoly fyller 10 år och det vill vi fira med dig! Onsdagen den 16 juni 17.00-20.00 är det ”Sommarmingel” hos Atex Polopoly. Vi börjar med att visa spännande produktnyheter och fyller sedan vår terass med lite mat och dryck och mycket trevliga människor.
Ta gärna med en kollega!
Alströmergatan 22. OSA till 10@polopoly.com senast 14/6
2010-06-01 04:31 av Niklas Olsson
Version 9.16.1 is a tuned version of 9.16.0 which contains a number of improvements that couldn’t be fitted in the regular fixpack format. Fixpacks are for bug fixes and minor enhancements. This release goes beyond that to form a minor release of it’s own. The major improvements in version 9.16.1 revolves around performance of the editorial GUI.
One of the major features in 9.16.1 is a collection of performance enhancements which will make the Polopoly GUI run a lot quicker for most customers. This has been achieved mainly by consolidating and slimming down static resources in the GUI and minimizing the number of reloads of such resources.
Examples include:
polopoly.css/polopoly now have correct cache headers. (For development it is possible to disable this feature by commenting out the StaticFileServlet in web.xml)Performance has also been improved by optimizing the way lock information is checked and by tuning the default cache time for lock information. Many default content lists have also been modified to only show the top 30 entries instead of all entries in the list. To show the remaining entries a ”show all” button has been added. This behavior is configurable. See change note: #11782.
Apart from the performance improvements there are a number of other useful fixes in version 9.16.1.
The in-context editing has been updated. When saving content, the save will now also propagate down to any in-context content being edited within the same template. Furthermore, editing an in-context content and then pressing edit on the content it is visible in will result in the context content keeping its state.
Sounds complex? Try it out by editing the Alt-text of any image in the Standard article in Greenfield Times.
The categorization capabilities in version 9.16.1 has been extended to include site specific categorization. A new categorization tab has been added to the site template where you can configure the category dimensions to use. Every category dimension has been extended to support a custom Atex Text Mining plan. See upgrade notes for more information.
In 9.16.0, profiling support for Elements was introduced. This capability has been extended to GUI widgets in version 9.16.1. It is now possible to profile Orchid Widget lifecycle operations such as init(), render() and update() with the Metrics Reporting tool. See the Developer’s Guide under ”Profiling Polopoly web applications” for details.
The constant battle for browser compatibility continues in version 9.16.1. Issues with popup menus in combination with frames on Internet Explorer 7 and 8 have been addressed. The Velocity code in flash.vm now also generates Internet Explorer-friendly markup.
These are the major enhancements in version 9.16.1. See the detailed change list in the forum
2010-04-09 03:06 av Patric Jansson
Polopoly 9.16 introduces two major features. The interactive preview mode has been enhanced to include WYSIWYG style on-page editing of teasers for page local tuning of content. In addition to that, the integration with Atex Content H11 has been enhances to support a much more sophisticated workflow.
One of the major features in 9.16 is the extension of on-page editing in Greenfield Times to include interactive editing of teasers directly in the browser. This enables page local tuning of the text and appearance of stories to fit the page context. The changes are stored on the teaser object, leaving the underlying article intact. On-page editing includes both texts and images. All text can be edited, title size and spacing can be controlled using sliders in the new interactive menu. Images zoom pan and crop vertically. In order to preserve the layout, image widths always follow the current layout. There is also an API that enables developers to add on.page editing to their own custom elements.
Following the principle of one logical repository, the integration with Atex Content H11 has been brought to the next level. New features include single sign-on support, real time editorial inbox in Polopoly to track repository changes, preview from H11 and online decoration from H11 using popup Polopoly templates.
Apart from these major features, 9.16 includes many enhancements and optimizations, among which the following can be mentioned:
Element profiling
Continuing the effort to provide developers with Site Engine trouble shooting and debugging tools, 9.16 includes support for element level profiling of pages. The Metrics tool breaks down page performance into execution time per element on a statistical basis. Combined with a simple stress test using JMeter for example, the element metrics tool gives the developer a graphical overview that makes finding performance bottlenecks a matter of reading a simple bar graph.
The statistical profiling of elements complements the existing RenderStats, Troubleshooter and Status pages and the combined toolset
allows for very detailed inspection and diagnostics of a Polopoly installation.
The new Metrics tool can be found under http://<domain>/polopolydevelopment.
Ldap group performance has been optimized by introducing reload of ldap groups only when a group has changed and the possibility to configure if groups in group should be supported. Turning of groups of group support makes loading of groups a lot faster (100 times faster is not uncommon). The following ldap properties has been added:
See the section called “Ldap group enhancement” for issues when upgrading.
and more…
see the Change list for details
Taggar: 9.16, polopoly, release notes2010-03-31 05:46 av Niklas Olsson
När din polopolyinstans växer och därmed källkodsträdet kan det vara bra att jämna mellanrum se över och ta bort eventuell kod som inte längre används. En del av detta är inputmallar som blir utdaterade med tiden. Jag tänkte därför tipsa om hur man kan ta bort gamla inputmallar som ligger och skräpar i systemet och det är några steg att hålla i huvudet.
Denna beskrivning är baserad på användandet av ramverket Pluris så alla detaljer kanske inte är relevanta för ditt projekt men principen bör framgå i alla fall.
package se.kth.ite.cortina.policy.article;
import com.polopoly.cm.policy.ArticlePolicy;
/**
* This policy is used as policy for deprecated templates.
*/public class DeprecatedArticlePolicy extends ArticlePolicy {
}
<?xml version="1.0" encoding="ISO-8859-1"?>
<template-definition version="1.0" xmlns="http://www.polopoly.com/polopoly/cm/app/xml">
<input-template name="it.article.coursesearch" label="template.article.coursesearch.label">
<policy>se.kth.ite.cortina.policy.article.DeprecatedArticlePolicy</policy>
<editor>se.kth.ite.cortina.widget.app.OLocalizedContentTopPolicyWidget</editor>
<viewer>se.kth.ite.cortina.widget.app.OLocalizedContentTopPolicyWidget</viewer>
</input-template>
</template-definition><entry mode="remove"> för att ta bort mallen ur avdelningen för mallar, på så sätt försvinner den ur alla mallistningar också.
<contentlist>
<!-- REMOVED DUE TO DEPRECATION -->
<entry mode="remove">
<metadata>
<referredContent>
<contentid>
<externalid>it.article.coursesearch</externalid>
</contentid>
</referredContent>
</metadata>
</entry>
</contentlist>Klar!
Senaste från supportforumet Polopolysnack på Twitter