@KMVastro looking at the history that’s exactly what happened, we did a patch on a branch to get the fix out ASAP but forgot to merge the patch branch back into master. we’ll try and get a build out ASAP.
We’ve now deployed 2.11.1, which brings back these fixes (for good this time).
Sorry for the trouble folks.
I now running 2.11.1, and can confirm the issue has been resolved again. Good work!
