Hi,

Technically, what happen is, when your cursor leaves the permalink, it performs a check. This is binded to the event onBlur for the field. Which means it happens if you where to click any where outside of the permalink, then a check will get triggered and this is intended.

I understand a bit more on this after playing around a bit. So I'm curious why it checks upon leaving the field? It checks each time you change the value by saying it's available before leaving the field. Is the second check in case the user manipulates it some how? When using Firebug I could not see it in the DOM input element. Although perhaps it's being stored in a JS location hence making it possible to bypass the first check?

When hitting submit it does a check once again to ensure that nothing was changed. So in total it does 3 checks. I would think the third one would make the second one unneeded.

Hi,

Will remove onBlur in the next version to prevent the 2nd check.

Thanks Jason. The same should go for the main profile permalink and the username check. They too do the triple method.

@Josh, noted

Thanks Jason for fixing the permalink triple check. Note that editing a username however still does a triple check (the second one onBlur).

Hi,

I will see if I can squeeze that in but do understand that we are currently on full force with EasyBlog.

Understood. ES 1.3.14 can wait until EasyBlog 5 beta is released.

Thanks for understanding Josh. Hopefully 1.3.13 is stable enough to last us through then

I assume EB5 beta is still being worked on. Just giving a reminder to add the edit user check issue fix to the ES 1.3.14 release.

Thanks Josh