You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2021. It is now read-only.
Sorry, my issue was not clear (and i've made a little mistake in the "correct link").
It's perfectly right that the final url should have the encoded &, even if now HTML5 it's less strict on it.
But the scope (in my case and i think for many other users) is to use your plug-in for manipulating the code before using it in an Email Marketing Platform such as Mailup or Mailchimp. In these cases the code will be parsed by the internal converter that will encode the & of "&" once again, risking of breaking the tracking paramenter. Maybe for the future it could be interesting to have an option of enconding or not the &, depending on the final sending system.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using queryString option to create a Google Analytics link with utm parameters.
Premailer convert the & conjiunction with the entity, breaking the link monitoring.
The text was updated successfully, but these errors were encountered: