For the benefit to other members reading this thread.
- I emailed TIG one of my for purchase ruby scripts in .zip format
- We both agreed that indeed when renamed to .rbz the SU 2016 Extension Manager failed to install the script.
to quote TIG: "As to why there are some issues with some of your ZIP/RBZ files is a mystery..."
Coincidentally SU 2016 Extension Manager also fails to install all of the other for purchase ruby scripts. This situation came to light when one of my Clients informed me that my scripts do not work in SU 2016. That's the reason I started this thread.
I also warned clients not to use my scripts for SU 2016 on my blog.
Manual installation, without the use of Extension Manager in SU 2015 ....works!
Hence loading the file in the Ruby Console also ....works!
Manual installation, without the use of Extension Manager in SU 2016 .....fails!
Hence loading the file in the Ruby Console also ....fails!
So now you have the problem you can no longer write or edit an .rb files the way you did with past version of SU 2015 and earlier.
- If you have to convert the .rb to .rbz first, then try to install in into SU 2016
and if that install fails, You wont be able to read any Ruby script errors in the Ruby Console.....So now what!
If you still have SU 2015 installed, stay with that version, and you wont have any install problems.