🌞 Community / Help Features👍👎 Bugs 🐞🐞
Here is the summary list of OpenCanyon.org's current open bugs from the Slack channel #canyon-db-bugs.
Topics are basically added on Slack, discussed there in the thread and also closed there. Requests please in Slack channel #canyon-db-feature-request.
Currently open bugs from Slack
| Prio | Bug | User | Date | Link |
|---|---|---|---|---|
| Prio: 2 | There is a nother picture reorder bug in the backend. You have to upload pictures, then delete and reorder at the same time, then woops pictures are gone, see video --- Reply 24.04.2026 21:03:26 by Max --- Root cause found => we need to rework picture handling in general to fix this --- Reply 24.04.2026 21:04:14 by Max --- As a workaround I will temporary disable picture delete in the repeater in order to not loose to many pictures :slightly_smiling_face: --- Reply 24.04.2026 21:41:09 by Max --- Workaround merged, see https://github.com/canyoningdb/db-v2-filament/pull/767 --- Reply 24.04.2026 21:57:38 by Max --- Implementation see/continue https://github.com/canyoningdb/db-v2-filament/tree/max/rework-backend-picture-handling | Max | 24.04.2026 12:37:36 | Slack Link |
| Prio: 2 | Version 0.23.2 request: GET /fr/canyon/3ddc259c-59cd-4c6e-ae52-97f52b7a4ce6 playground.ERROR: Allowed memory size of 134217728 bytes exhausted (tried to allocate 48463048 bytes) {"userId":2,"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\FatalError(code: 0): Allowed memory size of 134217728 bytes exhausted (tried to allocate 48463048 bytes) at /var/www/playground.opencanyon.org/vendor/laravel/framework/src/Illuminate/View/Concerns/ManagesComponents.php:196) --- Reply 24.04.2026 17:29:16 by Max --- Can be reproduced locally /fr/canyon/5b18896c-ee97-4284-9b6f-6874d7823258 with 0.23.1 has 8MB memory /fr/canyon/5b18896c-ee97-4284-9b6f-6874d7823258 with 0.23.2 has 120MB memory --- Reply 24.04.2026 18:59:46 by Max --- Temporary fix found with https://github.com/canyoningdb/db-v2-filament/pull/766 Could you have a look at a more permanent fix? --- Reply 25.04.2026 10:50:42 by P. Eisen --- first information: • the gmaps icon is the fault. it increases the used memory alot. • the gmaps.svg has 4´203 KB (4MB) on the local storage. • as x-icon / svg it is rendered multiple times so the mem_usage grows linear to the amount of coordinates a canyon has --- Reply 25.04.2026 11:53:56 by P. Eisen --- As far as i understand the gmaps.svg should be seen as asset not as icon because of its size. I tried different approaches to bind gmaps.svg as <img or implement a .svg sprite. But in any case i have to build a new workflow that puts the asset in the public folder. I shy away from building that new because i think we already have such a mechanism that puts content in the public folder. I just cant find the proper way which is used so far. Can someone explain to me how we put content in the /public folder automatically? --- Reply 25.04.2026 19:04:39 by Max --- Been in the mountains, just came back ... • A svg icon should typically not exceed 50kb, especially when we render it as 16x16, in case of the gmaps its a png as base64 added inside a svg, probably we need another source or an other converter. Maybe this one? https://upload.wikimedia.org/wikipedia/commons/a/aa/Google_Maps_icon_%282020%29.svg • /public/assets/svg has a dynamic link to /ressources/svg, this link is created locally when you run the command php artisan storage:link --- Reply 26.04.2026 08:56:50 by P. Eisen --- 1. Regarding the storage:link we can fix this bug by replacing "<x-icon name="gmaps" /> with <img src="{{ asset('assets/svg/gmaps.svg') }}">. Due to the intelligence of the browser it is caching the img and the mem_usage drops to 14 mb in my env for http://web.opencanyon.test/fr/canyon/3ddc259c-59cd-4c6e-ae52-97f52b7a4ce6#description 2. if we want to think about this case as precedent we can discuss when to use .svg and when it should be another format and try to build a rule out of that. Let me know if i can just make a feature branch with the fix mentioned in 1. --- Reply 26.04.2026 12:10:44 by Max --- • I guess using a svg that is cache by the browser instead of the inline svg is a good idea if we have to use the icons on multiple times in the page, that would also take care of canyons with many coordinates like: https://playground.opencanyon.org/de/canyon/88d96ff2-94dc-401f-b215-9bbf2563ed22#description • please also reduce the size of the icon as mentioned before • the /asset/svg/icon-example.svg data is automatically cached for 30 days in the browser, if the file is changed the cache is automatically updated --- Reply 28.04.2026 10:01:30 by P. Eisen --- i made a pullrequest with the mentioned changes: https://github.com/canyoningdb/db-v2-filament/pull/768 | Max | 24.04.2026 12:35:21 | Slack Link |
| Prio: 2 | When you add report pictures with descriptions the dirscriptions are translated and stored in translation_cache but on the page they are still shown as original text, see for example here | Max | 27.06.2025 16:33:59 | From DB Cache |
| Prio: 2 | Check and fix why we have audit logs without relationship, see examples in db with SELECT * FROM audits where user_type is null | Max | 19.09.2025 19:16:15 | From DB Cache |
| Prio: 2 | The API for Canyon's always displays warnings in German, regardless of the locale specified. This leads to mixed translations in the app, as the texts for the period are translated by the app, but the rest are not. This was noticed in the bachab chat, as people in French-speaking Switzerland do not always understand German. I would have looked into it in detail and solved it myself, but I'm currently unable to do anything. | Urs | 07.11.2025 15:41:21 | From DB Cache |
| Prio: 2 | I somehow can't add any canyon to a list. | Reto Bubendorf | 15.11.2025 21:04:52 | From DB Cache |
| Prio: 2 | *We have constant errors on notifcations, root cause currently unknown ...* Request: POST /livewire/update Userinfo: NULL Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php:32 Stacktrace: #0 [internal function]: Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}() #1 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Arr.php(788): array_map() #2 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Collection.php(819): Illuminate\Support\Arr::map() #3 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Collection.php(1753): Illuminate\Support\Collection->map() #4 /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php(31): Illuminate\Support\Collection->transform() #5 /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Features/SupportWireables/WireableSynth.php(41): Filament\Notifications\Collection::fromLivewire() #6 /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php(232): Livewire\Features\SupportWireables\WireableSynth->hydrate()... *Level* ERROR Laravel PROD | 13. Jan. [00:30 Uhr] *Message* 500 POST /livewire/update Userinfo: NULL Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php:32 *Level* ERROR Laravel PROD | 13. Jan. [00:30 Uhr] *Message* Request: POST /livewire/update Userinfo: NULL Cannot assign array to property Filament\Notifications\Livewire\Notifications::$isFilamentNotificationsComponent of type bool /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php:442 Stacktrace: #0 /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php(342): Livewire\Mechanisms\HandleComponents\HandleComponents->setComponentPropertyAwareOfTypes() *Level* ERROR Laravel PROD | 13. Jan. [00:30 Uhr] *Message* 500 POST /livewire/update Userinfo: NULL Cannot assign array to property Filament\Notifications\Livewire\Notifications::$isFilamentNotificationsComponent of type bool /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php:442 *Level* ERROR Laravel PROD | 13. Jan. [00:30 Uhr] *Message* Request: POST /livewire/update Userinfo: NULL Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php:32 Stacktrace: #0 [internal function]: Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}() #1 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Arr.php(788): array_map() #2 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Collection.php(819): Illuminate\Support\Arr::map() #3 /var/www/preview1.opencanyon.org/vendor/laravel/framework/src/Illuminate/Collections/Collection.php(1753): Illuminate\Support\Collection->map() #4 /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php(31): Illuminate\Support\Collection->transform() #5 /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Features/SupportWireables/WireableSynth.php(41): Filament\Notifications\Collection::fromLivewire() #6 /var/www/preview1.opencanyon.org/vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php(232): Livewire\Features\SupportWireables\WireableSynth->hydrate()... *Level* ERROR Laravel PROD | 13. Jan. [00:30 Uhr] *Message* 500 POST /livewire/update Userinfo: NULL Filament\Notifications\Collection::{closure:Filament\Notifications\Collection::fromLivewire():32}(): Argument #1 ($notification) must be of type array, int given /var/www/preview1.opencanyon.org/vendor/filament/notifications/src/Collection.php:32 *Level* ERROR | Max | 16.01.2026 08:06:20 | From DB Cache |
| Prio: 2 | *We have errors on canyon create* 500 POST /livewire/update Previous: Full: Userinfo: Olda Stos (ID: 1090) Cannot assign null to property App\Filament\Resources\Canyons\Pages\CreateCanyon::$form_gps_long of type string /var/www/preview1.opencanyon.org/app/Filament/Resources/Canyons/Pages/CreateCanyon.php:85 *Level* ERROR 500 POST /livewire/update Previous: Full: Userinfo: MirkoT (ID: 758) Cannot assign null to property App\Filament\Resources\Canyons\Pages\CreateCanyon::$form_gps_long of type string /var/www/preview1.opencanyon.org/app/Filament/Resources/Canyons/Pages/CreateCanyon.php:85 *Level* ERROR Any idea how we could reproduce this? | Max | 16.01.2026 08:04:12 | From DB Cache |
| Prio: 3 | When attempting to create a new canyon, validity checker insists on a sub-region, even though this is marked as not an obligatory field. E.g. Create a canyon in Romania at 46.805167 25.829056 (I don’t know if Romania has sub-regions) | David Mason | 21.07.2025 21:09:34 | From DB Cache |
| Prio: 3 | Invalid link when Sharing from the app, e.g. | Christian Balla | 12.05.2025 19:07:06 | From DB Cache |
| Prio: 3 | Make create canyon warning mobile ready | Max | 27.06.2025 15:01:44 | From DB Cache |
| Prio: 3 | Show translated report description under report pictures | Erik Weisz | 17.07.2025 06:56:32 | From DB Cache |
| Prio: 3 | We should only allow numbers as page nr, not 12-23 in backend on all literature screens | Max | 16.07.2025 05:03:01 | From DB Cache |
| Prio: 3 | When creating a new canyon, when a country is selected, the region selection should only show regions for that country (not all the regions in the database). Similarly, sub-region should only show for the selected region. | David Mason | 21.07.2025 21:44:58 | From DB Cache |
| Prio: 3 | If I Remove a canyon from a favorites list on the canyon itself and at the same time have the favorites list open and modified the descriptions there - I get a 500 when saving the favorites list. (I am aware this is an edge case - in my Opinion the list itself should always win over the canyon) | Daniel Sturm | 18.09.2025 09:53:59 | From DB Cache |
| Prio: 3 | Map zoom of website sometimes also zooms page | Max | 27.09.2025 16:17:44 | From DB Cache |
| Prio: 3 | filament shield doesnt show the item for role translator. Also for user super_admin the translator function is disabled | Max | 22.11.2025 15:16:45 | From DB Cache |
| Prio: 3 | Check why we always get a cache miss on playground apy for canyon full download via app - - [30/Nov/2025:20:21:21 +0100] "GET /public/api/v1/canyon/list/full?limit=500&page=1&locale=en HTTP/1.1" "" "MISS" "7.365" "Mozilla/5.0 (Linux; Android 16; SM-S921B .. On prod it seems to be working :) | Max | 30.11.2025 19:22:44 | From DB Cache |
| Prio: 4 | On canyon create we dynamicycally create new regions and subregion but they never show up as the select options are not refreshed. In order to fix this I would just "show" the information that was generated automatically during the "create" screen and the at a later stage let the user edit it in the canyon edit view. Any objections here? | Max | 07.09.2025 11:36:49 | From DB Cache |
| Prio: 4 | *Limit Date ranges for Warnings and First Decents* We can enter Warnings with unreasonable dates (e.g. from 15.10 to 08.10. -->it is displayed but it shouldn't be possible to enter) First descent in the future shouldn't be possible either. | Max | 25.10.2025 08:30:04 | From DB Cache |
| Prio: 4 | When I add a new gear - the name displayed right after I save the new gear is "Technical" Once the canyon is refreshed the correct "Displayname" of the gear is shown. | Max | 24.04.2026 10:54:07 | Slack Link |
| Prio: 4 | Playground: First decent can be entered in the future | Daniel Sturm | 20.04.2026 08:13:11 | Slack Link |
| Prio: 4 | Make and bugs mobile ready | Max | 27.06.2025 15:01:30 | From DB Cache |
| Prio: 4 | Topo test is to long within the pictures in the overview, see example here | Max | 27.06.2025 11:34:14 | From DB Cache |
| Prio: 4 | Analyse why picture is not responsive | Max | 29.06.2025 18:28:17 | From DB Cache |
| Prio: 4 | When editing a favorites list, and reordering the canyons, the next time you open the same list to edit, the order is not preserved. | Erik Weisz | 03.07.2025 07:04:21 | From DB Cache |
| Prio: 4 | Website tells me there are non saved changes when I try to close the tab - even though I just saved the canyon. | Daniel Sturm | 28.07.2025 08:40:10 | From DB Cache |
| Prio: 4 | Specialities are displaced when a siphon is connected to a canyon e.g. Toce: | Daniel Sturm | 04.08.2025 05:47:19 | From DB Cache |
| Prio: 4 | Canyon height does not get calculated if canyon ends on sea level. | Daniel Sturm | 22.08.2025 08:57:10 | From DB Cache |
| Prio: 4 | Package mohamedsabil83/filament-forms-tinyeditor is abandoned, you should avoid using it. Use instead | Max | 05.09.2025 04:23:36 | From DB Cache |
| Prio: 4 | Point descriptions imported from descente have weirdly-escaped ' characters, these should be removed: | Erik Weisz | 08.09.2025 09:16:32 | From DB Cache |
| Prio: 4 | Is this a bug in the language recognition? | Daniel Sturm | 16.10.2025 09:14:17 | From DB Cache |
| Prio: 4 | On descente Canyon Import it seems that the information shown in field *grading_engagement* is initially wrong (one stage to low) for all canyons. We should double check and update this info by a seeder or similar which checks live data from descente, checks if the canyon was not updated on opencanyon and if all conditions are ok then transfer the data. Problem here is often that we cant just read many pages at once, so we need to to that async and store the info somewhere for further processing. | Max | 30.10.2025 10:20:09 | From DB Cache |
| Prio: 4 | link overflows page | Daniel Sturm | 15.12.2025 06:46:21 | From DB Cache |
| Prio: 6 | Text running out of the page https://www.opencanyon.org/de/canyon/d235a9df-1ea2-47d2-893f-22d61c30a552#description --- Reply 31.03.2026 13:32:28 by Christoph Cramer --- Can't reproduce this. Looks OK at my PC with latest Firefox on W11. --- Reply 31.03.2026 13:55:45 by Daniel Sturm --- I'm on windows 11 using the latest chrome version. 10/10 reproducable on my machine. --- Reply 31.03.2026 14:14:41 by Christoph Cramer --- I can reproduce it with Edge on my machine. So it's browser engine dependent. I believe this is due to the extremely long URL. Probably a configuration in the browser? We should automatically convert URLs in the description to links to avoid this maybe.. | Daniel Sturm | 20.03.2026 08:23:42 | Slack Link |
| Prio: 6 | Pictures shown from reports in the pictures section are blurry in the overview. Is it possible to have them appear in the backend as "normal" picture upload as well? So we can edit the description or "promote" the topo picture to the actual "topo" picture category? | Daniel Sturm | 27.10.2025 13:07:51 | From DB Cache |
| Prio: 6 | nearby page filter is cut off when we only get one line as response | Max | 22.11.2025 20:08:09 | From DB Cache |