-
Notifications
You must be signed in to change notification settings - Fork 155
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
Allow copying attachments from non-default location #178
Comments
The attachment paths are stored in the database, how would a custom attachment path work? |
Ah, I see. Didn't realize the database specified absolute paths. In my ideal world, it'd substitute all database-coded locations with the specified path, for use cases like mine where you have a fully intact Attachments folder from a complete backup, but not in its expected home directory location. How I imagine it would work: If I run imessages-exporter with Any time the database specifies an Attachment in |
Sounds reasonable! |
iMessage Exporter 1.6.0
When
--copy-method
is specified, it appears to look for attachments in the default~/Library/Messages/Attachments/
directory, even if--db-path
is specified, leading to a series of errors such as:and render in the exported HTML as
I suppose this might be by design, but my use case is archiving iMessage databases (including
Attachments
directories) from complete backups on external hard drives.Would love if
--copy-method
looked relative to--db-path
if set, or if there were an additional flag for specifying a custom Attachments directory location.The text was updated successfully, but these errors were encountered: