Postby HunterZ » 04 Apr 2013, 18:38
Two issues have cropped up with new versions of tt-rss:
First: installing this to a direct subdirectory of tt-rss causes it to get wiped out by the auto updater plugin. I know this is relevant because some of us were installing to the mobile/ subdirectory, and the default config of ttrss-mobile uses a ttrss-mobile subdirectory as an example.
I'll be reinstalling to a sibling directory of my tt-rss install instead of a subdirectory. I suppose installing to plugins may also work, but it's not really a plugin.
Second: since the mobile browser detection code of tt-rss no longer redirects to the mobile/ subdirectory (which no longer exists anyways), tt-rss' mobile browser detection is now only useful for those who cling to the old mobile web interface (which is now implemented via an unsupported plugin), and ttrss-mobile users must now browse explicitly to the ttrss-mobile path.
To actually make the built-in tt-rss mobile browser detection routines useful for people who are using non-deprecated mobile web interfaces, it might be helpful if tt-rss could provide a configuration option to specify where mobile browsers should be redirected (e.g. the mobile plugin, or some path to ttrss-mobile, etc.).