Awasu 2.2.5 (beta)

This is a beta release [?]. Some features may not be complete and the software may be unstable. Install at your own risk! You may need to do some basic computer maintenance tasks to get this release to run.

 

Installation

First, backup your existing Awasu installation! [?]

Then choose how you want to install this release:

Upgrade from Awasu 2.2.5.alpha1 or alpha2 or alpha3
Upgrade from Awasu 2.2.4
Upgrade from Awasu 2.2 or 2.2.1 or 2.2.2 or 2.2.3
Upgrade from a version of Awasu prior to 2.2
Create a clean installation
Reinstall Awasu 2.2.5

 

Safe feed content

Awasu now checks your feed content and removes any potentially malicious HTML content, before showing it to you.

Awasu has long had a "plain text" mode, where it would strip all HTML tags from feed content before showing it to you. However, while it rendered your feed content safe, it was a bit heavy-handed in that it stripped everything, including tags that are perfectly safe e.g. <b> or <p>.

This release introduces a much smarter and selective process of removing dangerous HTML from your feeds. Everything is configured to work out of the box, so you don't need to do anything for this feature to be active, nor should you see any changes in how Awasu works. The only difference you are likely to see is in feeds that embed things like YouTube videos using the <object> tag. Because this tag can be used to cause mischief, it is automatically removed and feed items will no longer show the embedded content.

By default, Awasu removes only those HTML tags that can be used to cause problems on your computer but it can be fine-tuned to either always remove or always allow specific HTML tags and attributes.

This can be done either from the Advanced tab of the Program Options dialog (right), which will apply to all your channels, or for individual channels from the Advanced tab of the channel's Properties dialog (left).

Enhanced password security

Awasu now stores your passwords in the config files in a more secure manner. This means that you will need to re-enter your license key and any passwords that you may be using e.g. for feeds that need authentication, FTP server passwords for sync files, passwords for Bloglines/Google Reader/Gregarious if you are synchronizing with them, mail server passwords if you are using the SendEmail channel hook, etc.

 

Where your data files are stored

This release changes where your data files are stored, bringing Awasu into line with Microsoft-recommended practices. If you are already using Awasu, it will continue to use your existing data files (so you don't need to do anything and won't be affected by this change) but any new users will have their data files placed in the new locations.

This change has important implications if you have more than one copy of Awasu installed on your computer so please check these notes if this applies to you.

 

Other new features

  • Added the ability to manually check for newer versions of Awasu. This can be done via the Check for updates item in the Help menu.

  • Holding down the Control key when choosing the Open in Awasu option from IE's context menu will now open the link in a background tab.

  • Workpad reports can now access channel and item metadata (via the usual {%CHANNEL-METADATA%} and {%ITEM-METADATA%} parameters).

 

Minor changes and bug fixes

  • Awasu now always keeps at least the last feed for a channel in the archive database, no matter how old it is.
    This means that channels will always show some content, regardless of how long it has been since new content was published. This also fixes the problem where dormant channels would suddenly start showing their feed URL in My Channels instead of their normal name.
  • Made the enclosure icon in the channel summary pages clickable.
  • Tweaked the Rusty channel template to make it more readable if the channel has a very long description.
  • Awasu no longer shows self and edit links in the channel summaries for Atom feeds.
  • Simplified the report shown after optimizing the archive database if errors were found.
  • The Meta-Channel report template now uses Atom 1.0.
    This change required the addition of a new ITEM-METADATA-TYPE parameter that returns the type (HTML or plain-text) of a piece of content.
  • Awasu now checks that the version of your data files matches the version of Awasu being run.
  • admin.exe and upgrade.exe now must be run from an Administrator account.
  • Updated the BlackBox crash handler to recognize Windows Vista. It also includes additional information about Awasu-related processes.
  • Each user now downloads their own copy of the Channel Packs instead of updating a single shared copy.
  • ResetUi.exe and the Syndic8 application plugin no longer create their log files unless they are needed.
  • admin.exe no longer opens its log file in the Awasu installation directory.
  • The BUILD.INFO file is no longer written to the Awasu installation directory.
  • CDATA sections inside Atom XHTML or RSS xhtml:body content nodes are now parsed correctly.
  • Added the intriguingly-named Mark Of The Web to the application plugin template files.
  • Fixed a problem that was stopping Awasu from running on Windows NT.
  • Fixed a bug in relative link translation of Atom 1.0 XHTML content.
  • Fixed a bug in the way SGML entities were being parsed.
  • Fixed relative link translation when reading a feed from a file.
  • Disabled an IE performance workaround that was stopping Enhanced IE security from working the very first time Awasu is run.
  • The enclosing <xhtml:body> tags are no longer retained when parsing RSS feed item content.
  • Fixed a minor problem in the way the .CHANNEL filename is generated for application plugin channels.
  • Fixed a bug introduced in 2.2.3 to the application plugin framework that was stopping the Syndic8 plugin from working.
  • Fixed a redraw problem in the Sidebar.
  • Fixed a problem with switching between passive and active FTP.
    Many thanks to Torsten Jensen for his help with this one.
  • Fixed some possible crashes during startup (especially on multi-CPU machines).
  • Fixed a minor bug with the progress bar when generating certain reports that was causing it to show the process as being over 100% complete.
  • Fixed some possible crashes in the database handling code.
  • Optimized the way database connections are re-used.