Skip to content
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

Export Attachments #4

Open
hqsone opened this issue Dec 29, 2023 · 6 comments
Open

Export Attachments #4

hqsone opened this issue Dec 29, 2023 · 6 comments
Assignees

Comments

@hqsone
Copy link

hqsone commented Dec 29, 2023

Is it possible to export attachments?

@Szwendacz99 Szwendacz99 self-assigned this Dec 29, 2023
@Szwendacz99
Copy link
Owner

Currently script does not export attachments. BookStack API gives such possibility, so I think I might make that working as soon as I find time. Currently my idea is to create folder named like __attachments__ next to page to which it was attached, and put them there. But then handling export at multiple levels (pages,chapters,books) could be tricky. I could just make separate folder for only attachments and put all of them there, at their proper paths. If you have suggestions on how that should be handled, you can present them.

@Szwendacz99
Copy link
Owner

Attachments are now exported by default.
If any suggestions/problems arise, feel free to reopen the issue.

@dirks
Copy link

dirks commented Jan 2, 2024

Just in case someone else hits the same problem. In our bookstack we have an attachment linked to a protected resource. The change to export attachments by default thus resulted in a urllib.error.HTTPError: HTTP Error 401: Unauthorized. For me the new flag --dont-export-external-attachments is sufficient to resolve the problem. Thanks for the update. :)

@hqsone
Copy link
Author

hqsone commented Jan 4, 2024

Thank you for your work! Can links attachments be exported to a text file, maybe something like CSV. For example: Link name; link value

@Szwendacz99
Copy link
Owner

Szwendacz99 commented Jan 4, 2024

They could be, and probably this would be good in case of protected resources, so I might look into that.

@Szwendacz99 Szwendacz99 reopened this Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@dirks @hqsone @Szwendacz99 and others