[@angrygerman Participant 10 years, 4 months ago]

Actually – nevermind this one. Turns out this issue was caused by a different plug-in.

Problem resolved.