Cura Backup Plugin - Cura version issue

[flowalistik 180]

Hi everyone!

 

Today I got a new laptop, and it was time for me to backup and restore all my printers and profiles. While doing it, I ran into a frustrating issue, which affects the user experience. Here's what happened and how I solved it:

 

• Old laptop with Cura 3.4.1 installed. I have many machines and profiles, all backed up.
• New laptop has Cura 3.5.1, and no machines and profiles yet.
• I download Cura Backup in the new laptop, I log in and try to restore the backup, only to find the following message:

 

 

Yes, it's frustrating to get this message, as I can imagine it will be quite common to get a new laptop and download the latest version of Cura, while you may still be using an older version. And yes, I still use Cura 15.04. I tried to download Cura 3.4.1 in my new laptop, but for some reason, the toolbox didn't load all the plugins, including Cura Backup.

 

This is how I solved it:

 

• Downloaded and installed Cura 3.5.1 in my old laptop, which already has Cura 3.4.1.
• Download de Cura Backup plugin in my old laptop (Cura 3.5.1) and backup everything. It's literally the same backup I created in Cura 3.4.1, but hey, the Cura Backup plugin can be quite picky.
• Open Cura 3.5.1 in my new laptop and restore the new backup made with Cura 3.5.1.

 

This can be a slow method, as having multiple Cura versions in the same laptop can mess a little bit with the profiles and it's confusing, but until it's fixed, it should work!

 

Message to Cura devs: we really appreciate how much love you put into Cura, but please, allow us to restore backups made using different Cura versions. A partial solution should be a disclaimer that warned us that restoring backups made in different Cura versions may cause a black hole! 

[nallath 637]

I just looked at the code and it was explicitly set to behave this way. Why this was done, I don't know, as Cura should be perfectly able to restore older data, since it has upgrade scripts.

 

I will investigate a bit more to figure out why it's configured this way (and if there is no reason for it, change it)