Hey, I assume there are no news about this topic? I have one user, that is not able to see chats in the classic/legacy apps but only on Element X. But this comes with the downside og not being able to make calls
(Besides that the classic apps are barely getting any updates anymore)
[1.11.3]
Update YOURLS to 1.10.3
Full Changelog
added: testing on PHP 8.5 & 8.6 (#4036)
added: function to get reserved URLs from global variable (#3999)
added: database index on long URLs, for faster searches (#4013)
added: $context parameter of yourls_get_db() (#4020)
changed: hide referrers on public statistics page by default (#4005)
changed: set the infos cache of the keyword after a url is added/updated/deleted (#4008)
changed: fix hover-actions in tables for screen reader users (#4025)
changed: confirm link deletion with a modal dialog (#3932)
fixed: upgrade spatie/array-to-xml to address deprecation warnings in newer PHP version (#4037)
fixed: filtering for links with more than 0 clicks (#3977)
[2.11.3]
Update cal.com to 6.0.10
Full Changelog
test: cleanup old skipped e2e tests by @anikdhabal in #26597
fix: improve cleanup for managed event types and fix flaky api v2 e2e test by @anikdhabal in #26602
feat: rename --font-cal to --font-heading + use Cal Sans UI by @pasqualevitiello in #26064
fix(auth): block OAuth linking for unverified accounts by @pedroccastro in #26598
feat: companion add missing advanced event type by @dhairyashiil in #26594
feat: system admin blocklist table by @Udit-takkar in #25039
fix: skip stale run-ci label check on workflow re-runs by @anikdhabal in #26590
fix: Text cursor barely visible in calendar event name field by @Anshumancanrock in #26563
fix: PayPal setup page inconsistent spacing and button styling by @Anshumancanrock in #26612
feat: add BUILD_FROM_BRANCH option to release-docker workflow by @keithwillcode in #26615
Hello @davidbrrrr
The first issue you mentioned .next/cache is okay and can be ignored.
The following issue with 403 seems to be a known issue upstream with localStorage.
https://github.com/gitroomhq/postiz-app/issues/972
and
https://github.com/gitroomhq/postiz-app/issues/918#issuecomment-3254171711
and there even is a PR that fixes this issue: https://github.com/gitroomhq/postiz-app/pull/1085
This is an upstream issue and can't be fixed by Cloudron sadly.
The maintainers of Postiz need to add this fix.
I'd love to have this. The current solutions, already existing on cloudron (@girish) are actually not that mature. I remember you saying, (for the former app-name, hoarder) it could be a hassle to publicize that, but I'd strongly disagree, as this app is simple, easy to use use and allows for a one-stop solution for many use-cases.
Could you please take another look at it?
[1.9.0]
Update greenlight to 3.7.0
Full Changelog
Improve copy recordings functionality (#6154)
Added popovers that describe recording formats (#6136)
Fixed a few Host Header vulnerabilities related to asset urls
Removed role_id from permitted update params (#6117)
Updated multiple gems and packages
Clear recordings before the sync starts (#6164)
Hi @james - Many thanks for asking.
Based on the current state of the app, the stat of the fork and the message of the dev, I would suggest to move to the fork but, since the app is also not the most business critical app for us:
This mostly a @cloudron question. What practices you follow in such case, what makes more sense technically for you etc...We could easily live with both the options you presented
We are possibly not the only one in this situation and others might have alternative preferences
Hope that this makes sense. Thanks again for checking.
@inli for the Hetzner Storage box, the remote directory in the backup site configuration needs to be /home and you can then set a subfolder if you want within the storage box via the "prefix" setting in the backup site config form.
Note that this can only be set while you are adding a new backup site. This cannot be changed in hindsight, so you have to re-add the site in your cloudron.
Hello @luckow
This is an upstream issue for the pretix-oidc plugin thus, I have created an issue upstream: https://github.com/thegcat/pretix-oidc/issues/17
