@humptydumpty said in Plugin for automatic delete:

@robi You beat me to it.

Screenshot 2022-11-11 172507.png

Hi, plugin installation works, but the code

"ep_delete_after_delay": { "delay": 86400, // one day, in seconds "loop": true, "loopDelay": 3600, // one hour, in seconds "deleteAtStart": true, "text": "The content of this pad has been deleted since it was older than the configured delay." },

don't work after putting in settings.json and restart app.
I think a text should be displayed at a new pad, or? In my case there is no text...

@jdaviescoates said in Plugin folders need ownership change after installation:

I'm very bemused by this.

The first time I installed a plugin (the Akismet plugin) I didn't have to change permissions on the /app/code/plugins/discourse-akismet/ folder from root to cloudron

But every other plugin I've installed after that has required me to open the File Manager and change the ownership from root to cloudron.

Why?

Because the first time, when I installed the Akismet plugin, I restarted the app before looking at the File Manager, and seemingly restarting the app fixes the permissions.

I deleted the chat-integration plugin and reinstalled the checklist plugin and now I am able to see /admin/plugins again.

Seems the proposed method is indeed to just delete the directory:

@girish said in How to deinstall plugins:

I think just deleting the plugin directory inside /app/data/plugins and restarting the app will do it.

@staff that info should be added to the docs 🙂

But, also, does removing the directory actually make Cloudron then edit the app.yml file to remove references to the plugin?

Because that is what is supposed to happen as per:

https://meta.discourse.org/t/how-to-completely-uninstall-remove-a-plugin/55034/18?u=jdaviescoates

Working on this in parallel and just wanted to dump the status so far.

The reason discourse does not start is the instructions are "git clone" and that checks out the latest plugin code which is sometimes incompatible with the installed discourse version.

https://meta.discourse.org/t/pinning-plugin-and-theme-versions-for-older-discourse-installs/156971 says "You can now include a .discourse-compatibility file at the root of a plugin or theme repository, that designates what to checkout when installing on older Discourse versions."

Very nice, so we have to figure how to checkout the correct version. And Indeed that calendar plugin has moved on to min compat version of 2.9beta of discourse, we are only on 2.8 still.

https://meta.discourse.org/t/migration-failed-on-update-calendar-plugin-to-last-commit/239437 and https://meta.discourse.org/t/cloudron-missing-plugin-pull-compatible-all/244002 suggests there is some plugin:pull_compatible_all rake task. So, we have to figure how to use this in Cloudron.

@girish Thanks for the help.

The plugin does work fine but does not meet my expectations. I thought that, after installing the plugin, somewhere nodebb would have a page dedicated to events in a calendar. What happens is the events appear in a post OK, but there is not dedicated page where all the events happening appear. I mean that I still cannot see this:

alt text

Also, though the notification was set to happen, no notification occured. This might perhaps be because the default setting for checking new events is a long period of time.

I thought there might be a calendar icon or something to click here:

brave_GGN5dfEARQ.jpg

@LoudLemur Right, it will be like so:

bundle exec rake plugin:install_gems['discourse-calendar']

This issue has not been solved.

The issue appears to be Cloudron specific and so clearly @Staff need to do something to make Discourse plugins install/ work as expected.

If I can't install the discourse-calendar on my Cloudron Discourse app then the Cloudron Discourse app is completely useless to me 😞

See e.g. https://meta.discourse.org/t/migration-failed-on-update-calendar-plugin-to-last-commit/239437/6

And https://forum.cloudron.io/post/55230

@girish GREAT! Adding the path manually did the job!

@nebulon said in Does anybody use the plugin LDAP write in Nextcloud ?:

That is correct, our ldap server does not allow any modification or writes to the user directory.

that is smart, because it is so easy to mess with LDAP

@jdaviescoates it should be array_push($config['plugins'], 'myplugin');