benant

Hello, Tahmid.

I had the same problem.
Experience has shown a similar phenomenon in URI encoding with Korean.
So, not my plugin, but I checked Ajaxify’s history.js file.
As a result, I modified it as shown below, and the problem was solved in Korean.
Try it once.

m.unescapeString = function (b) {
	var c = b,
	d;
	for (; ; ) {
		// d = a.unescape(c);
		d = a.decodeURIComponent(c);
		if (d === c)
			break;
		c = d
	}
	return c
},

* reference : https://docs.microsoft.com/en-us/scripting/javascript/reference/unescape-function-javascript
* reference : https://docs.microsoft.com/en-us/scripting/javascript/reference/decodeuricomponent-function-javascript

ps: If Ajaxfy developers see this article, please reflect them in the source.

Hi. jessekramer27
Please, simply explain … How did you fix it?

• This reply was modified 9 years, 9 months ago by benant.