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

Fix missing setting_version after translation #2450

Closed
wants to merge 1 commit into from
Closed

Fix missing setting_version after translation #2450

wants to merge 1 commit into from

Conversation

ClemaX
Copy link

@ClemaX ClemaX commented Sep 18, 2017

Resolves #2117.
0f5814e implemented a check against the "setting_version" metadata when importing profiles. Legacy profile translation does not add this entry, which leads to Cura failing to import the translated profile.

Resolves #2117.
A recent change implemented a check against the "setting_version" metadata when importing profiles. Legacy profiles translation does not add this entry, which leads to Cura failing to import the translated profile.
@nallath nallath requested a review from Ghostkeeper September 19, 2017 07:54
@Ghostkeeper
Copy link
Collaborator

This is not the desired solution. You may say that the settings are at version 2, but they aren't. They need to be upgraded to version 2 first. The legacy profile importer imports the profiles to the format they were in at Cura 2.1, but settings have been deleted since then, and renamed, and have their units changed. This is the reason for checking against the setting version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants