mettadas

You understood correctly, and it seems I have learned something. I’ve never seen (ampersand)amp; in an url before and in many years of coding have never generated such an url. But it seems to work. I guess this changed with xhtml?

Damn. The forum software ate my example even in a CODE block. The second line should read (sort of)

https://example.com/path/to/page?param1=value1(ampersand)amp;param2=value2(ampersand)amp;param3=value3

with (ampersand) replaced by an actual ampersand. My point is that the amp; should not be there.

And more generally, if the plugin is inserting HTML that I have configured it to insert, why would it not insert it exactly as I’ve asked it to? I can see the point of encoding values that the user entered into the pop up form, but surely the configured code should be left as entered, no?

No, it is not, when you want to use it to separate GET parameters. The correct format is

https://example.com/path/to/page?param1=value1&param2=value2&param3=value3

Look in your browser at any url that includes GET parameters. You will never see this:

https://example.com/path/to/page?param1=value1&param2=value2&param3=value3

But this plugin turns the first, correct form into the mangled second form.

Wish this forum had a preview … I wasn’t sure if my html would be interpreted or not. It was.

What I tried to say above is that an ampersand will be replaced by {ampersand}amp;, which breaks the URL.