To make it easier for future developers ive moved the Agenda repository back to Github since thats what most developers and Joplin uses. The link is here
2 Likes
Hi there,
starting with Joplin 2.10.* (tested with 2.10.2 and 2.10.3) the Agenda Plugin is no longer working.
When you start Joplin with a 2.10.* Version then the space for the agenda plugin is just empty. Going down to 2.9.17 (latest 2.9. release) the plugin works again.
I am not enough of a developer to get deeper in - hope others can find the bug.
Regards,
Michael
That will be fixed in the next pre-release
Thanks, I can confirm that the sqlilte3 database accesses is working again with version 2.10.4
Regards,
Michael
1 Like
Hi,
thats a grat Plugin, thanks. Unfortunately I can't use it because I use the Kanban Plugin too and this Plugin is not working with the Kanban Plugin. Is there any possibility to get them work together? For me it would helpfull if I can choose in wich notebooks this Plugin is shown.
Regards, Michael
Hey, it seems this plugin is now broken on the new Joplin version 2.12.15.
Clicking a different agenda profile will not load the profile, and the panel does not refresh. The only way to get it to refresh or change profiles is to select the necessary profile, and then completely restart Joplin. Upon loading, the agenda panel shows up with the selected profile.
I've tried disabling the plugin, deleting and adding it back, creating new profiles and deleting old ones, and even completely reinstalling Joplin. Same issue occurs.
Is there any possibility of this issue being resolved? I understand this plugin needs a maintainer.
I'm not sure if anyone else is experiencing the same issue.
Never mind, I was able to solve the issue. After checking the developer console, I noticed it was throwing up an exception because I set the Overview Note ID to partially have the markdown link, specifically ":/" before the actual note ID. Once I removed those two characters leaving just the string of characters, I managed to switch between profiles.
Strangely, this was how I was using the plugin for months, and it only recently became an issue after the update. Not sure if it was just a coincidence, or if it was indeed the update.
1 Like