![]() Mikrotik, this is a matter of utmost importance!Īgreed, breaking functionality is a huge no-no. Otherwise, Mikrotik runs the risk of introducing yet another showstopper that makes it even harder upgrading to v7. IMO, the current implementation is ill-conceived, particularly considering that there are much smoother ways to resolve it while still preserving strict compatibility.īottom line Mikrotik must really make every effort to prevent compatibility issues in future releases. It may not be a significant concern for a garage-based company full of hacker heros, but for a serious corporation with a large installation base, it might have a profound impact. NO, it's better to "fix" the scripts (very easy) than revert to the previous shitty formatīreaking script compatibility in the middle of a major revision is not a trivial task and should be taken very seriously. So that they are compatible with this change. In the next few days I am editing all my scripts posted here: Not only on, but on every other places where date is usedĪ small price to pay for doing things right. Hopefully it's a right step in the direction of standardizing all dates in ISO format even within LOG and other places where the date is misspelled.Īll old scripts containing will stop working properly from v7.10+ ![]() THIS IS NECESSARY AND HAD TO BE DONE BEFORE, (and probably all other points where can be retrieved one date, like on /log, /certificate, /system scheduler, address-list entry creation-time, etc.) ![]() The new RouterOS v7.10+ changes the date reported by from may/10/2023 to the correct ISO format. WARNING: RouterOS v7.10+ will break all scripts based on or other date(s) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |