Just updated to Ver. 3.1.0, and happy to report both issues have been fixed. Not sure if they were already being worked on or if one of the developers saw that message while working on Ver. 3.1.0, but doesn’t really matter I guess.
Thanks for the fixes!