Support for extension dropped; new onboard function replaces extension functionality

English
#1

I have been using a Calc extension, XPysort, for several years in support of a user. Support for the extension has evidently been dropped, but a new onboard sort function effectively replaces it.

My problem is I have about 5 years of historical spreadsheets my user occasionally needs to access. If she tries to use the new version of Calc, these historical files won’t open correctly. She can use an older version, but then that older version cannot be used to build new sheets because the extension is not supported.

As we go forward, I can either try to maintain two versions of LO Calc for her and instruct her to use the correct one depending on the age of the file she wants to open, or I can go back in history and rewrite the files to use the new onboard function. Either of these approaches seems clunky, so I was wondering if the experts here had any advice for me.

Background of my experience can be found here.

Thanks very much for any advice

#2

In such situation, my recommendation is to try minimizing the workload.
Your solution to maintain two versions looks fine, if, most of the time, the old documents are used for reference only, not for update.
If, from time to time, an old document needs update, then I would recommend to update it in a way that it doesn’t require XPysort anymore.
I would use a clear naming convention by appending _old to the names of the old documents may help in the process.

1 Like
#3

If the extension issue cannot be resolved readily, you could parallel install an older version of LibreOffice just to work with the old extension while keeping a more modern version for other work. Installing several versions of LibreOffice in parallel - The Document Foundation Wiki

1 Like
#4

trying to sort out what the actual problem is, have to go down convoluted posts / bug report / zip / ods … :face_with_thermometer:
would be wise to narrow this down with the simplest possible example.
would make sense to add “python” as tag of this topic :wink:

would then first quantify it :wink:

which is how many files ?
calls to the failing python code ?
to be replaced by what ?

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.