Board Thread:Technical Updates/@comment-24006128-20200319160218/@comment-9605025-20200321005918

Again, just to clarify (since I don't think this is clear in Himmalerin's post), the prefix parameter works fine for what it is supposed to do. The issue is that, when prefix and preloadparams[] are used together, preloadparams[] gets encoded differently in the URL query string. For some reason, UCP can't handle this different encoding.

I find it odd that they would have this in the extension. If it was a mistake, it seems odd that the fix would be to recognize the different encoding rather than fix the encoding error.