You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm I have restarted NotePlan and this problem still persists.
Is this a repeatable problem?
Describe the bug
I have used the Search Extensions plugin to create a number of saved searches. saved as notes.
When I click the “Refresh Results” link that’s in those search notes, I always get “No results found for search” popping up. And the results do not refresh.
What do you expect it to do instead?
I expected the results to be refreshed. There are results to be found, as evident in the multiple existing search results, and new items that should be picked up in the refresh.
To Reproduce
Steps to reproduce the behavior:
I expect most of the steps are self-evident. Do let me know if you need more info.
In my tests, I am search for a tag (#waiting-on). I have tried using just the /quicksearch method, and also the /flexisearch method. It doesn’t appear to matter what terms I search for, or other conditions.
E.g., in my /quicksearch I simply searched for #waiting-on. It gives results as expected.
I then add a new instance of #waiting-on in my notes.
I then refresh, and it doesn’t work, as descried in this bug report.
I have also used the /flexisearch to give more complex criteria (doesn’t seem to matter what they are). Same issue occurs.
Screenshots
System
Device: Mac
OS: macOS 14.5
NotePlan Version: 3.12 (1196)
Plugin Name & Version: Search Extensions v1.3.1
Additional context
I think that’s about it.
Plugin Console Log
To provide us with more clues about where the bug/error is occurring...
Open the Plugin's Preferences by going to NotePlan's menu > Preferences > Plugins and clicking the settings "cog" icon next to the plugin in question. Scroll to the bottom and set the logging level to "DEBUG" and click "Save & Close"
Now open the Plugin Console by going to Noteplan > Help > Plugin Console (not the macOS Console app).
Run the plugin command you're reporting
Copy the output from the Plugin Console and paste it below
Delete any output that has personal information you don't want in there
Thanks for the clear report @inspiredearth. I can't try to fix it right now, as I'm in the middle of releasing something else, but I can reproduce the problem. And I can suggest a workaround, which is to reveal the x-callback URL under the 'Refresh' link, and remove the &arg2=... part.
Checks
Describe the bug
I have used the Search Extensions plugin to create a number of saved searches. saved as notes.
When I click the “Refresh Results” link that’s in those search notes, I always get “No results found for search” popping up. And the results do not refresh.
What do you expect it to do instead?
I expected the results to be refreshed. There are results to be found, as evident in the multiple existing search results, and new items that should be picked up in the refresh.
To Reproduce
Steps to reproduce the behavior:
I expect most of the steps are self-evident. Do let me know if you need more info.
In my tests, I am search for a tag (
#waiting-on
). I have tried using just the/quicksearch
method, and also the/flexisearch
method. It doesn’t appear to matter what terms I search for, or other conditions.E.g., in my
/quicksearch
I simply searched for#waiting-on
. It gives results as expected.I then add a new instance of
#waiting-on
in my notes.I then refresh, and it doesn’t work, as descried in this bug report.
I have also used the
/flexisearch
to give more complex criteria (doesn’t seem to matter what they are). Same issue occurs.Screenshots
System
Additional context
I think that’s about it.
Plugin Console Log
To provide us with more clues about where the bug/error is occurring...
NotePlan's menu > Preferences > Plugins
and clicking the settings "cog" icon next to the plugin in question. Scroll to the bottom and set the logging level to "DEBUG" and click "Save & Close"Noteplan > Help > Plugin Console
(not the macOS Console app).The text was updated successfully, but these errors were encountered: