polopolyforum.se

Yesterday evning Atex Polopoly released the 10.2 version of Polopoly. Heres a summary from there support site.

Atex Tablet Publishing 1.1

Together with Polopoly 10.2, we introduce a new version of our tablet offering – Atex Tablet Publishing, or ATP. The goal of ATP is to provide customers with an efficient workflow for quickly publishing and updating tablet editions. It is built around a templated write-to-fit workflow, with a high degree of automation, using on-page editing for the final touch-up.

It is an end to end offering built on Polopoly that contains everything needed for tablet publishing: From Polopoly serving as the backend to an iPad application supporting daily issues, Apple iTunes subscriptions and HTML5 based rendering with support for videos, image galleries and more.

Atex Tablet Publishing is a stand-alone product with a separate license and does not require an existing Polopoly installation or license to use.

For more information about ATP, please contact your local sales rep.

Polopoly 10.2

One feature that we have automatically enabled in Polopoly 10.2 is auto-save. Auto-save allows any input template to be saved at regular intervals, so that work doesn’t disappear if the session times out or something crashes. we have enabled it by default for the standard article but you can set it yourself for any input template.

We have also added a ton of improvements with an eye to improving the Content File Servlet.

For example, with Polopoly 10.2 it is possible to explicitly assign MIME types for files imported on to content, which will then be served with that same MIME type when served from the Content File Servlet.

Another nice improvement is that it is now possible to have per-content authentication by letting the policy containing the files implement ContentFilePermissions.

The last thing we have done, but certainly not the least, is that the Content File Servlet now supports serving request for files with the Range and If-Range HTTP headers, allowing it to, for example, serve video files to iOS devices transparently.

A few other small features include some Moderation GUI improvements, a new render directive, #renderwithfallback, that allows you to include fallback code on the page if rendering fails, and updates to interactive preview that allows you to save a content in interactive preview that you have in edit mode in the Polopoly GUI at the same time.

Unified Web Service

The Unified Web Service we introduced as an early access feature in 9.16 has also had a few improvements. For example, it now supports tag categories in its standard format, and has improved error messages that show who locked what content in case an import fails, so that you have a chance to rectify that.

Community efforts

Finally, not related to the release, we hope you check out some of the cool stuff we have made available open source that you can use to improve your daily workflow. Check out this blog post on the polopolyforum.se community for more info.

General Release Notes

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.

Interactive on-page editing of teasers

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.

Support for H11

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.

… and a lot more.

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.

Optimized loading of LDAP groups

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:

• ldapNestedGroupsSupported (default false)
• ldapTimestampSupported (default true)
• ldapCreateTimestampAttribute
• ldapModifyTimestampAttribute

See the section called “Ldap group enhancement” for issues when upgrading.

Other selected improvements

• Possibility to start front servers in disconnected mode
• Bundled JBoss upgraded to upgraded to version 4.0.5
• Quick cropping of teasers
• Possibility to reindex Solr from the command line

and more…

see the Change list for details

Polopoly släppte idag version 9.13.2 och bland nyheterna så hittar vi bl.a en lösning för den inrapporterade buggen om att listningen av användare uteblir när man närmar sig 1000 st och kör Oracle som databas. Andra nyheter är bl.a. ändrade standardinställningar för minnet på index-, xml-, statistics- och pollservern, förbättrad dokumentation och att man tagit bort knappen för att manuellt bygga om sina index.

Kommande diskussion

Vi vill passa på att pusha för att vi senare kommer återkomma med en diskussion om hur vi (d.v.s. alla läsare på polopolyforum.se) skulle vilja att Polopoly hanterar sin information gällande nya releaser. Där vi hoppas på era förslag och synpunkter på hur man kan förbättra handhavandet för nya versionsreleaser, men mer om det i kommande inlägg.

Här kommer hela listan som den presenteras på Poloploys supportsida:

Polopoly släpper sin nästa version, Polopoly 9.12 den 6/4 och vi har fått en förhandstitt på vad som är nytt.

Nyheterna i version 9.12 är till stor del fokuserade på Greenfield Times och är bl.a. följande:

• Communityplattformen har flyttats till Greenfield Times som nu också går mer mot att vara en produktionsinstalltion än tidigre. Man ska i slutändan kunna använda den som den är ”out of the box” i en produktionsmiljö om man t.ex. är en mindre eller medelstor tidning eller liknande.
• Registrering som användare där man kan skapa sig ett konto och logga in/logga ut och ”best practicies” på hur man bygger en stomme för personalisering, detta utan att förstöra cachningen.
• Bloggar. Man kan som ovannämnd registrerad användare skapa sig en blogg och producera inlägg. Inmatningen i ett inlägg sker via en FCK-editor. Än så länge går det inte att kommentera inläggen men de har i alla fall grundstommen för bloggen klar. Mer funktionalitet kommer i senare minor releases.
• ACAP-funktionalitet (ACAP – Automated Content Access Protocol) som används för att styra access till innehåll när det gäller sökmotorernas spindlar. Ersättare av robots.txt

Något som är nytt fr.o.m. i år är att Polopoly kommer släppa sina nya versioner på förutbestämda datum. D.v.s. inte funktionsbaserade releaser som det har varit tidigare. Detta gör att vi kommer veta när nästa version kommer och ungefär vad som kommer finnas med. Polopoly kommer självklart inte kunna vara exakta i vad som kommer med en release, men efter ett antal itterationer in i 9.12 så ser tempot ut att följa deras uppsatta mål ganska väl.

Polopoly har också lovat att polopolyforum ska får en demo inför varje ny release så vi användare kan få bättre vetskap om vad som kommer. Personligen känner jag att det har saknats tidigare. Jag har många gånger utvecklat funktionalitet som senare dykt upp i produkten.

Polopoly visade också sin Roadmap för 2009, vi kommer att skriva om den så fort vi hinner!