Installation_and_FAQ

Featured
de , en, fr

Updated Feb 20, 2011 by zzuzzlwuzzl@gmail.com

Installation

Upload all files in the ZIP archive
make the directories config, data/cache, data/favicons and data/thumbnails writeable (use your FTP client and change the rights of the directories)
open rsslounge in your browser and follow install instructions

OPML Import

The most RSS reader offers an OPML export. You can export all your feeds in a single XML File. This file can be imported in rsslounge. Open the menue on the header (right) and chose "OPML Import". rsslounge will import all feeds and reloads the page. Afterwards rsslounge will update all feeds. This first update needs a little bit more time than the further updates.

Important: The feed icons will be set after the first update of the feeds!

Update via Cronjob

For updating rsslounge feeds via cronjob point your cronjob to open

http://<rsslounge url>/update/silent

via wget or curl.

After installation all looks weird

Mac OS and Linux users must ensure that all files will be uploaded. Also the file .htaccess which is hidden by default on Unix based Systems.

Password protected rss feeds

You can also subscribe to password protected rss feeds. Just enter the username and passwort before the url:

http://user:password@example.com/rss

The page is empty or following php error occurs

PHP Parse error: syntax error, unexpected T_CLASS in /home/bongzone/public_html/rsshat.com/application/models/settings.php on line 1

Choose the binary upload in your FTP Client software.

There are problems on the feed update process, where can I find more debug information?

rsslounge offers an logging mechanism which can be activated via the configuration file

config/config.ini

Change there the option

logger.level = ALERT

logger.level = DEBUG

Then you can find detailed information about an cronjob or ajax update in the log file:

data/logs/default

I only get an ServerError 500

This error occurs especially on Apache 1. Insert in the

.htaccess

following line bellow "RewriteEngine on"

    RewriteEngine on
    RewriteBase /path/to/rsslounge/

I don't see icons

rsslounge tries to collect all favicons of your feeds in one single image file. This reduce the http requests on loading rsslounge dramaticaly. But the conversion of some ico files failed. You can disable the favicon collection by setting following parameter in the config/config.ini file:

cache.iconcaching = 0

Then rsslounge will include the favicons directly (without generating one single image file).

Installation on lighttpd

For user of lighttpd you have to set the rewrite rules in the lighttpd configuration:

    url.rewrite-once = (
      "^/rsslounge/favicon.ico$" => "/rsslounge/public/favicon.ico",          
      "^/rsslounge/plugins/([^/]+)/(.*)$" => "/rsslounge/plugins/$1/public/$2",
      "^/rsslounge/favicons/(.*)$" => "/rsslounge/data/favicons/$1",
      "^/rsslounge/thumbnails/(.*)$" => "/rsslounge/data/thumbnails/$1",
      "^/rsslounge/javascript/(.*)$" => "/rsslounge/public/javascript/$1",    
      "^/rsslounge/stylesheets/(.*)$" => "/rsslounge/public/stylesheets/$1",  
      "^/rsslounge/public/" => "$0",                                   
      "^/rsslounge/(.*)" => "/rsslounge/index.php?mod_rewrite=1&$1"
    )

Modify the urls according to your directory structure.

Installation on nginx

For user of nginx you have to set the rewrite rules in the configuration:

    server {
        listen              80;
        server_name         www.server.com;

        root /var/www;
        index           index.php index.html index.htm;
        location ~ .php$ {
            root            /var/www;
            fastcgi_pass    unix:/tmp/php-fpm; # oder einfach 127.0.0.1:9000 je nach Einstellung
            include         fastcgi_params;
            fastcgi_param   QUERY_STRING   mod_rewrite=1&$query_string; # perfomanter als ein rewrite
            fastcgi_index   index.php;
            fastcgi_param   SCRIPT_FILENAME   $document_root$fastcgi_script_name;
        }
        # rewrites von .htaccess:
        rewrite ^/favicon.ico$ /public/favicon.ico;
        rewrite ^/plugins/([^/]+)/(.*)$ /plugins/$1/public/$2;
        rewrite ^/favicons/(.*)$ /data/favicons/$1;
        rewrite ^/thumbnails/(.*)$ /data/thumbnails/$1;
        rewrite ^/javascript/(.*)$ /public/javascript/$1;
        rewrite ^/stylesheets/(.*)$ /public/stylesheets/$1;

        location ~ \.htaccess {
            deny all;
        }

        if (!-e $request_filename) {
            rewrite ^.*$ /index.php last;
        }

    }

Comment by marc.brodt@gmail.com, Sep 2, 2009

Hallo.

Auf den letzten Punkt (für MacOS und den unsichtbaren Dateien) sollte man in der Readme besser hinweisen. Mich hat das etwas Zeit gekostet.

Comment by marc.brodt@gmail.com, Sep 2, 2009

Jetzt bekomme ich folgende Fehlermeldung ganz oben (über dem schwarzen Balken): {{{Notice: Use of undefined constant APPLICATION_PATH - assumed 'APPLICATION_PATH' in /srv/www/vhosts/meine-domain.de/httpdocs/rss-lounge/index.php on line 4 Notice: Use of undefined constant APPLICATION_PATH - assumed 'APPLICATION_PATH' in /srv/www/vhosts/meine-domain.de/httpdocs/rss-lounge/index.php on line 5

Comment by marc.brodt@gmail.com, Sep 2, 2009

Mist. Da fehlt die Hälfte meines Textes... Frust. Erstmal habe ich genug. Die Tage vielleicht wieder.

Comment by project member zzuzzlwuzzl@gmail.com, Sep 6, 2009

Hi Marc,

wenn das PHP Error Reporting auf STRICT gesetzt ist, kommt diese Fehlermeldung. Die aktuelle Version behebt das Problem. Einfach patchen. Wenn du dann noch Probleme hast, kontaktiere mich bitte einfach nochmal.

Viele Grüße

Tobi

Comment by henrycon...@gmail.com, Dec 30, 2009

My apache 1.3.33 server gives me an 500 Internal Server Error wich i think its caused by the .htaccess. I can access if i point the browser directly to index.php but the reference to all public assets (javascript and stylesheets) is lost, then I can't do anything in the ajax interface. I want to test rsslounge in my domain, so any help would be appreciated! Thanks!

Comment by project member zzuzzlwuzzl@gmail.com, Dec 30, 2009

What happens if you delete all lines before # mod_rewrite rules <IfModule? mod_rewrite.c>

RewriteEngine? on

... in your .htaccess?

Is the mod_rewrite Module available?

Comment by henrycon...@gmail.com, Dec 30, 2009

Yes, the mod_rewrite is enabled. The 500 error continues to appear after removing the indicated lines. I tried to identify the rule behind the error and the only way to avoid the error is removing the two rules for the front controller, but instead of the 500 error i got a 404 one. Thanks for your answer!

Comment by project member zzuzzlwuzzl@gmail.com, Dec 31, 2009

Hm, it seems as if mod rewrite of apache version 1 differs from apache version 2. I will test this the next days and install apache 1 on my test system.

Comment by Datenban...@gmail.com, Jan 18, 2010

Gibt es schon was neues für den alten Apache?

Comment by project member zzuzzlwuzzl@gmail.com, Jan 21, 2010

For all with an problem with the old Apache 1: add the line

RewriteBase? /

(e.g. RewriteBase? /path/to/rsslounge/)