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

Workfiles tool > Published > Copy & Open - invalidly prompts for save file extension #1118

Open
2 tasks done
BigRoy opened this issue Feb 3, 2025 · 0 comments
Open
2 tasks done
Labels
type: bug Something isn't working

Comments

@BigRoy
Copy link
Collaborator

BigRoy commented Feb 3, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior:

When doing a Copy & Open then the user gets the save prompt with allowing the user to check the extension. However - what it'll do is just take the published file, and copy it with the different extension - in this case it'd e.g. just copy the .zip as .sfx instead of actually "resaving" it into a different format. Worse even, it does not default to the extension of the published file, but to the 'first' file extension defined for the host.

Image

Image

I think "Copy & Open" should not allow changing the extension. So the copy should always use the extension from the published file.

Expected Behavior:

Matching the extension seems most reasonable - disallowing the extension change in the prompt.

Version

1.0.14

What platform you are running on?

Windows

Steps To Reproduce:

  1. In Silhouette integration, publish workfile as .zip
  2. Use "Copy and Open" from published section in workfiles tool
  3. It'll prompt to default to .sfx (and just copy the .zip as .sfx) which is the incorrect format.
  4. Hence Silhouette will be unable to open the file.

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

Additional context:

Came up internally in a private chat here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant