Thanks for the report. On the 29th I ran into those same kind of problem(s) and posted an update and wrote in the changelog, except it wasn't because of another extension and I was able to isolate the problem; I haven't since been able to replicate it. I’ll keep an eye on it, and if we can narrow down the conflicting extension or exact reproduction steps, I can look at adding a protection for that case.

