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.