Error displaying a quote

[tecnoborder]

Starting from today, the quote I have in my home page does not show (always, sometimes it does) correctly

[tecnoborder]

[sundevista]

Is this console error and Local Quotes' message ("You caught an error...") show up in the same time?

[tecnoborder]

[tecnoborder]

nothing specific to local quotes

[sundevista]

Try to clear block metadata and one-time block metadata in the Local Quotes settings. It's placed in a "Danger Zone". It'll clear cached metadata. Then you should relaunch app. It must help. If it's not help, write me back.

[tecnoborder]

I did so and relaunched the app. Unforuntalt the issue is still present

[sundevista]

Do you create this quote block via Quote Maker or by typing code block by yourself? If yes, did you validate a search?

[tecnoborder]

the quote maker. I found this problem happening when I use the workspace feature of obsidian to lead the home page. I have a home page note with an inserted quote.

[sundevista]

I tried to reproduce it with workspaces and all work correctly. Can you share a sample vault with the problem?

[tecnoborder]

The issue does not happen always. I will investigate further!

[sundevista]

I'll be waiting for the results of your investigation

[tecnoborder]

[tecnoborder]

Could it be a problem with the load of dataview?

[tecnoborder]

[tecnoborder]

when I click on the refresh button

[sundevista]

It is just info message

Could it be a problem with the load of dataview?

I don't think so, but previously I caught and fixed some conflicts with the dataview

[sundevista]

Can you send me a code block that provoke an issue? You can replace private parts (e.g. author) if it's necessary

[tecnoborder]

:::This is the author:::

• 1) This is a quote: This is a sub-quote
• 2) This is the second quote: This is another sub-quote

[tecnoborder]

id aZn3k
search This is the author
refresh 1d

[sundevista]

There is nothing suspicious. You said it works sometimes?

[sundevista]

#20 Error displaying a quote

[tecnoborder]

Yes, I can confirm the bug is still present

[sundevista]

This issue should be fixed with the latest commits. The update will be shipped today!