Respectfully, there are many errors and much damage that these hastily released updates caused. I already noted in my ticket that I do not have the database tools to restore the passwords that your upgrade script had corrupted. In an effort to give you a chance to mend this situation, I have invited you and invite you again to fix your mistake starting with me. I understand it represents a lot of work, but I have been contributing to this community and I would welcome some reciprocation for it. I can even gladly donate some money for your time even but all I ask is your help. Thanks!
Plus, as mentioned earlier, email passwords need to have a $ character in them in some cases. Has this been fixed and if so, is it safe to rerun the CyberPanel upgrade script to apply the fix?
No doubt you have contributions, but you do have to understand our contributions to the community as well.
Helping all our free users either via helpdesk or forums. Right now there is so much to do, that is why things are bit slow, but all the tickets and threads are pretty much answered along with bug fixes.
Totally understandable. Coming from a more traditional, business developer background, though, I have learned earlier on that whenever changes are introduced and proper validation is not guaranteed, I am the sole party who is responsible and culpable if I rushed a feature out which caused damage to the user’s data and configuration. I understand how many hours of unpaid work your current development paradigm has invested but that unfortunately still does not preclude you for the responsibility of proper validation and taking responsibility and recovering when the onus is on yourself, no matter how painful and time-consuming it is. It is a painful lesson in the school of hard knocks, to be sure, but everyone has to learn it early on or no one will take them seriously or trust in their work. Otherwise, if users see their data as written off as a casualty even when they have backups or other means that you could effectively restore or provide tools to restore, it sends the clear signal that you do not take their data seriously. Some solutions to avoid this pitfall include not being reactionary in tense critical security-related situations like this one and instead being proactive in order to avoid collateral damage and negative feedback. Just some food for thought.
Agreed and lesson learned. Though responded your ticket regarding how you can generate the password in crypt format through PHP.
I did! And not only that, but I also just finished a full, custom CyberPanel password changing plugin for Rainloop! I will be uploading it very soon now!
Done and done. I also initiated a pull request. So hopefully, it should be added very soon to the official Rainloop project. If this meets your approval team @CyberPanel, please let the Rainloop team know that they can go ahead and add it: