Sitebeam 4.1.4

This version was publicly released on 26th April 2011.

Availability

These changes were made following the recent Amazon downtime which affected many of our customers.

  • Sitebeam now explains if it is unable to connect to the required Amazon cloud service, and explains the current problem. Previously certain types of database problem could cause Sitebeam to stop responding entirely.
  • Sitebeam can now display a custom message to all users prior to their login, to explain any service problems that may be occurring.

Broken links test

  • This now shows the number of pages with a broken link on them.

Readability test

  • Purely legal pages, such as Terms & Conditions, are now given a very low weighting for this test. Generally these pages would tend to have low importance because of their position in a page (in the footer), but this is now directly enforced.
  • The automated extract of ‘hard to read’ text now excludes pages which appear to be purely legal in nature.
  • The detection of legal pages is done by observing the title of the page for specific keywords, such as “Terms & conditions”. It is not perfect, but will reduce instances of common legal pages appearing the example extracts.
  • The hard to read extract is now the hardest fairly-long sentence to read found on any page. Previously it was the hardest found on the hardest page, which wasn’t always the best example.

Fixes

  • Fixed serious issue where running a report could potentially corrupt an existing one (under certain conditions with Test Servers being replaced and a site being re-tested afterwards).
  • Made the Broken links test more understanding of slow sites. The test now allows a longer timeout before assuming a link is broken.
  • Prevented an upgrade from getting run more than once at the same time. Once an upgrade is started, STN can’t request another (avoiding potential race conditions and corrupted index files).
  • Fixed possibility of some installations crashing due to a heavily loaded server.

Other

  • Various metrics now use ‘smart rounding’. Generally, less decimal places are shown where those decimal places don’t add meaningful value to the information being shown, but more decimal places are added where they clarify the data being shown. E.g. “0.001” would retain the necessary decimal places, but “2,300.01” would round to “2,300”. This affects many tests.

Was this article helpful? Contact our support team if you have a question.