@Takashi the current version doesn't have that problem, Marcus reports a warning during the update from 4.7.1 to 4.8.0 which I could reproduce, but I don't know what to do about it. Actually I don't even understand the implications, that's why I'm throwing my hands in the air.