Fresh install, stuck at “Loading, please wait: 80%” with the following error in the console. This happens in both Firefox and Chrome, extensions are disabled.
ReferenceError: Effect is not defined
at Object.hideReadCat (http://servername/tt-rss/js/FeedTree.js?1520499839636:423:8)
at http://servername/tt-rss/js/FeedTree.js?1520499839636:440:11
at Array.forEach ()
at Array.each (http://servername/tt-rss/lib/prototype.js?1517559441:861:12)
at Object.hideRead (http://servername/tt-rss/js/FeedTree.js?1520499839636:439:10)
at Object. (http://servername/tt-rss/js/FeedTree.js?1520499839636:222:10)
at Object. (http://servername/tt-rss/lib/dojo/dojo.js?1517559441:8:32980)
at Object._268 [as _expandNode] (http://servername/tt-rss/lib/dojo/dojo.js?1517559441:8:59340)
at Object.selectFeed (http://servername/tt-rss/js/FeedTree.js?1520499839636:357:23)
at selectFeed (http://servername/tt-rss/index.php:336:86)
tt-rss version (including git commit id):
v17.12 (2c51fac)
Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
CentOS Linux release 7.4.1708 (Core), php-5.4.16-43.el7_4, postgresql-9.2.23-3.el7_4
The update feed script is run by systemd and I could briefly see my feed names after importing OPML from Feedly, but then I hit this.
i don’t know why scriptaculous (the library that provides Effect class) is not loaded on your system or tt-rss starts running before dependencies are loaded, neither of those should happen.
check for errors related to scriptaculous.js in browser error console and httpd log files. could be a permission issue or something like that.
yeah, going by the log the file is being sourced successfully.
if you do typeof Effect in browser console does it also return undefined? idk what could be the cause here.
do you have anything unusual on your server or client machines? an over-eager AV, maybe content-security-policy headers on the server? also if you’re not running over SSL you could be MITMed one way or another which breaks tt-rss.
personally i would try booting a linux distro and connecting directly to the server through vpn (or at least ssl) to rule out a potential MITM.