Modules which are put into the predefined folder plugins.local are not available in the UI over at https://DOMAIN/prefs.php.
Also a restart does not solve the problem.
I tried multiple plugins and put them in a folder like described here
https://git.tt-rss.org/fox/tt-rss/wiki/Plugins and also here https://docs.cloudron.io/apps/tinytinyrss/ but they are not showing up.
what could be wrong? a wrong symlink or setting I need to activate? have not found anything in the docu, so I think it is a cloudron "issue"
Thx for the info.
I want to install Performance Audit. This module is a Marketplace Module. If I click/install it, it will be put under /plugins as you said.
If I move it to a newly created plugins.local, the system will not recognize. not in the marketplace section, that is can be used or in the plugins section.
maybe there is a matomo/cloudron folder mapping issue?
@thetomester13 hey sorry… I answered in the wrong thread… my fault!
but I tested it again…
I added multiple modules and tried multiple locations. Restarted the app, but one of them are showing inup in the preference settings over at
I added them in plugins and plugins.local but no success
I changed the folder name to "package nme or let it stay like it came from git…
@grienauer does your File Manager look something like this? (Note the directory hierarchy)
Be sure that the plug in actually works and can work on a regular instance to verify that it's the app itself. Besides that I'm not really sure what to say do your logs say anything fishy?
this is inside of tinyrss…
be aware, that the plugins.local was from me. but I tested both folders…
this is the default plugins folder
and here the .local one
please be aware, that I tested naming schemes also tho check if this is the issue…
in both folders and also after a restart, no new plugins are visible in the preferences.
@grienauer were you able to test this plugin on a local version of TTRSS? I know that's not always an option for non-technical people though. This is the plugin that is working for me in the
/app/data/pluginsdirectory - can you try that and see if it works? If it does, there might be something wrong with your plugins themselves.