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.

Sign up for GitHub

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

Jump to bottom

Octoprint renames auto0.g to auto0.gco on upload to SD #1314

Closed
Lenbok opened this issue Apr 17, 2016 · 1 comment
Closed

Octoprint renames auto0.g to auto0.gco on upload to SD #1314

Lenbok opened this issue Apr 17, 2016 · 1 comment
Labels
bug Issue describes a bug done Done but not yet released
Milestone
1.2.12

Comments

@Lenbok
Copy link

Lenbok commented Apr 17, 2016

What were you doing?

Marlin supports running gcode files automatically on startup. This is a handy way to run printer initialization commands or store settings that cannot be saved to EEPROM.

If you use octoprint to upload auto0.g to the SD card, it is renamed to auto0.gco

What did you expect to happen?

The file should be uploaded with the name provided.

What happened instead?

The file was renamed to auto0.gco

Branch & Commit or Version of OctoPrint

1.2.10

Printer model & used firmware incl. version

Mendel90, Marlin (an oldish version)

Browser and Version of Browser, Operating System running Browser

I have read the FAQ.
@foosel foosel added the bug Issue describes a bug label May 20, 2016
@foosel foosel added this to the 1.2.12 milestone May 20, 2016
foosel added a commit that referenced this issue Jun 1, 2016
@foosel
Whitelist .g extensions on sd file upload
30b6211 
That way uploading something like auto0.g will not
cause a rename to auto0.gco anymore.

Closes #1314
@foosel foosel added the done Done but not yet released label Jun 1, 2016
@foosel
Copy link
Member

foosel commented Jun 1, 2016

Fixed in maintenance and devel branches, will be part of the next release.

@foosel foosel closed this as completed Jun 1, 2016
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Issue describes a bug done Done but not yet released
Projects
None yet
Milestone
1.2.12
Development

No branches or pull requests
2 participants
@foosel @Lenbok