Thanks! This will be fixed in the next bugfix update (probably coming later today)
thank you :) it really seems to be fixed in 0.4.26g *yay*
