Reading List will be discontinued

Mar 11, 2014

Later in the year we will discontinue our Reading List service in favour of Wallabag.

If you haven’t heard of Wallabag, it is a self-hostable, free software read later alternative to Instapaper, Readability, Pocket1, and of course our own Reading List.2 We are happy to have been able to contribute Full-Text RSS 3.1 to handle Wallabag’s content extraction.

You can download Wallabag and install it on your own server, or try their hosted service. It also comes with a number of browser extensions and mobile apps.

Our Reading List service will continue to work for existing users, but sometime around August we will take it down. Before then we plan to release the source code for anyone interested.

  1. Wallabag used to be called Poche (the French word for pocket), until Pocket got nasty and threatened legal action

  2. We developed Reading List before we’d heard about Wallabag. Now that it’s available, and appears to be actively maintained, we have decided to focus on our existing tools instead of continuing work on Reading List. 

PDF Newspaper 2.5

Feb 4, 2014

We’ve just released a new version of PDF Newspaper, our tool to create printable versions of web articles and feeds. Here’s what’s new.

HTML output

The biggest change in this release is the ability to request HTML output instead of PDF. It may seem odd to offer HTML output in an application called PDF Newspaper, but browser support for recent CSS specifications means that browsers are now quite adept at producing print layouts very similar to what we were generating before as PDF files.

The HTML view we generate contains a print stylesheet to produce a somewhat similar result to our PDF output when printing. There are a number of differences though:

  • You can edit the text before printing.
  • Unlike our PDF output, columns are balanced (roughly same height) in this view.
  • You can convert to PDF using your own PDF creator (e.g. Acrobat) provided it has a PDF print driver.1
  • Our print stylesheet will use 3 columns if you print A4 landscape or larger, 2 columns for A4 portrait, and 1 column for A5 or smaller.2
  • Right-to-left languages can now be displayed.3
  • If you know HTML/CSS, you can make changes to the template.4


Here’s a short video demonstrating some of the features of HTML output — mainly the multi-column CSS rules being applied in print view, based on paper size and orientation.

Live Examples

To load the feeds we used in the video with PDF Newspaper, use the links below:

PDF screenshots (A4)

multi-story mode single-story mode
PDF Newspaper output PDF Newspaper output

More screenshots

PDF changes

We’ve made changes to our PDF output to address problems with PDF.js rendering (used by recent versions of Firefox to render PDFs in the browser) and iOS rendering. If you used a previous version of PDF Newspaper and had trouble seeing your PDFs on Firefox or iOS devices, this new version should work better.

We also now offer a Letter template in addition to A4 and A5.

Combining stories from different sources

If you’d like to generate a newspaper by selecting articles from different sources, you’ll have to first create a feed from those articles. The easiest way to do that is to use our Feed Creator. Here you can paste URLs, one per line, and create a static feed containing only the URLs you’ve entered.

Let’s say we want to create a newspaper from the following articles:

We would paste the URLs to these articles in the Feed Creator field provided and click Create Simple RSS. This will generate a feed containing the 3 items above:

Now if we give this feed URL to PDF Newspaper, here’s what it can produce:

Try it!

PDF Newspaper 2.5 is live now at

Request parameters

Using the form we provide is the easiest way to get started, but if you want to call PDF Newspaper programmatically, the following table of request parameters will tell you what PDF Newspaper can accept. These parameters should be used in a HTTP GET request to makepdf.php.

Parameter Value Description
url string URL of a feed or a single web article.
mode multi-story (default), single-story
Use for feeds. You can customise the newspaper title.
Use to process a single article (even with feeds). Produces a more compact layout, omitting newspaper title.
template A4 (default), Letter, A5 Sets PDF paper size. The A4 and Letter templates produce a larger, two-column PDF. The A5 template produces a smaller, single-column PDF.
output pdf (default), pdf-download, html
Your browser decides what to do with the generated PDF - either it will load the PDF within the browser, download it, or prompt you to choose an action.
Tells the browser that you want to download the PDF rather than view it inside the browser. It will either download automatically or prompt you to choose an action.
Outputs the generated HTML without producing a PDF. Produces a result faster than the pdf options, but uses a print stylesheet to achieve a somewhat similar result when you print. Note: the template parameter currently has no effect with HTML output - if printing, you will set the paper size in the print dialog that appears. For best results printing or creating a PDF from this view, please use Firefox.
dir auto (default), ltr, rtl Sets text direction: auto = browser decides, ltr = left-to-right, rtl = right-to-left. This parameter currently only works for HTML output.
images 1 or 0 (default) Include images. Pass 1 to enable.
date 1 or 0 (default) Include date and time for each article (if available). Pass to 1 to enable.
sub string This can be a tagline, slogan, or the main title if using single story mode. If omitted, the default one set in the config file will be used.

