Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Tasks are not physically moved (is this expected behavior?) #7

Open
luhmann opened this issue Sep 13, 2022 · 9 comments
Open

Comments

@luhmann
Copy link

luhmann commented Sep 13, 2022

Thank you for the plugin, which sounds like it would do exactly what I want, but doesn't when I try to use it, so I wanted to ask if I failed to understand correctly or if something is not working as expected.

I added the unfinishedBusiness- renderer to my daily-template without a specific tag as decribed in the Readme

template:: daily
template-including-parent:: false
- Daily Template  
	- ## Tasks  
		- {{renderer(:unfinishedBusiness)}}  
	- ## Notes  

I expected that this would physically move all my non-completed TODOs to the current day.

Instead the TODOs remain on the page before and instead the text "🚀 Moved 4 tasks(by Marker then Priority) from yesterday" is inserted in the current day (see attached screenshot, I would have expected the todos at the bottom to be at the top. I also tested TODOs that are not nested in a block, the result is the same).

CleanShot 2022_09_13 _09_37_58-Logseq@2x

Is this the expected behaviour?

@rlanhe
Copy link
Contributor

rlanhe commented Sep 15, 2022

I started to see the same behaviour since last week (before it was moving the tasks as you expected). Probably related with one of the last logseq updates?

@rlanhe rlanhe mentioned this issue Sep 19, 2022
@santiyounger
Copy link

Same issue for me, hopefully it can be fixed. Will keep an eye on this issue, thanks @luhmann for posting this

@matthjes
Copy link

matthjes commented Oct 6, 2022

Dito here, seems to have started after update Logseq to the latest version.

@tristengrant
Copy link

Same here.

@matthjes
Copy link

Well, looks like the pull request remains...unfinished business....

I'll show myself out.

@pararang
Copy link

the issue still exists, Does anyone know what the is root cause?
Screenshot 2023-01-19 at 10 22 11

@pararang
Copy link

for the quick hack, I fixed it by updating the code directly on the ~/.logseq/plugins/unfinished-business/dist/index.r4nd0m5tring.js using the result from building code in #8

@martinkoutecky
Copy link

@pararang Hi - how exactly do I do it? I don't know what you mean by "building the code in #8", and I would very much like to have this plugin work!

@matthjes
Copy link

@martinkoutecky I've just tried the suggestion from @pararang.

  1. Open the file @pararang mentioned with some text editor, e.g. Notepad++
  2. It's obfuscated / minimized Javascript, so it's a mess...
  3. Search for the word "moveBlock". There should only be a single hit near the end of the file.
  4. Replace logseq.Editor.moveBlock(t.uuid.$uuid$,n.uuid, with logseq.Editor.moveBlock(t.uuid,n.uuid,
  5. Save
  6. Restart logseq

It should work now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants