The News app is an RSS/Atom feed aggregator. It offers a RESTful API for app developers. The source code is available on GitHub

For further developer and user documentation please visit the wiki

• Bernhard Posselt
• Alessandro Cosentino
• Jan-Christoph Borchardt (Design)

are listed on the ownCloud apps overview

• ownCloud >= 8.2
• libxml >= 2.7.8 (2.9 recommended)
• php-curl
• iconv
• SimpleXML
• PHP >= 5.5

Supported means that the distribution's default repository packages will work in conjunction with the News app and you won't have to add any 3rdparty repositories.

The following distros are supported:

• Ubuntu 14.04
• Debian 8 (Jessie)
• Arch Linux

• Newest Firefox (Desktop, Android, Firefox OS)
• Newest Chrome/Chromium (Desktop, Android)

• PostgreSQL (recommended)
• MySql
• SQLite (discouraged)

Please read the appropriate section in the contributing notices

Before you install the app do the following:

• Check that your owncloud/data/ directory is owned by your webserver user and that it is write/readable
• Check that your installation fullfills the requirements listed in the README section
• Set up ownCloud Background Jobs to enable feed updates. A recommended timespan for feed updates is 15-30 Minutes.
• If you are updating from a previous version read the Update Notices

Then proceed to install the app either from an archive (zip/tar.gz) or clone it from the repository using git