Multi-story parameters — These parameters only apply when multi-story mode is enabled (see mode parameter above).

Parameter Value Description
title string Newspaper title. If you’d like to use the default title image instead, delete the title.
order desc (default) or asc Determines how stories will be ordered by date. Pass asc for chronological ordering (oldest story in the feed appears first). Pass desc to have the latest stories shown first.
date_start string If the feed contains dates for feed items, you can restrict items returned by specifying a start date. Any items with a publish date earlier than date_start will be omitted from the output.
date formats
You can pass an absolute date using the YYYY-MM-DD format, e.g. 2014-01-24 or a relative one, e.g. last week or yesterday.
date_end string If the feed contains dates for feed items, you can restrict items returned by specifying an end date. Any items with a publish date later than date_end will be omitted from the output. See note above about using relative and absolute dates.

Full-Text RSS integration — When you give PDF Newspaper a URL to a web article, Full-Text RSS is automatically used to extract its content. For a partial feed, you will have to tell PDF Newspaper if you’d like it passed to Full-Text RSS for full content. (Full-Text RSS integration can be configured or disabled within the config file.)

Parameter Value Description
fulltext 1 or 0 (default) Use for partial feeds. Runs feed through Full-Text RSS before processing result. Pass 1 to enable.
use_extracted_title 1 or 0 (default) Normally feed titles take precedance over extracted titles. Pass 1 to tell Full-Text RSS to replace feed titles with those it extracts. (Requires Full-Text RSS version 3.2 or greater. Has no effect without fulltext parameter.)

API keys — If you want to restrict access to PDF Newspaper you can specify API keys in the config file. URLs produced by PDF Newspaper can be used publically, e.g. linked from a website, so the API key should not appear in the final URL.

Parameter Value Description
api_key string A key that you’ve entered in the config. If you’re calling PDF Newspaper programattically, it’s better to use the key and hash parameters (see below) to hide the actual key in the HTTP request. If this parameter is used, PDF Newspaper will produce the key and hash values automatically and redirect to a new URL to hide the API key. If you’d like to link to a PDF publically while protecting your API key, make sure you copy and paste the URL that results after the redirect. If you’ve configured PDF Newspaper to require a key, an invalid key will result in an error message.
key integer This should be the index number which identifies an API key without revealing it. It must be passed along with the hash parameters. See the config file.
hash string A SHA-1 hash value of the API key (actual key, not index number) and requested URL, concatenated. It must be passed along with the key parameter. In PHP, for exmaple: $hash = sha1($api_key.$url);

Required parameters: url must be supplied.


  • New: HTML output with editable content and print stylesheet (Firefox recommended for printing)
  • New: Output parameter to choose between PDF, HTML, and PDF for download
  • New: Text direction parameter (only for HTML output for the time being)
  • New: PDF Letter template for US users
  • New: Form field to specify start date (if feed items include dates)
  • New: Config option to set PDF filename - see $options->filename
  • New: Config option to enable/disable output caching - see options->caching
  • New: Config option to for whitelisting/blacklisting hosts - see $options->allowed_hosts and $options->blocked_urls
  • Font subsetting disabled in PDF output to improve iOS and PDF.js rendering
  • PDF is no longer generated if there are no items to include (e.g. no articles published after start date)
  • Table showing available request parameters now shown in index.php
  • Full-Text RSS updated to version 3.1
  • HTML Purifier updated to version 4.6.0
  • SimplePie updated to version 1.3.1 
  • PHP Typography updated
  • Humble HTTP Agent updated
  • TCPDF fonts updated
  • TCPDF minor update (latest version not compatible with our modifications)
  • Plus other minor fixes/improvements

  1. If you have a PDF print driver, you’ll see it in your list of printers when you go to print. If you have Acrobat, you’ll probably see ‘Adobe PDF’ in the list. If you get an error creating a PDF using Adobe PDF, go into Properties and in Adobe PDF Settings, uncheck ‘Rely on system fonts only; do not use document fonts’. 

  2. Not all browsers currently support multi-column printing. Notably, Chrome, which supports multi-column layouts in its regular view, does not support it in its print view. In our tests, Firefox (tested with version 26) and IE (version 11) had the best support for multi-column printing. 

  3. By default we rely on the browser to decide (based on the content) whether it should show the result as right-to-left (we use dir=”auto” attribute). You can override this, however, by passing &dir=rtl in the querystring to makepdf.php. 

  4. To make changes to the template used in the HTML view, save a copy of html_template.html as custom_html_template.html and edit it. The custom file will be used if it exists. This only applies to users of our self-hosted package. 

