@sam_uk yes it does. I created a LAMP app and made it work, here is how:

https://forum.cloudron.io/topic/6368/enable-ldap-authentication-on-mattermost/4

+1 for Zammad

@girish The reason could be that it's quite stable already. We use their commercial SaaS version that uses that in the background but provides a nice UI and it works like charm. I guess they are more focused on supporting new devices and updating their OS, which happens regularly.
You can check their forums. I mean, those guys ported Docker to ARM in the first place.

I would love to see it too!

I was able to fix it by changing the following values in table focalboard_schema_migrations

• version 15 -> 11 (I figured that's the current version)
• dirty 1 -> 0

Sounds super useful indeed!
We could manage all our users centrally and create mailboxes for them too

@fbartels Thank you very much. I guess I'll try the official way. Thanks for pointing out the functionality of add-ons.

Thank you, guys.
Unfortunately, it didn't fix it for me, since plugins were already enabled.

Then I found this in my logs:

Jan 18 11:25:23 {"timestamp":"2022-01-18 10:25:23.926 Z","level":"error","msg":"Not activating plugin because diagnostics are disabled","caller":"app/plugin_api.go:928","plugin_id":"com.mattermost.nps"}

So I enabled diagnostics. However this was the result (not sure if its related to this update):

Jan 18 11:28:35 {"timestamp":"2022-01-18 10:28:35.229 Z","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:142","plugin_id":"focalboard","error":"error initializing the DB: Dirty database version 15. Fix and force version."}

@ashughes Perfect, that's correct.

Here is the answer:
https://github.com/mattermost/focalboard/issues/2119#issuecomment-1013751739

@robi It's not an issue with cloudron. So I guess as soon as there is a fix by Mattermost it will also land here.
The only action step from @nebulon and cloudron would be to add some tests for boards in future releases.

@nj it’s not free, but you can make it work with a workaround. I had to adjust an existing project, but it works now. I put together my changes here, hope it helps:

https://github.com/terehov/Mattermost-LDAP

I would love to see it too!

@sam_uk yes it does. I created a LAMP app and made it work, here is how:

https://forum.cloudron.io/topic/6368/enable-ldap-authentication-on-mattermost/4

@nj it’s not free, but you can make it work with a workaround. I had to adjust an existing project, but it works now. I put together my changes here, hope it helps:

https://github.com/terehov/Mattermost-LDAP

Sounds super useful indeed!
We could manage all our users centrally and create mailboxes for them too

@ashughes Perfect, that's correct.

Here is the answer:
https://github.com/mattermost/focalboard/issues/2119#issuecomment-1013751739

@robi It's not an issue with cloudron. So I guess as soon as there is a fix by Mattermost it will also land here.
The only action step from @nebulon and cloudron would be to add some tests for boards in future releases.

I was able to fix it by changing the following values in table focalboard_schema_migrations

• version 15 -> 11 (I figured that's the current version)
• dirty 1 -> 0

Thank you, guys.
Unfortunately, it didn't fix it for me, since plugins were already enabled.

Then I found this in my logs:

Jan 18 11:25:23 {"timestamp":"2022-01-18 10:25:23.926 Z","level":"error","msg":"Not activating plugin because diagnostics are disabled","caller":"app/plugin_api.go:928","plugin_id":"com.mattermost.nps"}

So I enabled diagnostics. However this was the result (not sure if its related to this update):

Jan 18 11:28:35 {"timestamp":"2022-01-18 10:28:35.229 Z","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:142","plugin_id":"focalboard","error":"error initializing the DB: Dirty database version 15. Fix and force version."}

Hey there,

does anybody else experience the same?
We were using Mattermost Boards (introduced in V6) and they disappeared after the last update to 6.3.0.

I can still find the setting and tried disabling and enabling (hoping that would set a flag in DB). Unfortunately, it did not help.

I guess it would make sense to add boards to the tests too.

Best

Eugene

I'll be in Berlin next week (Mon-Thu). But I guess it's too short of a notice

@girish The reason could be that it's quite stable already. We use their commercial SaaS version that uses that in the background but provides a nice UI and it works like charm. I guess they are more focused on supporting new devices and updating their OS, which happens regularly.
You can check their forums. I mean, those guys ported Docker to ARM in the first place.