@laurenshof @melroy it should be fixed in the next release and/or you could use the NodeInfo plugin, that should fix it immediately.

@pfefferle @melroy cool, no rush, next post comes out only in 9 days anyway so should be fine

thanks for quick fix matthias!