Feed Creator: Our new tool to monitor web pages using custom feeds

Oct 19, 2013

If you’ve ever wanted to treat set of links on a website as a web feed (so you can subscribe and be notified of updates), you might find our new feed creation tool useful.1

You can use the tool to create a feed from almost any publicly accessible webpage. That includes:

  • Twitter streams
  • Public Facebook timelines
  • Search results on a website

Here are a few cases and examples where you might want to use Feed Creator:

  • A webpage has no feed of its own
    For example: Twitter accounts or public Facebook timelines2
  • There is a feed, but not for the items that interest you
    For example: Search results on a website or a category on a news site

How does it work?

Our service sits in between your feed reader (e.g. NewsBlur, Feedly, IFTTT) and the publisher’s website.

If a website already offers a feed for the information you’re interested in, this is typically how your feed reader gets updates after you subscribe to the feed:

Feed Reader communicates directly with publisher's server

If there is no suitable feed, our service produces one based on the information you give it. You then subscribe to the feed we generate. Now when a feed reader requests the feed, here’s what happens behind the scenes:

Feed Reader communicates with publisher's server via the Feed Creator service

Getting started

To use the feed creator you will need:

  1. The URL of the source page which contains the items you’re interested in.
  2. Some knowledge of HTML (and CSS for advanced selection)

Before we go on, I’d like to stress that if there’s already a feed associated with the webpage, you should use it instead of relying on this tool.3 Feed Creator extracts links from the webpage by looking at its HTML.4 If a website gets redesigned, HTML changes could break our generated feeds.

Extracting links: 3 different ways

If you supply only the page URL, Feed Creator will return the first set of links it encounters in the HTML. This will include things like navigation elements - which usually appear at the top of the page. That’s probably not what you want. Below we’re going to look at 3 different ways to extract the items you’re interested in.

1. Selecting links using URL segments

The simplest way to narrow results to the set of links you are interested in is to see if you can find a URL segment that’s exclusive to that set of links.


The official Noam Chomsky website has a page listing Chomsky’s articles. There is no RSS feed linked on the page nor in the HTML header.5 The first set of links point to other pages on the site (recent updates, books, audio and video) - these are navigation elements which we’re not interested in. Below those, the article links appear. These are the links we want to use in our RSS feed and monitor for updates.

If you hover your cursor over a few of the article links you’ll find that they all contain the segment ‘articles/’ - e.g. ‘articles/20130902.htm’, ‘articles/20130604.htm’. So it looks like ‘articles/’ is common to all these links. If you now hover over the navigation links, you’ll find: ‘books.htm’, ‘audionvideo.html’, ‘articles.htm’ (note, no forward slash here).

So, our brief examination suggests that the URL segment ‘articles/’ is exclusive to the article links we’re interested in. Let’s go ahead and try creating a feed from this information:

  1. Visit the Feed Creator site
  2. In the page URL field enter:
  3. In the ‘keep links if link URL contains’ field: articles/
  4. Click ‘Preview’ and wait for results.
  5. If results look okay, you can subscribe to our generated feed using the button provided.

It’s important to note that what we’re trying to do is to identify patterns within the page that will not only return items that are currently on the page, but also pick up future entries. That’s why we don’t want to select links using identifiers that only apply to existing links (e.g. ‘20130902.htm’ or ‘20130604.htm’).

2. Selecting links using class and id attributes

Sometimes you’ll need more than a URL segment to select the links you want. If you know some HTML you can check the source of the page and see if there are class or id attributes associated with the links, their parent elements, or ascendants.6 If you find some, you can use those values to restrict your search to those elements.


John Pilger’s website already offers an RSS feed for his articles, so this is one of those cases where you shouldn’t really use this tool. But I’ll use it as an example.

