eiland
83
…and feeds weren’t updating, because the default PHP_EXECUTABLE was set to “/usr/bin/php” in classes/config.php
Changed it with putenv('TTRSS_PHP_EXECUTABLE=/usr/bin/php74'); in my legacy config.php
fox
84
i’m not sure why you decided to keep us all informed in trials and tribulations of your unsupported tt-rss install but it’s not nearly as interesting or useful as you might think.
“i’ve changed X to Y” is only useful to others if you describe the context and reasons for it, otherwise you’re just encouraging people to change random things around without any understanding, confusing everyone who might follow your hollow non-advice further.
in short, post this shit to your personal blog from now on.
j_d
85
Thanks a lot for all this information and tips in this thread. I did the update to the new config unintentionally and had some problems. I know reading helps, but if someone runs into the same problem, here is what I did and what you should avoid.
- I replaced
define() with putenv(), e.g. putenv('DB_HOST', 'myserver'); (This is wrong!)
- I adjusted the syntax, so
putenv('DB_HOST', 'myserver'); became putenv('DB_HOST=myserver'); (This is still wrong!)
- I added the
TTRSS_prefix: putenv('TTRSS_DB_HOST=myserver'); (This finally works)
If you do the update, please read the documentation at https://git.tt-rss.org/fox/tt-rss/wiki/GlobalConfig. It helps a lot!
Now that I have admitted my mistakes, another big thanks for the rebuild, my config is now significantly smaller.
Yeah, well, MY problem (last night) was a missing ’ at the end of one of the new env variables… Which wouldn’t have been so bad, except nothing happened. no error messages, nothing, same with update.php, run it, no output, nothing.
So, I tried the old tried and true “comment out all of my stuff and see what happens” routine, then add back lines until I found the broken one.
syntax highlighting would have helped me there, but didn’t have it on that system. Anyway, it’s all working now.
ekin
87
I just updated tt-rss and had to update config.php as discussed in this thread. There was a clash of the option SELF_USER_AGENT in config.php with the definition in functions.php reported in the event log. I commented out the line in functions.php to make sure the definition in config.php is used. I am modifying SELF_USER_AGENT because otherwise some RSS servers that I use refuse connections from tt-rss. At least that’s how it was last time I checked (some months ago). Is the SELF_USER_AGENT option gone for good, or is there a chance that it can be reintroduced?
You can do this with a plugin by hooking HOOK_FETCH_FEED and calling UrlHelper::fetch() with a custom user agent, then return the results. This is actually a better approach as you can configure it to be different for only specific feeds.
fox
89
