Yesterday there was here a message about that coming update, with releasenotes that made sense to me. Of course that message was deleted here because it is not official at this moment, but I expect to see it monday or tuesday, as the most updates and new versions untill now came out officially.😁
There has been no update 387 announced for VP17. Ian, where are you hearing this? Grazie, that is VP15.
My friend told me. Wait offical release note.
Former user
wrote on 12/14/2019, 7:37 AM
Every message i've posted here has been deleted. I would like an explanation please, and if on review of the messages I posted it's found I did nothing wrong, I'd like the moderator responsible to be reprimanded. You may say I exposed a security problem with Magix, and if I did, don't you want to learn from that instead of censoring me and keep doing the same insecure things. I spend 15minutes to research and test this issue, before contributing here, to then rudely have my messages deleted without explanation.
Do this again, and I"m done beta testing your software for free Magix
Bob-h, the explantation is quite simple - a new build has not be launched yet. Not so hard to understand I think. Wait for the official launch please and everything should be fine with the language versions.
There has been no update 387 announced for VP17. Ian, where are you hearing this? Grazie, that is VP15.
My friend told me. Wait offical release note
Every message i've posted here has been deleted. I would like an explanation please, and if on review of the messages I posted it's found I did nothing wrong, I'd like the moderator responsible to be reprimanded. You may say I exposed a security problem with Magix, and if I did, don't you want to learn from that instead of censoring me and keep doing the same insecure things. I spend 15minutes to research and test this issue, before contributing here, to then rudely have my messages deleted without explanation.
Do this again, and I"m done beta testing your software for free Magix
If you post things that have not been authorized to be released, you're violating NDA (assuming you actually are a tester) regardless of how you found the information, and risk being removed as a tester anyway. If you did find a way to access protected information pre-release, the proper way to go about it would be to notify one of the development staff of the issue, not to post your findings publicly for all to see.