-
Hi,
I get the error,
Can not enable extension TinyTinyRSS API: server cannot write in /app/code/p/api
while trying to enable "TinyTinyRSS API" extension on Fress RSS.
I assume this is happening since "p/api" is readonly and FreshRSS is trying create an entry in that directory.
Is it be possible to have the "TinyTinyRSS API" extension enabled by default? Or is it a feasible to make "p/api" persistent and accessible to "www-data"?
-
Found it - https://github.com/FreshRSS/Extensions/blob/master/xExtension-TTRSS_API/extension.php#L9 . The extension is trying to write to system directory '/p/api' at runtime. Not sure how to keep it updated given there are other files in that place which come from the main project. Many PHP projects have this habit of writing all over the place for some reason If we want to support this specific extension, we have to make that directory writable.
@pratik how important is this extension or where you just trying things out?
-
@pratik how important is this extension or where you just trying things out?
TLDR:- Need it to access it from mobile.
I use Palabre Android client to read RSS on mobile, since the UI is pretty and they have a working plugin for ttrss. Have been using Tiny Tiny RSS server for a while and was never happy with it. UI is messed up when using Firefox Tracking blocking. Even on Chrome it is not very legible.
On FressRSS, everything is great on browser. Love the UI and the speed is awesome. But, all the recommended apps for Android have features missing that I really need - mostly lack of a decent widget.
So, FressRSS with support for Tiny Tiny RSS API is the best possible combination for me. -
@girish said in Fresh RSS - Extension Error - "TinyTinyRSS API":
The extension is trying to write to system directory '/p/api' at runtime.
I think this is to be consistent. All their API code is in this directory. So if ttrss plugin comes preloaded, may be it won't want write access to this directory anymore.
-
@nebulon This plugin requires a file to be placed as part of the core files. We have to rework packaging of the /p/api directory to make it work. Not sure if it's worth it. Maybe we should provide a constructive error report to the upstream project on how they can help us by making the plugin installation only write to modifiable directories.