Glaring, no. But I think the we should let folks know the extra capabilities of:
Code:
limitlength() still works mostly as originally designed. New options - even if the entry is already short enough, all tags
can still be stripped from the field if a third parameter is set to true, ex:
instance.limitlength(175, 'descriptionfield', true)
Instead of providing a number limit, one can opt for the keyword 'strip'. If one does so, the
result is that tags are stripped from the field but no limit is imposed, ex:
instance.limitlength('strip', 'descriptionfield')
And that, of course if one is using an ATOM feed, it must be specified in the addFeed entry:
Code:
freeform.addFeed("Babblefish", "http://bblfish.net/blog/blog.atom", "atom"
) //Specify "label" plus URL to feed, optional feed type, defaults to "rss" - "atom" is the other option
Finally, we should let them know that for the ticker and scroller they can now use addregexp(). The usage is the same as with gfeedfetcher. But in the scroller and ticker they're limited to using it on titlefield, datefield, descriptionfield, or on the entire feed (as in fetcher, by not specifying the field).
But I don't think any of that is essential, except maybe the part about needing to specify 'atom' for an ATOM feed.
Edit: Also added are routines that more evenly distribute an uneven number of 'items to show' over the selected feeds, and ones to detect the base url of the feed and use it to complete the feed's items' links if it's determined they're relative links. Another change is that regexps added via addregexp() for specific fields are no longer deleted when used. So they are available to be reused with a subsequent init() or however one might choose.
I also just added an update to my updated gfeedfetcher-prot.js file that detects earlier versions of the ticker and scroller scripts and enables them to work with it (not miss the date):
gfeedfetcher-prot.js
Bookmarks