Drupal Template: 
UQ Base Template
UQ News RSS feeds
Drupal Template: 
UQ Base Template

There are two sets of feeds:

  1. LEGACY to simulate what the old UQ News site produced and for the benefit of some really old parsing scripts out there that haven't yet been updated.
  2. VALID feed that should be used from now on.

http://uqnews.drupal.uq.edu.au/* is a development URL until news.uq.edu.au has been provisioned and to get around some server to server communication issues. Please use the uqnews.drupal urls noted below as they’re not going away and we can simply change to news.uq* in the future.

Legacy XML feed from UQ News (utf-8)


	<DATE>Feb 10 2014</DATE>
	<HEADLINE>'Affordable housing' for reptiles</HEADLINE>
	<ABSTRACT>University of Queensland researchers have found that naturally regrowing woodlands in the subtropics can help to reduce declines in Australia's reptiles.</ABSTRACT>

Legacy RSS feed from UQ News (utf-8)


	<title>Norwegian rocket range confirms motor problems</title>
	<description><![CDATA[The Andøya Rocket Range has released a statement confirming that The University of Queensland&#39;s SCRAMSPACE project was not responsible for last week&#39;s launch failure in Norway]]></description>
	<author>UQ News</author>
	<pubDate>Mon, 23 Sep 2013 14:45:00 +1000</pubDate>

VALID RSS Feed from UQ News (UTF-8)


	<title>UQ team challenges the limits of famous quantum principle</title>
	<description>A team of physicists is challenging the very limits of Heisenberg’s famous uncertainty principle by measuring quantum particles with unprecedented accuracy.</description>
	<author>communications@uq.edu.au (UQ Communications)</author>
	<pubDate>Wed, 05 Feb 2014 08:45:00 +1000</pubDate>

Character encoding

The UQ CMS template uses iso-8859-1 characters whereas Drupal uses utf-8 when storing.  So when we output html on UQ CMS templates the news item heading and description most likely need to be converted in your php scripts. e.g.

print htmlentities($this->title, ENT_COMPAT, 'utf-8');
print htmlentities($this->description, ENT_COMPAT, 'utf-8');

OR change the header to use utf-8 if you’ve got control of the template.

The valid feeds use a charset of utf-8:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />