Email Export

Thank you for this report, we could reproduce the issue and our team is working on it.

@mathieu1 thanks for the update, I’ll hold off on deployment until I hear from you.

Cheers

DK

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

1 Like

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 .gz file 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 .dxf file
    or
  • A .zip file, 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

1 Like

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.

1 Like

@kiteboardshaper We have updated the Email Export component, it should now export archives as .zip files when the archives are included in emails.

1 Like

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

1 Like

@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?)