Lastpass arbitrarily breaks tt-rss forms preventing various stuff like saving settings from functioning properly.
I’m experiencing random failures / UI glitches (error codes 6 & 7) / visibly broken HTML
Almost every time those are caused by malfunctioning and/or badly written browser extensions. Always try opening tt-rss without browser
extensions running (i.e. separate Firefox profile, Chrome incognito mode, etc). This way you will be able to figure out which extension
One of the extensions that causes such problems is Lastpass.
What should I use - MySQL or PostgreSQL?
PostgreSQL should give you much better performance, especially if you tune it a bit.
I need a URL I can call to subscribe to feed to integrate with some third party browser extension/application.
I have used the update daemon before, but switched away from it. However, the UI keeps nagging me about the daemon not running or not updating feeds or whatever.
Find and delete daemon lock file in LOCK_DIRECTORY.
Usually, it’s lock/update_daemon.lock. You can also remove
I have questions about article purging / I don’t think purging works.
In short, you may and will see articles with date older than the cutoff
for purging. Here’s why:
Starred articles are not purged.
Purging is done based on article import date internal to tt-rss which
could be different from the date specified in the original feed (e.g.
article has date 01-01-1970, but it was imported today).
When tt-rss sees articles still exist in the feed it bumps the import
date because otherwise the articles will get purged and reimported
periodically causing annoyingly reappearing duplicates. This is mostly
relevant for rarely updated feeds.
Purging is performed when the feed is updated hence disabled updates
= no purging.
Please see these forum threads for more information:
I have HTTP authentication enabled and get “Your access level is insufficient to run this script” error on login
The problem is that if you have auth_remote enabled in config.php
tt-rss tries to automatically log you in as the user specified by the
server using HTTP authentication, which may not have administrative
privileges. You will need to either temporarily disable auth_remote
(replace it with auth_internal in config.php), temporarily disable HTTP
authentication, or give yourself administrative permissions using the