• Go to the ownCloud News GitHub releases page and download the latest release/archive to your server
• On your server, check if there is a folder called owncloud/apps/news. If there is one, delete it.
• Extract the downloaded archive to the owncloud/apps/ folder.
• Remove the version from the extracted folder (e.g. rename owncloud/apps/news-4.0.3/ to owncloud/apps/news/
• Activate the News app in the apps menu

• The master branch will always be stable in conjunction with the latest master branch from ownCloud

• In your terminal go into the owncloud/apps/ directory and then run the following command:

    git clone https://github.com/owncloud/news.git
  

• If you are using a stable ownCloud release, stay with the latest git tag release which is running on your version. To get an overview over all existing tags run:

    git tag
  

You can switch to a release which will be supported on your installation by running:

  git checkout tags/TAG

For instance to use the 5.2.8 release, run:

  git checkout tags/5.2.8

• Activate the News app in the apps menu

To update the News app use change into the owncloud/apps/news/ directory using your terminal and then run:

git pull --rebase origin master

• Use MySQL or PostgreSQL for better database performance
• Use the updater script to thread and speed up the update

To receive notifications when a new News app version was released, simply add the following Atom feed in your currently installed News app:

https://github.com/owncloud/news/releases.atom

If you are serving your ownCloud over HTTPS your browser will very likely warn you with a yellow warnings sign about your connection not being secure.

Chrome will show no green HTTPS lock sign, Firefox will show you the following image

Note that this warning is not red and won't block the page like the following images which signal a serious issue:

This warning is caused by mixed passive content and means that your page loads passive resources from non HTTPS resources, such as:

• Images
• Video/Audio

This allows a possible attacker to perform a MITM (man-in-the-middle) attack by serving you different images or audio/video.

The News app fully prevents mixed active content by only allowing HTTPS iframes from known locations; other possible mixed active content elements such as <script> are stripped from the feed. Because images and audio/video are an integral part of a feed, we can not simply strip them.

Since an attacker can not execute code in contrast to mixed active content, but only replace images/audio/video in your feed reader, this is not considered to be a security issue. If, for whatever reason (e.g. feed which would allow fishing), this is a security problem for you, contact the specific feed provider and ask him to serve his feed content over HTTPS.

For the same reason that we can't fix non HTTPS websites: It does not fix the underlying issue but only silences it. If you are using an image HTTPS proxy, an attacker can simply attack your image proxy since the proxy fetches insecure content. Even worse: if your image proxy serves these images from the same domain as your ownCloud installation you are vulnerable to XSS via SVG images. In addition people feel save when essentially they are not.

Since most people don't understand mixed content and don't have two domains and a standalone server for the image proxy, it is very likely they will choose to host it under the same domain.

Because we care about our users' security and don't want to hide security warnings, we won't fix (aka silence) this issue.

The only fix for this issue is that feed providers serve their content over HTTPS.

This error usually means that your database schema was not properly migrated which can either be due to timeouts or bugs in Doctrine/ownCloud core. To prevent future timeouts use

php -f owncloud/occ upgrade

instead of clicking the upgrade button on the web interface.

To fix this issue either manually add/remove the offending columns or trigger another database migration.

Databases are migrated when a newer version is found in appinfo/info.xml than in the database. To trigger a migration you can therefore simply increase that version number and refresh the web interface to run an update:

First, get the current version by executing the following Sql query:

SELECT configvalue FROM oc_appconfig WHERE appid = 'news' and configkey = 'installed_version';

This will output something like this:

7.1.1

Then edit the appinfo/info.xml and increase the number on the farthest right in the version field by 1, e.g.:

<?xml version="1.0"?>
<info>
    <!-- etc -->
    <version>7.1.2</version>
    <!-- etc -->
</info>

Now run the update in the web interface by reloading the page.

Finally set back the old version number in the database, so the next News app update will be handled propery, e.g.:

UPDATE oc_appconfig SET configvalue = '7.1.1' WHERE appid = 'news' and configkey = 'installed_version';

Instead of triggering an automatic migration, you can of course also add or remove the offending columns manually.

The exception name itself will give you a hint about what is wrong:

• BadFunctionCallException: Is usually thrown when there are more columns in the database than the code
• InvalidFieldNameException: Is usually thrown when there are more columns in the code than the database

To find out what you need to add or remove, check the current appinfo/database.xml and compare it to your tables in the database and add/remove the appropriate fields.

Some hints:

• type text is usually an Sql VARCHAR
• type clob is usually an Sql TEXT
• length for integer fields means bytes, so an integer with length 8 means its 64bit

Some websites block the News app because the mistake its user agent string for an attack (most notably https://www.joomla.org/announcements.feed\?type\=rss). You can test for this issue by changing the default user agent string in appinfo/application.php.

Search the section that defines the user agent:

$userAgent = 'ownCloud News/' . $appConfig->getConfig('version') .
             ' (+https://owncloud.org/; 1 subscriber;)';

and replace it with the following line:

$userAgent = 'test';

If this fixes the issue, contact the feed's administrators and ask them to fix their server setup.

Hint: Should you not be able to set up picoFeed or Miniflux, you can simply use the bundled picoFeed version to test the website, e.g.:

php -f vendor/fguillot/picofeed/picofeed feed https://www.joomla.org/announcements.feed\?type\=rss

This is very often caused by missing or old files, e.g. by failing to upload all of the News app' files or errors during installation. Before you report a bug, please recheck if all files from the archive are in place and accessible.

Delete the folder owncloud/apps/news/ and owncloud/data/news/, then connect to your database and run the following commands where oc_ is your table prefix (defaults to oc_)

DELETE FROM oc_appconfig WHERE appid = 'news';
DROP TABLE oc_news_items;
DROP TABLE oc_news_feeds;
DROP TABLE oc_news_folders;

Check the owncloud/data/owncloud.log for hints why it failed. After the issues are fixed, turn off the maintenance mode by editing your owncloud/config/config.php by setting the maintenance key to false:

"maintenance" => false,

• Check if the cronjob exists with crontab -u www-data -e (replace www-data with your httpd user)
• Check the file permissions of the cron.php file and if www-data (or whatever your httpd user is called like) can read and execute that script
• Check if the cronjob is ever executed by placing an error_log('updating') in the background job file. If the cronjob runs, there should be an updating log statement in your httpd log.
• If there is no updating statement in your logs check if your cronjob is executed by executing a different script
• If your cron works fine but owncloud's cronjobs are never executed, file a bug in core
• Try the updater script

If you want to add a feed that uses a self-signed certificate that is not signed by a trusted CA the request will fail with "SSL certficate is invalid". A common solution is to turn off the certificate verification which is wrong and makes your installation vulnerable to MITM attacks. Therefore turning off certificate verification is not supported.

If you have control over the feed in question, consider signing your certificate for free on one of the following providers:

• letsencrypt.com
• StartSSL
• WoSign

If you do not have control over the chosen feed, you should download the certificate from the feed's website and add it to your server's trusted certificates. The exact procedure however may vary depending on your distribution.

All configuration values are set inside owncloud/data/news/config/config.ini and can be edited in the admin panel.

The configuration is in INI format and looks like this:

autoPurgeMinimumInterval = 60
autoPurgeCount = 200
maxRedirects = 10
maxSize = 104857600
feedFetcherTimeout = 60
useCronUpdates = true
exploreUrl =

• autoPurgeMinimumInterval: Minimum amount of seconds after deleted feeds and folders are removed from the database. Values below 60 seconds are ignored
• autoPurgeCount: Defines the minimum amount of articles that can be unread per feed before they get deleted, a negative value will turn off deleting articles completely
• maxRedirects: How many redirects the updater should follow
• maxSize: Maximum feed size in bytes. If the RSS/Atom page is bigger than this value, the update will be aborted
• feedFetcherTimeout: Maximum number of seconds to wait for an RSS or Atom feed to load. If a feed takes longer than that number of seconds to update, the update will be aborted
• useCronUpdates: To use a custom update/cron script you need to disable the cronjob which is run by ownCloud by default by setting this to false
• exploreUrl: If given that url will be contacted for fetching content for the explore feed