mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 16:49:47 +03:00
Unable to edit diagram #3315
Reference in New Issue
Block 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 @Nicks182 on GitHub (Oct 27, 2022).
Describe the Bug
Hi
We've been testing bookstack for a while and really like. Currently running it using Docker Desktop for testing, but we plan to host with ubuntu server.
Yesterday while working on an existing diagram, we were suddenly unable to edit it. We can still view and edit the page, but we can't edit the diagram it self. We can still edit other diagrams and create new ones, but something about this particular diagram causes an Internal Server Error when we try and edit it.
The logs don't contain any info regarding this error. I'm just looking for guidance on how to try and track down the cause so I can either fix or avoid it in the future.
Steps to Reproduce
(This won't be useful as it's only a specific diagram on our end having the problem. Other and even bigger diagrams seems to work fine)
Expected Behaviour
When double clicking the diagram, draw.io should load.
Screenshots or Additional Context
Browser Details
No response
Exact BookStack Version
v22.07.3
PHP Version
No response
Hosting Environment
Windows, Docker Desktop (for testing only, we plan to host on ubuntu server)
@Nicks182 commented on GitHub (Oct 27, 2022):
Just noticed I put this under the wrong label, sorry :(
@ssddanbrown commented on GitHub (Oct 27, 2022):
Hi @Nicks182,
STORAGE_TYPEoption set and, if so, what this is set to?@Nicks182 commented on GitHub (Oct 27, 2022):
I don't recall setting a STORAGE_TYPE and I don't know where to check that.
We can see the diagram while viewing the page and we can even edit the page. We just can't edit the diagram it self.
The diagram was not copied. It was created as part of the original page. I tried to make a copy of the page to see if that would do anything, but it has the same issue.
@ssddanbrown commented on GitHub (Oct 27, 2022):
Hi @Nicks182,
The
STORAGE_TYPEoption will be in your.envfile on a common BookStack install, or maybe passed as an environment option on a docker setup.The error currently seen can be due to the image file no longer existing, or by the current user lacking permissions to view the page it was originally uploaded to.
You can view the images that were uploaded to a specific page by editing that page, then in the editor toolbar click the dropdown arrow next to the insert drawing icon, then select "Drawing Manager", then view the "Page" tab.
Regardless the cause, since you have access to see the image on page view, you can perform a workaround to create a new drawing from the old one. Drawings are stored as png files with drawing data embedded. Save the old drawing to your desktop via right-click > save image. Then, start a new drawing and drag the old drawing png file into the view. It should be editable like before. If you cannot drag and drop on your device, you should be able to use the "File > Import From > Device..." menu item to select and import the old png file.
@Nicks182 commented on GitHub (Oct 27, 2022):
No STORAGE_TYPE is set. Reading about this in the docs now...
Confirmed that saving the image and then importing it in the Drawing Manager works.
Since the current setup was done quick and dirty for testing I'm not sure it's really worth trying to find the exact problem here. I've never even heard of draw.io until we stumbled onto bookstack and so had no idea where or how the data was being stored. But now it's stored in the png fiels and we know where these png files are stored so if it were to happen again we'll be better prepared to deal with it.
Apart from this weird case, everything has been working great which is why we are planning on doing a proper setup on our actual server and I'm having our Linux guy do it this time :)
Thank you for your time and again, sorry for putting this under the wrong label.