If you visit the articles page and click ‘Expand all articles’, you’ll see his latest articles at the top. If you examine the HTML, you’ll find the entries are marked up as follows:

<span class="entry">
    <a href="{{ article url }}" class="entry-link">{{ article title }}</a>
    <span class="entry-date" title="1 day ago">{{ article date }}</span>
    <a href="#" rel="nofollow" class="show-intro" id="showintro-815">Show intro...</a>
    <span class="intro" id="article-intro-815">{{ article description }}</span>

Each article entry is contained in a <span> element with the class attribute value “entry”. This element holds two link (<a>) elements. The actual article title and URL appear in the <a> element with class “entry-link”.

So let’s try creating a feed from this information:

  1. Visit the Feed Creator site
  2. In the page URL field enter:
  3. In the ‘look for links inside…’ field enter: entry-link
  4. Click ‘Preview’ and wait for results.

Here’s a direct link to results.

3. Selecting links using CSS selectors

For more advanced selection, you can use CSS selectors. Note that this selection method cannot be used in combination with the previous one, and we don’t yet offer form fields for entering selectors, so you’ll have to create the URL by hand. You can refer to the information in the request parameters table to see how these should be used.


First, let’s see how the previous example looks like using a CSS selector:

  1. Page URL:
  2. item parameter: .entry-link or a.entry-link

Here’s a direct link. It should produce the same results as in the previous example.

Now let’s look at a more complicated example: a Twitter timeline. If you view a Twitter timeline in your browser, this is how tweets are currently marked up in HTML:7

<div class="tweet original-tweet js-stream-tweet ...">
    <span class="icon dogear"></span>
    <div class="content">
        <div class="stream-item-header">
            <a class="account-group ..." href="..." data-user-id="...">
                <img class="avatar js-action-profile-avatar" src="..." alt="">
                <strong class="fullname js-action-profile-name ...">...</strong>
                <span class="username ..."><s>@</s><b>...</b></span>
            <small class="time">
                <a href="{{ tweet URL }}" class="tweet-timestamp ..." title="{{ date }}">
                    <span class="_timestamp js-short-timestamp ...">1h</span>
        <p class="js-tweet-text tweet-text">{{ tweet text }}</p>

Notice that the tweet URL appears in the element which holds the date, and there is no suitable title (unless you consider the tweet text to be the title) to use for feed items. So here we’re going to tell Feed Creator to omit item titles, and to use the tweet URL as the item URL. We could tell it to use the tweet text (p.tweet-text) as the description, but then we wouldn’t know who tweeted it (could be a retweet), so we’ll tell it to use the parent element (div.content). Here’s what our parameters will look like:

  1. Page URL: (use any Twitter account you like)
  2. item: .original-tweet
  3. item_url: a.tweet-timestamp
  4. item_desc: .content
  5. item_title: 0

If we stop here, we’ll find that the description will contain text from elements within div.content which we’re not interested in. So let’s remove these elements using the strip parameter: .stream-item-footer,.username,.js-short-timestamp

Here’s a direct link.

Hosted service with self hosting option

