I was a bit to quick with v3.0.0.2 and had to do one more update to fix this properly. Look here for the change log: Sorry for the inconvenience, Alexander