Conversation Block - Error: Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary

madesimplemedia · February 20, 2025, 6:58pm

I’m getting this error when trying to submit using the Conversation block in v8.

We have the site set to use Turnstile as the captcha, I suspect this block isn’t loading it correctly?

JohntheFish · February 20, 2025, 7:43pm

Conversation block has issues with anything other than the default captcha.

github.com/concretecms/concretecms

reCaptcha v3 fails to load assets or allow post submission in conversations

opened 12:24PM - 28 Jul 23 UTC

losttheplot

Type:Bug Bug Priority:Medium Affects:Visitors Product Areas:Conversations Bug:Level of Effort:Low

### Affected Version of Concrete CMS 9.x ### Description With a fresh i…nstall of the 9.2.1 codebase, and the site correctly configured for Google reCaptcha v.3, the form added to the 'Contact Us' page displays a reCaptcha badge and passes the submit validation. However, a conversation block added to any page does not display the reCaptcha badge (with the user logged out) and submission of a message triggers the error: "Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary." Two recent forum posts refer to the same issue without a resolution: https://forums.concretecms.org/t/v9-2-and-recaptcha-display-problem/5844 https://forums.concretecms.org/t/using-recaptcha-v3-with-c5-v9-1-3/5732 ### How to reproduce Download fresh 9.2.1 codebase and install the Atomik version onto an apache server running php 8.1. Configure the site for Google reCaptcha v.3. Confirm that on the 'Contact Us' page, the reCaptcha badge is visible floating at the page foot, confirming that reCapture is enabled. Now visit a blog page and add a conversation block to that page. Log out and note that the reCaptcha badge is not displaying. Try to submit a message and note the error: "Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary." ### Possible Solution _No response_ ### Additional Context # Concrete Cache Settings Block Cache - Off Overrides Cache - Off Full Page Caching - Off Full Page Cache Lifetime - Only when manually removed or the cache is cleared. # Server Software Apache # Server API fpm-fcgi # PHP Version 8.1.21 # PHP Extensions bcmath, calendar, cgi-fcgi, Core, ctype, curl, date, dom, exif, FFI, fileinfo, filter, ftp, gd, gettext, hash, iconv, igbinary, imagick, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, Phar, posix, readline, redis, Reflection, session, shmop, SimpleXML, soap, sockets, sodium, SPL, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib # PHP Settings max_execution_time - 90 max_file_uploads - 20 max_input_nesting_level - 64 max_input_time - 300 max_input_vars - 5000 max_multipart_body_parts - -1 memory_limit - 2G post_max_size - 32M upload_max_filesize - 32M zend.exception_string_param_max_len - 0 ldap.max_links - Unlimited mbstring.regex_retry_limit - 1000000 mbstring.regex_stack_limit - 100000 mysqli.max_links - Unlimited mysqli.max_persistent - Unlimited pcre.backtrack_limit - 1000000 pcre.recursion_limit - 100000 redis.pconnect.connection_limit - 0 session.cache_limiter - no value session.gc_maxlifetime - 7200 soap.wsdl_cache_limit - 5 unserialize_max_depth - 4096 opcache.jit_bisect_limit - 0 opcache.jit_max_exit_counters - 8192 opcache.jit_max_loop_unrolls - 8 opcache.jit_max_polymorphic_calls - 2 opcache.jit_max_recursive_calls - 2 opcache.jit_max_recursive_returns - 2 opcache.jit_max_root_traces - 1024 opcache.jit_max_side_traces - 128 opcache.max_accelerated_files - 10000 opcache.max_file_size - 0 opcache.max_wasted_percentage - 5 Redis is not being used due to multiple runtime issues.

The same applies to any other JS based captcha.

No permanent fix announced as-yet.

madesimplemedia · February 21, 2025, 8:48am

Thanks John, that is a shame, but I guess it’s not that widely used.

mhawke · February 21, 2025, 7:47pm

Chicken and egg issue. Perhaps it’s not used much cuz it’s busted!

JohntheFish · February 21, 2025, 8:00pm

I am sure you are both right. The bug/limitation will have been around since day zero for conversations. I came across the details from a post in the old forums.

madesimplemedia · February 28, 2025, 9:42am

I actually think that comments should be part of a wider marketing platform, and this goes beyond what Concrete aims to provide. Disqus is terrible, it really could have been a great way of providing comments, but also a wider engagement platform like Medium to drive traffic to users websites too. I’m going a bit off topic, but I feel like Concrete CMS comments for public users probably aren’t a great option anyway, we need another platform that can do so much more.