I just researched this and it is indeed a bug. The original querystring isn't being passed so the & is in the wrong location. I am working on a fix now.
Yes but it usually takes a little longer because I have to repackage it. I will probably be releasing v3.1.1 in a few days because their are a few other minor things that have poped up.