Filter bug
Hello, I try to apply a filter on a multiselection field in Companies and I get this error (image attached)
SyntaxError: JSON Parse error: Unexpected EOF
parse
kq — index-DXIJshCq.js:10711:1929
TMn — index-DXIJshCq.js:10711:2376
HD — index-DXIJshCq.js:46:17955
boe — index-DXIJshCq.js:48:45346
hoe — index-DXIJshCq.js:48:40875
$Ze — index-DXIJshCq.js:48:40799
H7 — index-DXIJshCq.js:48:40649
yL — index-DXIJshCq.js:48:36882
doe — index-DXIJshCq.js:48:37696
Rg — index-DXIJshCq.js:46:3298
(anonymous function) — index-DXIJshCq.js:48:35176
Any idea how to correct this?
In the logs, I have nothing specific, expect this (but not related to the action):
codex-server | That means you use raw catalog or your catalog doesn't have a translation for the message and fallback was used.
codex-server | ICU features such as interpolation and plurals will not work properly for that message.
codex-server |
codex-server | Please compile your catalog first.
codex-server |
codex-server | Uncompiled message detected! Message:
codex-server |
codex-server | > Li5Lbf
3 Replies
Hey, what version are you running? There was a bug but it should be fixed by now https://github.com/twentyhq/twenty/issues/14367
GitHub
View breaks when applying filter on Select field (v1.5.0) · Issue ...
Bug Description When a user clicks the Filter button on any field of type Select , the entire view breaks immediately. The filter UI never appears, so no values can be chosen. This issue is a regre...
Hi Bob, I'm using 1.5.0. I saw that it has been corrected in 1.5.3, so I will update and confirm
Thanks
When I do :
docker exec -e PGPASSWORD="${PG_DATABASE_PASSWORD}" "${CONTAINER_NAME}" \
psql -h localhost -U "${PG_DATABASE_USER}" -d "${PG_DATABASE_NAME}" \
-c "\x" -c "SELECT * FROM core.workspace;"
I had (before update) and after update version : 1.5.0
In the logs, I have:
Nest] 57 - 09/12/2025, 11:55:28 AM LOG [UpgradeCommand] Upgrading workspace 5bc2d041-8036-41ed-ba7a-a5514e1216d6 from=1.4.0 to=1.5.3 1/2
codex-server | [Nest] 57 - 09/12/2025, 11:55:28 AM LOG [UpgradeCommand] Upgrade for workspace 5bc2d041-8036-41ed-ba7a-a5514e1216d6 ignored as is already at a higher version.
So I suppose I am in 1.5.3 but in the DB I still see 1.5.0. It would be usefull to get the exact version somewhere. An API call?
And I confirm that I don't have the bug anymore after update, thanks Bob!
Hey you will need to either restore a backup of a previous version or either manually change your workspace version in database to 1.4.0 only if it's 1.5.0
For 1.5.3 upgrade to run