@joseph said in issue with update to 1.6.6?:

@uwcrbc said in issue with update to 1.6.6?:

I am also wondering why the logs are showing a time that is neither the one set in the Cloudron server settings nor the one from the server.

Cloudron server time is always UTC. This timezone is an implementation detail but it's easier if all logs and db fields are in standard time.

Cloudron Time zone is used for cron job schedules (https://docs.cloudron.io/settings/#timezone)

The times you see in the UI like the logs, eventlog are from the browser timezone . So.. I guess your browser is in UTC+1 ?

This also makes sense - I have a fairly locked down browser security wise, which explains the difference between local time and the time displayed in the browser.
I will try to remember this.

Many thanks again @joseph

Should be fixed with latest package now.

this should be fixed with the latest package now.

@BetterWP awesome, thanks for updating with the solution!

Haven't tried this but have asked @vladimir-d to take a look.

This may be related to default timezone and language settings for users created with the previous package version containing a broken setting. Latest package is fixed, but unfortunately those users already created with the broken package version have to be recreated.

@ramiroro https://community.vikunja.io/ is a better place to report bugs/errors. Use this forum for more packaging related issues and the other one for bugs in the app itself.

@girish - I can also confirm that the latest package resolved the issue! Thanks!

@girish Thanks for the quick update!

The app is finally working again.

@canadaduane and the Cloudron package was updated also to 0.20.0

@girish Great, the e-mail works. Thank you so much for the update 👍

@p44 Thanks!

@girish It's fixed! Thank you very much.

@scooke thank you. Just me then ! But also then usually easier to resolve 🙂

Hi! (Vikunja dev here)

As @girish correctly pointed out, you don't need to enable openid to use the api. In fact, when you're using the Vikunja Frontend or Desktop app it already uses the api. The login endpoint is your way to go to get the api token.

I hope to build "classic" api tokens in the future you may know from other websites (like github) where you can create a long-lived token in the user settings and use it without a login.

@roundhouse1924 thanks for the heads up, our release notification app was stalling for a few days. The new version is published now.

@kolaente thank you !
yep, I understand it's probably a platform default.

@kolaente it does catch the eye !
and I like the domain selection strategy 👍