Since the update from 19.0.5 to 20.0.4 the files_retention app is no longer supported by nextcloud.
Doing a app:update files_retention delivers an incompatibility hint.
Looking in the app Store in nextcloud, there is a red hint that it could be enabled as experimental app.
So, some users argue with that and wrote an issue at github
that there is no update for a longer period since 20.x is on the market nor a hint when the app will be compatible or if nextcloud gmbh will implement this feature into the core.
Would be very pleased if one of the developers can lift the curtain and don’t let us guess any longer
Definitely frustrating for those relying on it, but the app is reported to work fine once re-enabled. As a volunteer effort, you cannot expect any further development on this… hopefully it will be updated.
What i am missing is, that the known nextcloud app compat check before the upgrade has not given any signal that one of the apps can not be updated.
That why i did not force any update by switching from stable to beta!!
So in this case this didn’t work for the files_retention app - and it is not clear why?
One one hand it may be not possible to expect development on this side but here we have the info in the store that the developer (group) behind this app is:
Herausgeber
Nextcloud GmbH
And what is more important, developing “Flow” does not make sense without the apps behind that delivers action by tagging files
How did you re-enable it? Using the terminal - what i use normally does not offer any bypass the warning of the occ comand.
So where is the version between 1.8.2 and 1.10.0 that might be compatible with Server 20.x ?
But the hint to version 21.x leads into hope, that retention is actively maintained
With this version i set the version number to the following to get it working
…/…/nextcloud/apps/files_retention/appinfo/info.xml
{"reqId":"XGQi2FoBfSH7s4SXxa6R","level":3,"time":"2020-12-23T16:10:02+01:00","remoteAddr":"","user":"--","app":"core","method":"","url":"--","message":{"Exception":"Error","Message":"Call to a member function getUID() on null","Code":0,"Trace":[{"file":"/var/www/nextcloud/apps/files_retention/lib/BackgroundJob/RetentionJob.php","line":151,"function":"notifyNode","class":"OCA\\Files_Retention\\BackgroundJob\\RetentionJob","type":"->"},{"file":"/var/www/nextcloud/lib/private/BackgroundJob/Job.php","line":52,"function":"run","class":"OCA\\Files_Retention\\BackgroundJob\\RetentionJob","type":"->"},{"file":"/var/www/nextcloud/lib/private/BackgroundJob/TimedJob.php","line":59,"function":"execute","class":"OC\\BackgroundJob\\Job","type":"->"},{"file":"/var/www/nextcloud/cron.php","line":127,"function":"execute","class":"OC\\BackgroundJob\\TimedJob","type":"->"}],"File":"/var/www/nextcloud/apps/files_retention/lib/BackgroundJob/RetentionJob.php","Line":236,"CustomMessage":"Error while running background job (class: OCA\\Files_Retention\\BackgroundJob\\RetentionJob, arguments: Array\n(\n [tag] => 32\n)\n)"},"userAgent":"--","version":"20.0.4.0","id":"5fe438b589f3b"}
And the tagged files for deleting by next background job are still on the server.