-
-
Notifications
You must be signed in to change notification settings - Fork 59
URI too long message #20
Comments
The plugin uses the and url for clipping the entire set of data, if you are clipping an entire page for example, the dataset simply is too large to fit into an URL. I haven't found a solution for this problem. I will keep this issue open as a reminder, but at this moment it is not possible to fix this... |
Aaah gotcha. Any ideas on the limit? Might be worth putting something in the docs about that. |
Sooo, just thinking a bit more about this - Joplin has a Web clipper, but I don't think Obsidian has the same sort of service to expose a browser to it's API. I'm guessing the Alfred script already has system file access, so a lot more to work with. Not much good there either. This came up recently in the forum, so I don't know whether the webhooks is an option for the plugin. |
How does the quiver clipper do it ? I haven't had problems with it. or maybe I just didn't clip enough. Howdy! @jplattel also, what about using the advanced uri plugin in tandem with the clipper, if the dataset exceeds the max size, push the note in parts, appending to the newly created note |
Using the advanced URL plugin might be an option, but it does involve more pieces of a puzzle resulting in a fragile system that might result in even more bugs... In the future I might make it an advanced option! I'll keep it in mind and keep this issue open! |
Had this issue a couple of times now, the extension complains about the URI being too long. Here's an example page.
My settings are:
Tried removing the {title} tag from the note title, but still have the same issue.
The text was updated successfully, but these errors were encountered: