For the love god, PLEASE STOP with the CAPTCHA.

Post Reply New Topic

Yep, thats the same problem I'm having. I wish somebody would fix this.

CAPTCHA should be used only for registering, not for every posting.

Unfortunately it is close to impossible to deal with.

Last edited by Max000 on 14 Jul 2013, 10:24 pm, edited 1 time in total.

Maybe it's all of those frowny-faces ... ?

Interesting theory, but it's happening on postings without the frowny-faces too.

Oh my god... yes, please... for the love of all that is unholy STOP with all the poxy Captcha checks.
I never had this until today, but all day... ever single time I try to post, preview or even edit typos in a post.... captcha, captcha, captcha.....
I realise I'm not exactly standard as humans go, but I absolutely assure you that I am one.


I wouldn't mind but that on top of the usual glitchiness of WP is winding me up now.... either WP can't cope with smiley data in the message (even ones with NO smilies in them) , it can't get 'topic watch information', it's overloaded with messages and conks out completely, or it's bombarding me with captcha messages.

It will probably do it again when I post this !

Oh my god... yes, please... for the love of all that is unholy STOP with all the poxy Captcha checks.
I never had this until today, but all day... ever single time I try to post, preview or even edit typos in a post.... captcha, captcha, captcha.....
I realise I'm not exactly standard as humans go, but I absolutely assure you that I am one.


I wouldn't mind but that on top of the usual glitchiness of WP is winding me up now.... either WP can't cope with smiley data in the message (even ones with NO smilies in them) , it can't get 'topic watch information', it's overloaded with messages and conks out completely, or it's bombarding me with captcha messages.

It will probably do it again when I post this !



ETA : oh for the love of.... yes it has.
"can't optain topic watch information"

.. except that it posted my first message anyway and never told me.
Well, I'm not deleting it because it will just captcha me again and it seems to be letting me post messages just now without having to do them.

I wouldn't mind if it was an actual CAPTCHA and once you entered it your post would post, but what keeps happening for me is they tell me I have to "enter the above text" but the page is totally blank. There IS no "above text" to enter. So there is literally nothing I can do.

Yeah, right now its a bit annoying.

Maybe all of those lines in your signature?

Yeah, I'm taking random guesses, and mainly because I rarely encounter a Captcha screen on this website.

This is unrelated to CAPTCHA - it's an intermittent bug with the forum software itself and if you've previously posted to a thread, nothing happens and the error can be ignored.
If it's the first time you've posted to a thread then the normal function of activating a watch on that topic for replies won't happen. If this is important to you then you will need to go to the first page of the topic and click on the "Watch this topic for replies" link at the foot of the page to manually activate it.
(but I see that you have the "Always notify me of replies" option disabled in your profile, therefore the error about obtaining watch information can be ignored)

There is something to investigate, though: see here, in your other thread:
http://www.wrongplanet.net/postt235211.html

Thankyou for your informative reply.

Would you be able to explain why I keep getting "error in posting" responses coming up sometimes when I try to make posts ?

Or why WP keeps protesting about being unable to process the smiley data in my posts even when there aren't any smilies ?

UGh yeah i have been getting them too.

No signature. Hardly ever use smilies. Mine might be because my internet is purely on my phone? I don't know.

The smilies error can still appear even when there are none in a post - 'something' goes wrong in the background, while preparing the post, and that seems to be a pretty meaningless error the forum software coughs up as a result. I don't think I've ever seen this error unless I'm including an image in the post, though.
If, in desperation, the "Disable Smilies in this post" checkbox is checked, it's still hit and miss whether it will now succeed - it can sometimes work after doing this, but more often it simply fails with another error instead.

The best way to "test the waters" is to click the "Preview" button, whether images are included or not.
Any problems likely to cause an "error in posting" failure when submitting will surface then, plus it's an ideal chance to spot those text formatting or spelling errors. Although... sometimes, despite successfully previewing a post, submitting it can still cause the "error in posting" message - but in those cases, retrying the submission normally succeeds.
When no images are included this error appears to be very rare, and I can't think of any case during my own postings when it has appeared that a single retry hasn't then succeeded.

But when images are included and a preview generates the smilies error, it is sometimes worth trying the preview a few more times and if it succeeds, submitting the image immediately will also usually succeed. But if the preview never succeeds... well, it's a case of not including the image or trying another one from a different source - and it is source-related in some way: I have never had this error when posting images sourced through Wikipedia, for example.

@CheredIsTyping - no, this one is caused entirely by problems with the forum software. It's something about they way in which it processes a post in preparation for display (preview or post) that causes the error.

My solution so far for the CAPTCHA crap I get on google chrome:

Copy the text from the reply box to the clipboard -> open firefox -> login to wrongplanet -> go to the same thread -> reply -> paste the text into the reply box -> post -> log off -> go back to chrome.

In other words, try posting the same message using another browser.

Um, that seems like a lot of work to go through. Especially when there is no guarantee that it will work in the other browser either.

But thanks for the suggestion. Maybe I'll try a different browser, the next time it happens.