NYInstallers Posted December 21, 2022 Posted December 21, 2022 Just took over a new client with a system roughly on 2.6. I connected using a new version of composer and it started to throw all kinds of errors. is there a way to manage this system keeping It on the existing OS with the new version of composer 3.1? if so, are those errors ignorable? Or will I mess something up by making changes? How do I safely make changes and backups of the system? thanks Quote
msgreenf Posted December 21, 2022 Posted December 21, 2022 no, you need to use the same version of composer or upgrade. there is KB article with legacy versions of composer. Quote
NYInstallers Posted December 21, 2022 Author Posted December 21, 2022 Thank you. I will take a look Quote
Cyknight Posted December 21, 2022 Posted December 21, 2022 To be clear - OS3 up you have one composer with 'packages' for each version (it'll download on demand as needed) - pre 3.0 you'll need a (near) matching version (ie as an installer, you should have 2.10.6, 2.9.1, 2.6 and probably 2.5.3 installed - those will catch 99% of pre 3.0 systems. Quote
NYInstallers Posted December 23, 2022 Author Posted December 23, 2022 Thanks for all the help. I found it. msgreenf 1 Quote
Amr Posted January 1, 2023 Posted January 1, 2023 On 12/23/2022 at 2:59 PM, NYInstallers said: Thanks for all the help. I found it. Actually if the system can take it try to get them to 2.9.1 or better 2.10.6 if they are sticking with OS2 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.