I’m new to kopano and try to share calendars with everyone.
How do I add a permission? Do I need a keyword?
k = kopano.Server()
store = kopano.user('str').store
cal = store.calendar
# try to share the calendar with everyone. This is not working:
Hi @mhope ,
this seems to be an issue with recent versions of rocket.chat when viewed in outdated browsers.
I had this happen to me too, when trying to open it in an ancient version of opera, even without the kopano plugin (looked exactly like your screenshot).
You could still open channels using the search, but the list was broken.
The user @tasism tried to post the following reply, but for whatever reason the forum software does not let me approve his post. Therefore posting manually:
As I stumbled upon this thread trying to get to get the kopano-docker setup to work behind my reverse TLS proxy (haproxy, not nginx), I just wanted to share the required configuration changes that allowed this to happen for me:
First of all, the configuration variable has changed its name in later versions and is now SECURE_COOKIES (not INSECURE_COOKIES). I chose to put the following in the kopano_webapp.env file:
In addition, I commented out the FQDNCLEANED variable in the .env file:
PYTHON3 was definitely the problem. I was able to successfully build! Having a weird issue with it not taking PYTHON_PATH/PYTHON_EXEC_PATH variables to send the python packages to somewhere other than site-packages (I’m looking for dist-packages), but I have a rather embearassing hack in place to move them manually after install. Thanks for your assistance.
Yes, that was it.
I installed the nightly builds from today and ran into the same error you referenced. The workaround did not work. I simply installed an older nightly build of the grapi packages and it works for now.
Access token expiration is now 3540s.
You are the man :-)
Since you are located in Germany as myself perhaps we see each other at an event (if my company is willing to pay for me to visit :-)) and I’ll buy you a beer.
Thanks, @jengelh, that’s what I gathered from reading the GetSetting() code itself. In that case, why are there so many non-NULL-checks in LDAPUserPlugin.cpp for configuration variables? I’d gather they make no sense, because all options have defaults (the empty string); that’s where my initial confusion came from.