Loading
Issues With Publishing Articles ...
Just a brief article prompted by some comments I've seen people posting regarding difficulties in publishing articles.

It seems that certain users, most recently Shine&Sparkle have been able to start writing articles, but not been able to publish them as they are being asked for a security code, which it appears means nothing to anyone - not even the IMA.

So, I set about investigating it and created a free test account simply for that purpose and here's what I found.

The first screenshot below shows the problem people have been experiencing and I've highlighted the reference to the security code.

Whereas the second screenshot shows what happens when they attempt to publish their article - again I've highlighted the reference to the security code, which has now changed slightly from earlier.

As you can see, when they are preparing their article the text tells them to Retype this code here whereas once they try to publish the article they're told that The security code is incorrect and so the 'loop' continues.

This has led people to think that it might be a bug, and I speculated it might be to do with restrictions on free accounts, but as I've now found out it's actually related to which browser you are using.

The above screenshots were taken when I was logged into my free test account and using Internet Explorer. However, when I logged into that same account using Google Chrome as my browser things were quite different as you can see from this next screenshot.

As you can see, beneath the text that tells you to Retype this code here there now appears a reCAPTCHA box, which many of you will have come across on other sites. Simply tick/check the I'm not a robot box and then answer the questions that follow. Once the system software is satisfied that you are indeed not a robot you will be able to either publish your article or save it as a draft to work on and/or publish at a later date.

So, the problem is that for whatever reason the reCAPTCHA section and the questions that follow are not being displayed to people using Internet Explorer which is why they are unable to do what they're being instructed to do.

Now whether this means that Internet Explorer has a problem with reCAPTCHA or it's that the coding within ipernity isn't correct I'm afraid I can't say, but at least what I've discovered goes someway to explaining why some people are having difficulties publishing their articles.

In closing it's worth pointing out that this problem as I've encountered it only relates to free account holders. There is no request for Club members to go through the reCAPTCHA process on either of the two browsers I ran this test on.

So, until such time as the IMA are able to fix the glitch or offer more advice to users I recommend that if you have a free account and you want to publish an article then you need to avoid using Internet Explorer.

If you use Google Chrome (or possibly some other browsers that I didn't test) then you shouldn't have any problems in publishing articles.

Of course the best way to avoid such issues entirely would be to take out a Club membership, but I appreciate that at this moment in time not everyone feels comfortable doing that.

6 comments

HappySnapper said:

Has not been a problem for me Paul, just to say I admire your diligence to see this through.
4 years ago

StoneRoad2013 said:

Thanks for this research, Paul. I'll pass it on.
I wondered if it might be something related to non-club accounts, but the browser issue wasn't included my initial thoughts.
4 years ago

William Sutherland said:

Thank you for this info Paul!
4 years ago

Sami Serola (inactiv… said:

Very useful test and report, Paul. I don't understand why this Captcha check is shown only to some users. Our (ima team) test account does not show it. And something should be done to either disable it or make the check work on all browsers.
4 years ago

Pam J said:

Well Done Paul !
4 years ago ( translate )

Andy Rodker said:

Excellent detective work, Paul - and succinctly explained. Thank you!
4 years ago ( translate )