I was unable to reproduce the issue in a debug environment. But I couldn’t fix it in my own environment either. Solved my problem with a custom solution instead, so won’t be able to answer if this is a bug in the plugin or a side effect of something in our configuration (our configuration is quite vanilla, however).
