This is turning into a spectacular problem for us too, and we've advised against 6.1 too. MikroTik, could you please be more careful with changing your scripting API? Some people have constructed elaborate management systems around it and have to also try accommodate multiple ROS versions across hundreds of routers. Changes like these really hamper the stability of the ROS platform.Hi,
We have 2 problems with the Ros6.1 release.
importing rsc scripts has changed the calling structure and also the maximum characters per router script has been changed in Ros 6.1
The first problem is fixable with some work on rewriting the structure of the scripts, aka where we had to \\\ a " or $ it has to change to only 1x \.
The second problem we can also sort by breaking the scripts up into smaller scripts being called.
I do not see these changes in the change log, and wondered who else has experienced this problem?
We have advised our clients not to upgrade to Ros6.1 for the moment as we first need to rewrite our scripts and test it on the new version, as it currently breaks (fails) on importing the rsc script file.
Is this an error on Mikrotik's side or will things stay this way forward?
Any info welcome please.
So my first question, why does /import have to print script lines by default? Can you rather add a "debug=yes" or "verbose=yes" option to the import command, please? Reason being, we have scripts that are already perfectly verbose ala :put, so having ROS automatically print line numbers and commands creates an utter mess of the terminal output.
Secondly, please could you (MikroTik) explain exactly what other limitations have been imposed now, that Russian has observed? Right now all I see is scripts failing all over the network, and researching a fix will be much easier with an in-depth understanding of the changes you've made.