mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
How do I add an existing draw.io diagram? #866
Closed
opened 2026-02-04 22:37:40 +03:00 by OVERLORD
·
7 comments
No Branch/Tag Specified
development
l10n_development
further_theme_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
No Label
❓ Question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#866
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Leon99 on GitHub (Oct 18, 2018).
I've got so excited to find a wiki that satisfies all the requirements we had only to realise that there (seems to be) no way to make use of all our current diagrams. Am I missing something?
@ssddanbrown commented on GitHub (Oct 18, 2018):
@Leon99 Do you know the format of your current diagrams? (Draw.io has a few export options).
Are they embedded within other content?
By default BookStack uses png's with emedded draw.io info, Wrapped in a tag to identify them as diagrams.
@davidjgraph commented on GitHub (Oct 18, 2018):
One way is create a blank diagram in Bookstack, open the original diagram, ctrl/cmd+a to select all in the original, ctrl/cmd+c to copy, then ctrl/cmd+v in the blank bookstack draw.io editor to paste the diagram in.
@Leon99 commented on GitHub (Oct 20, 2018):
@ssddanbrown I wasn't aware draw.io has different formats. I just open it and draw my diagram, then save it on my GDrive.
@davidjgraph it'd be a somewhat cumbersome solution, but I tried that and it didn't work for me - only small subset of the elements are pasted in the new diagram.
@davidjgraph commented on GitHub (Oct 20, 2018):
@Leon99 If you have multiple layers it will select only the active layer. Another question, would you pay for a cloud managed version of Bookstack? Something like an AWS, GCP image you running up with a premium pricing on the VM. Not that we intend to supply this, but I think Dan should be building this out full-time 8-).
@ssddanbrown we wrote a Google Drive viewer for Confluence, welcome to use the code.
It might seem strange people mixing cloud and on-premise tools, but we see a lot of requests for the connector in Confluence Server, but are often using on-premise because the cloud hosted options don't cut it.
@Leon99 commented on GitHub (Oct 20, 2018):
Hell yeah, copy-pasting all our diagrams layer-by-layer is not just annoying but time-consuming and error-prone, although looks likes there is no choice :(
Cloud-managed version? Maybe, depending on the price.
@ssddanbrown Is there a hope in
?
@ssddanbrown commented on GitHub (Oct 21, 2018):
@Leon99 Unfortunately not, Thinking deeper, it will be a lot of work to get the content in the format that BookStack expects.
I just done a test using google drive and BookStack. I found exporting my drive drawing as XML then importing via the BookStack draw.io editor (File > Import from > device) did import the drawing with all layers as expected. I can understand this is a big hassle though. You can speed this up by dragging the downloading XML file into the drawing editor instead of using the import menu.
@davidjgraph Thanks for offering the code. I'll keep that in mind but gdrive integration has been an fairly uncommon request so far so probably not worth the effort right now to implement & maintain.
@ssddanbrown commented on GitHub (Mar 13, 2020):
Since this conversation is over a year old, and did not move any further, I'll go ahead and close this off.