User committed a fix to 5.3.x. Commit Message:

Fixes - Use "http_build_query" to escape url parameters

Dmitry will test all together later.

Changes required to custom-code after this task is commited:

1. __URLENCODE__ parameter is no longer supported by (use no_amp parameter instead):

   • kApplication::HREF method

   • m_Link, m_t tags or they derivatives

2. no_amp parameter is now only supported in (only use in tags alongside with js_escape parameter):

   • m_Link, m_t tags or they derivatives

3. escape parameter is no longer supported by (use js_escape parameter instead):

   • kApplication::HREF method

   • m_Link, m_t tags or they derivatives

P.S.

If you see no_amp or __URLENCODE__ parameter in resulting url, then see a solution proposed above.

An interesting side effect, after implementing proposed idea, popped up: "\" is encoded as %5C automatically resulting in 100% valid url escaped for usage in JavaScript without a need to pass js_escape="1" to <inp2:m_Link .../> tag.

Before single slash ("\") was left as is and using js_escape="1" parameter converted it to double slashes.

Migrating issues to new workflow.