Our hosted service (the one accessible on is free to use. It is intended for personal use and to show you what the feed creator application can do. We limit results to 10 items per feed and we’ll soon start caching webpages for around 30 minutes.

If our service turns out to be popular for subscribing to Twitter/Facebook feeds, there’s a possibility that these companies will block access. If you want to avoid that happening, you should consider running your own copy of the code. You’ll find information on the self-hosted package and a ‘buy’ button at the bottom of the Feed Creator page.

That’s all for now. Hope you found the guide useful. Feel free to comment or post a question on our help page if you like.

  1. We announced this service in May, but have since improved it and made it available for self-hosting. 

  2. Facebook and Twitter don’t like RSS. When you visit a public account on either site, you will not find RSS links on the page nor in the HTML header (which is how other services usually detect if there’s a feed associated with a page). Facebook can in fact produce a feed for public pages, but you’ll have to do some work to get the feed URL. Twitter no longer produces a feed, so you’ll have to use a service like ours. 

  3. If a site publishes a feed, they’re generally committed to maintaining it. People who subscribe to the feed depend on it to get notified of updates, so it’s not really in the publisher’s interest to remove the feed. 

  4. We don’t yet support pages which rely exclusively on Javascript to load content. 

  5. used to link to one of my earlier projects which produced an RSS feed for their latest news page. They then moved to Blogger, which provides feeds. Now they appear to be using Facebook for their latest news. 

  6. The easiest way to find class and id attributes to use as selectors is to use Firefox’s page inspector. Simply right click a link or some other element on the page and select ‘Inspect Element’. 

  7. When viewing the HTML source of a webpage, or using the Firefox page inspector, you should bear in mind that it might not be seen the same way by our software. Servers may send back different responses depending on where the request originates, and what it contains. Another issue is how the HTML response is parsed. Even if the server sends back the same response to us as it does to your browser, your browser could parse it differently to our application (which uses PHP’s built-in HTML parser). 

Gothenburg Book Fair

Sep 3, 2013

We have a small stand at the Gothenburg Book Fair this year. If you’re going, you’ll find us at stand F02:41.

We’ll be demoing some of our current applications and introducing a new one. More information soon.

Update: Thanks to everyone who showed up. The new application we demoed is the Reading List—we’ll have more to say about this soon.

Google Reader closing down

Jun 6, 2013

As you may have heard, Google is shutting down Google Reader on July 1 2013.

We’ve never been fond of Google Reader, mainly for these reasons:

  • It’s not free software
  • It’s a Google product
  • It doesn’t treat feeds equally—updating popular feeds (high subscriber counts) much more frequently than less popular feeds

So, how will this affect our users?

Some time ago, to deal with Google Reader’s selective treatment of feeds, we introduced monitored feeds to subscribers of our premium Full-Text RSS service. This was an experimental feature specifically aimed at Google Reader users. Feeds marked in this way are periodically checked and updates sent to Google Reader using pubsubhubbub.

Seeing as Google Reader will be shutting down, we will soon be removing this feature for new users. Existing users who have set up monitored feeds will receive an email with more information sometime after July 1 2013. - a very nice news reader

Finally, if you’re looking for a simple, clean news reader, by Elbert Alias looks very nice. It’s free software (GPL) written in PHP, and there’s a hosted version you can sign up for and try out.

Create a feed from a web page or list of URLs

May 21, 2013

We’ve put up a new experimental service to help you create RSS feeds for sites which do not offer their own.

The idea is that you give it the web page URL which contains the links you’re interested in, and one or more clues to help us find and return the correct links. (This is a simple tool at this stage, so it does not try to guess the appropriate set of links to use in the feed. We may play around with something like that at a later time.)

Example: Extracting links from a web page

In this example we’ll use the articles page on John Pilger’s website. It already offers a feed, so there’s no reason to create one with this tool, but we’ll use it as an example anyway.

On our create feed page, enter the following information and click ‘Create Feed’:

Extract URLs containing: /articles/

The first field asks for the URL of the web page which contains the links we’re interested in. We’re not interested in all links on this page, e.g. navigation links, so the next field allows us to enter a string that must appear in a URL if it is to be extracted. It so happens that all the article URLs on this website contain the path segment /articles/, so that’s what we enter in the second field.

There is also a third field, not used in this example, which allows us to narrow the search to HTML elements which contain the class or id attribute value we supply.

The resulting URL you see in your browser’s address bar can be used like any other feed - you can subscribe to it in your news reader, or any other tool which takes RSS as input.

If you followed the example above, the URL would be

Create a static feed from list of URLs

Finally, you can also create a static feed with your own set of URLs. Simply paste the URLs, one per line, into the form and click ‘Create Feed’. We’ll return that list as a simple, static RSS feed. There’s no extra processing here, so you won’t get item titles or anything else in the output. You can now copy the URL shown in your browser’s address bar and use it to create a PDF Newspaper or convert it to a fuller feed, with titles and content, using Full-Text RSS.

Any feedback appreciated.

Full-Text RSS 3.2 released

May 14, 2013

Full-Text RSS 3.2 is now available for purchase.

What’s new?

There are quite a few improvements in this release (see below), but the main one is probably the ability to include excerpts in the output.

You can enable excerpts by passing ‘&summary=1’ in the query string. This will place a plain text excerpt from the extracted content in the description element.

Another addition is the ability to omit full-text content from the output. So if you want Full-Text RSS to return only excerpts from a feed or web page, you can pass &summary=1&content=0 in the query string.

Note: if both content and excerpts are requested, the excerpt will be placed in the description element and the full content inside content:encoded. If excerpts are not requested, the full content will go inside the description element — where it has always appeared in previous versions.

Why does the location of the content change when excerpts are requested? According to the RSS advisory: “Publishers who employ summaries should store the summary in description and the full content in content:encoded, ordering description first within the item. On items with no summary, the full content should be stored in description.”

The full changelog for this release:

  • A short excerpt from the first few lines of the extracted content can now be included in the output (pass &summary=1 in querystring, see $options->summary in config file for more info)
  • Full content can now be excluded from the output (pass &content=0 in querystring, see $options->content in config file for more info)
  • Site config files can now be automatically updated from our GitHub repository (URL to call visible in admin area)
  • Site config files updated for better extraction
  • PHP Readability updated to be more lenient when pruning HTML
  • Language detection library updated
  • HTML meta refresh redirects now also followed
  • APC stats (if APC is available on your server) now visible in admin area
  • Bug fix: Duplicate find_string and replace_string values in site config files no longer removed (thanks Fabrizio!)
  • Bug fix: MIME type actions now applied when following single page URLs
  • Other minor fixes/improvements

Customers who purchased earlier versions should shortly receive an email with either a free download link (if purchased in the last 12 months) or links to a discounted upgrade.

Hosting our applications

May 12, 2013

We’re often asked to recommend web hosts for our applications. We’ve now added a new help page for Full-Text RSS doing just that. The suggestions apply to our other PHP tools too.

Hope you find it useful.

Code repository updated

Apr 18, 2013

While we sell the latest versions of our software to sustain our project, our code repository contains older versions of some of our code along with code we’ve ported to PHP from other languages for use in our tools.

We recently updated the repository. Here’s what’s new:

PHP Readability

PHP Readability is a library which detects and extracts the content block (article text) from a given HTML document. It is a PHP port of the original Readability code developed by Arc90.

In Full-Text RSS 3.1, we updated PHP Readability to preserve more images and YouTube, Vimeo and Viddler embeds. This update is now available to download.

We’ve also made it compatible with Composer by adding a composer.json file to the package and listed it on Packagist. See below for an example of how you can use this in a new project with Composer.

Term Extractor

Term Extractor is a library used to extract terms from English language texts. It is a PHP port of Topia’s Term Extractor.

Term Extractor is now also compatible with Composer and listed in Packagist. See below for an example of how to use this with Composer.

To use Term Extractor as a web service, we sell a self-hosted package - useful if you’d like to switch away from relying on Yahoo’s Term Extractor.

Full-Text RSS 2.9.5

Version 2.9.5, which was released 2012-04-29, is now freely available. The previous version in our code repository was 2.8 (released 2011-05-30). Here’s the changelog.

This does not contain the site config files we include with purchased copies, but these are now all available online. If you’d like to keep yours up to date using Git, follow the steps below:

  1. Change into the site_config/standard/ folder
  2. Delete everything in there
  3. Using the command line, enter:
    git clone .
  4. Git should now download the latest site config files for you.

To update the site config files again, you can simply run git pull from the directory.

If you find Full-Text RSS useful, there are some nice changes in 3.0 and 3.1 which you might want to consider - if you’re not already a customer. :)

Using PHP Readability and Term Extractor with Composer

  1. Install Composer if you haven’t already.
  2. At the root of your project, create a file called composer.json (or update it) with the following content:
        "require": {
            "fivefilters/php-readability": "1.0.*",
    	"fivefilters/term-extractor": "1.0.*"
  3. From the command line, run composer install (or composer update if your project already uses Composer).
  4. The new files should be downloaded into the vendor folder and ready to use.

Full-Text RSS 3.1 released

Mar 6, 2013

Full-Text RSS 3.1 is now available for purchase. The changelog entry for this release:

  • PHP Readability updated to preserve more images/videos
  • Site config files updated for better extraction
  • SimplePie updated
  • New site config option favour_feed_titles and request parameter use_extracted_title to allow extracted titles to be used in generated feed
  • Remove image lazy loading (looks for markup used by
  • <category> elements appearing inside <item> elements are now preserved in generated feed
  • <media:thumbnail> elements now preserved
  • Allow multiple <media:content> elements (previously only one was preserved)
  • Bug fix: No more self-closing iframe elements
  • Bug fix: Fixed manifest.yml to prevent error message when deploying to AppFog
  • Other minor fixes/improvements

Customers who purchased in the last year should have received an email with a free download link.

« To the past Page 1 of 2

Recommended articles and tweets

Follow us on Twitter for more