Thank you for this report, we could reproduce the issue and our team is working on it.
Hi Guys,
Its been a month - has there been any progress on fixing this DXF file issue?
Cheers
DK
The reason Iām chasing is Iāve had two users in the last 24hrs create āblankā export files - which without the JSON from the website I canāt trace the error - to improve my code I need to be able to test the setting that are causing errors.
Cheers
DK
We have released a fix for the issue you mentioned in your previous message. For technical reasons, that means files included in emails are now included in archives.
However, as I understood it, the issue is only for the attached exported files, correct? There should have been no issues with attaching JSON files using the latest version of the component. In Grasshopper, you can separately enable attaching the exported file to the email and/or the JSON file.
Hi Mathieu, yeah I was waiting for the DXF fix to do the update that would give me the JSON file as well.
Iāll jump on and test as soon as I find 5 minā¦
Cheers
DK
Hi Guys
First offāhuge thanks for the recent improvements to the DXF export via email. I finally had time to test it out tonight, and hereās a quick rundown:
- The JSON file comes through perfectlyāno issues at all.
- The email is sent directly to the client with me CCādāthis is awesome. Iāve been hoping for that for years, so massive thanks for making it happen.
- Even better, the DXF file is no longer brokenāgreat to see this resolved!
That said, I have one major request regarding the DXF attachment:
Please donāt use .gz files for compression
The DXF currently arrives as a .gz file. While I understand itās probably a lightweight and efficient format for backend systems, itās not user-friendly for non-technical users.
Most clients:
- Donāt know what a
.gzfile is. - Donāt have the tools to open it.
- Might assume the file is corrupted or suspicious.
Suggestion:
Could we please switch the DXF attachment to be either:
- A raw
.dxffile
or - A
.zipfile, which is universally supported and easy to open on all platforms.
This would make a huge difference for usabilityāespecially for clients who arenāt particularly tech-savvy.
Thanks again for the great progressāreally appreciate the work thatās gone into this so far.
Cheers,
DK
Guys, I must say WOW - having the ability to add a cc address AND the .json parameter file to the email is a MASSIVE improvement on Shapediver.
Being able to get the parameter .json file to my own inbox AND being able to load this into the local GH file is going to be HUGE help in bug tracking and fixing - I will no longer need to rely on my users saving the .json and sending to me.
THANK YOU!
Cheers
DK
Thank you for the kind feedback!
The reason why we do not include raw files directly in the emails is that uncompressed files are much bigger. I filed a task for our team to switch from .gz to .zip in the next release.
Note that you still have the option to include a download link instead of including the file directly in the email; in that case, the downloaded file will directly be in the target file format (.dxf in your case) as our servers take care of the decompression when downloading it.
@kiteboardshaper We have updated the Email Export component, it should now export archives as .zip files when the archives are included in emails.
Hi @mathieu1
Thank you for the update mate - I saw that change come thru on a customer download yesterday - very happy to see!
Cheers
DK
@mathieu1 Thanks for the update, very usefull indeed!
SIde question, Is it actually possible to send Two separate emails when clicking on the export? One Email to the webshop with all the paraneter data and one to the customer with more simplified data (Some sort of confirmation email?)