-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Flowchart resetting due to app.diagram.net not working properly #406
Comments
Hi @MxPie200, |
@bijwaard |
Hm ok, so it looks like it's a new bug with currently no solution for? |
Looks like a new bug indeed. What version of the plugin are you using? I'm using 1.0.0d (on grafana 9.3.2).
|
@bijwaard |
Yes, you can update via the command line. You move the old plugin away from /var/lib/grafana/plugins and unzip the latest the beta release in the /var/lib/grafana/plugins folder, then restart grafana. Depending on which version you had previously, you may need to rename the folder to the old name. |
Which files do i have to copy from github? |
just tried on another grafana instance with plugin version 1.0.0b on grafana 9.1.5, and here the editor keeps working, but after saving the result stays blank in the panel, but further editing still works. |
you can rename your ticket to say that embed.diagrams.net is not working properly.... |
hm ok, i've had same as you that changes lead to reset to default flowchart.. |
Hopefully Arnaud just has to update/refresh the embed.diagrams.net library in the plugin.... |
looks like the same problem reported in #395 |
I'm still having the same issue as @bijwaard , in 2023.
I can open the drawing and its showing the mentioned warning:
But if i make any changes to the Flowchart, the whole thing disappeared after closing the editor:
How can I edit my drawing / how can we move to embed.diagrams.net ?
Changing the url in the "Source Content" does not work:
I really like the Flowchart extension and would be great to hear about a fix for my issue.
Originally posted by @MxPie200 in #230 (comment)
The text was updated successfully, but these errors were encountered: