@ Mark
Thanks! I noticed I made this error the other day shortly after releasing 8.2.5. This is fixed and will be in the 8.2.6 bugfix release scheduled for this weekend.
Apologies for the error!
