New TODO doesn't appear in Locations

[DonCN]

App version: 0.46.0-beta

---

There's a problem when I use "location" in task manager. First, I create a new Locations, then I create a TODO, and set its Location for the one I created. The problem is that in the Locations, the new TODO doesn't appear.

trilium-2021-02-19.log

[zadam]

Hi, so I think the problem is in the order - it is expected that the location is created automatically from the task by filling in not-yet-seen value.

You can define your own location first, but they you also need to define the taskLocationNote label manually:

Also, don't expect much from this - it's more or less just scripting example not really intended for day-to-day use.

[DonCN]

Hi zadam, thank you for your reply. I did define the #taskLocationNote in the new location, but as you said it didn't work. I tried the order you mentioned, but it did not work, there were no new locations are automatically generated in the Locations. And also, some TODOs have the same location, but only a portion is displayed in the Locations. May be the Inherited attrs "~runOnAttributeChange=attribute changed " did not work.

[zadam]

Hmm, do you have a fresh installation or is it already an older one? I wonder if perhaps it's some old version of task manager.

Also, could you check frontend console (open by CTRL-SHIFT-I) to check if there's any error there?

[DonCN]

It's not a fresh installation, I just deleted the old "trilium-windows-x64" and pasted the new one. App version 0.45.10->0.46.0-beta->0.46.1-beta.

Frontend console error: keyboard_actions.js:76 Cannot find action logout keyboard_actions.js:76 Cannot find action searchNotes tree.js:73 09:35:27 Did not find parent root (root) for child mrLtEsD45NLu (attribute changed), available parents: EHijesmxLe9Z (Implementation) tree_context_menu.js:132 Triggering deleteNotes root/uKWH4wNoUUWO/jIAuOC0gCIUo/iQWWcler9BCy/7E3KAaiCF3E1 tree.js:73 09:36:57 Did not find parent root (root) for child he0O2D7AlxHd (new task), available parents: iQWWcler9BCy (TODO) tree_context_menu.js:132 Triggering recentChangesInSubtree root/uKWH4wNoUUWO/jIAuOC0gCIUo/X1sLwXDF6nct tree_context_menu.js:132 Triggering recentChangesInSubtree root/uKWH4wNoUUWO/jIAuOC0gCIUo/iQWWcler9BCy ws.js:20 10:44:14 Uncaught error: Message: ResizeObserver loop limit exceeded, URL: http://127.0.0.1:37840/#root/Mm3vwHCbpPtq/PPhBUorRTuZU/TTwDK0og9hAG-9u2m, Line: 0, Column: 0, Error object: null, Stack: null w @ desktop.js:1 ws.js:20 10:47:43 Uncaught error: Message: ResizeObserver loop limit exceeded, URL: http://127.0.0.1:37840/#root/Mm3vwHCbpPtq/PPhBUorRTuZU/TTwDK0og9hAG-9u2m, Line: 0, Column: 0, Error object: null, Stack: null w @ desktop.js:1 ws.js:203 11:13:45 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 11:13:46 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 11:13:47 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 11:15:32 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 11:15:33 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 11:15:33 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 11:15:33 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 11:15:33 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 11:15:33 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 11:15:34 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 11:15:34 WS closed or closing, trying to reconnect ws.js:193 11:15:35 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 11:15:36 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 12:12:54 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:12:55 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:12:56 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:12:57 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:12:58 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:12:59 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:13:00 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 12:13:01 WS closed or closing, trying to reconnect 2ws.js:193 15:00:59 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 15:01:00 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 15:01:00 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 15:01:01 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 15:01:01 WS closed or closing, trying to reconnect ws.js:193 15:01:02 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 15:01:03 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 15:01:04 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 15:01:05 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 16:15:14 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 16:15:15 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 16:15:16 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:203 16:15:17 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 14:42:14 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 14:42:14 WS closed or closing, trying to reconnect ws.js:183 WebSocket connection to 'ws://127.0.0.1:37840/' failed: Error in connection establishment: net::ERR_NETWORK_IO_SUSPENDED C @ desktop.js:1 ws.js:193 14:42:15 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:203 14:42:15 WS closed or closing, trying to reconnect ws.js:193 14:42:16 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 14:42:17 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 14:42:18 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 14:42:19 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 14:42:20 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. ws.js:193 14:42:21 Lost websocket connection to the backend. If you keep having this issue repeatedly, you might want to check your reverse proxy (nginx, apache) configuration and allow/unblock WebSocket. DevTools failed to load SourceMap: Could not load content for http://127.0.0.1:37840/libraries/bootstrap/js/bootstrap.bundle.min.js.map: Unknown error DevTools failed to load SourceMap: Could not load content for http://127.0.0.1:37840/libraries/fancytree/jquery.fancytree-all-deps.min.js.map: Unknown error DevTools failed to load SourceMap: Could not load content for http://127.0.0.1:37840/libraries/split.min.js.map: Unknown error DevTools failed to load SourceMap: Could not load content for http://127.0.0.1:37840/libraries/ckeditor/ckeditor.js.map: Unknown error DevTools failed to load SourceMap: Could not load content for http://127.0.0.1:37840/libraries/bootstrap/css/bootstrap.min.css.map: Unknown error

[zadam]

Hmm, I see, it is because WebSocket does not work ... This usually happens because proxy server misconfiguration but based on the port number you have a desktop version which shouldn't have any such issues ...

What is your platform? Did Trilium (and this Task Manager functionality) used to work before and broke only with this update?

[DonCN]

It looks like the problem is to be determined :-). OS: Windows 10 v1809. I think the Trilium used to work with v0.45.9-portable. By the way, I deleted the newer version, and pasted "trilium-windows-x64"v0.45.9, but the Trilium.exe did not start, so I could not test it.

[Magic-King]

I have the similar question with that.

I just use scoop to update trilium to the version 0.46.6

OS:windows 10 v20H2

devTools show that: Cannot find action logout keyboard_actions.js:76 Cannot find action searchNotes keyboard_actions.js:76