By Klaus Kroenert on Friday, 09 March 2018
Posted in Technical Issues
Replies 19
Likes 0
Views 1.5K
Votes 0
Hello,

after the last Komento Update (V 3.0.12 ) on Joomla (3.8.4 german) the Google ReChapta didnt work.
We get a Error (chapta not posible DE: Falsche Captcha Eingabe)
As attachment, i send you to Files, that was a fixed you wrote us in history, that we have this issue on older Komento version. Did this files fix again?
·
Friday, 09 March 2018 00:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Klaus,

I tried using google Recaptcha on Komento and it's working fine(http://take.ms/0Tzfe).

Am I missing something here?
·
Friday, 09 March 2018 10:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Raymond,

end then if you press "send comment" you get an error. Se attached picture
·
Friday, 09 March 2018 10:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Klaus,

Looks like I'm not able to load your ftp directory in FileZilla so I used extplorer in the backend to investigate.

The following is the error message that I received when getting curl response(http://take.ms/MY4Ps).

Regarding the error, you can refer to these 2 links, which suggest that error is due to a permission issue while trying to access the file
https://curl.haxx.se/mail/curlphp-2005-11/0038.html
http://chrisschuld.com/2008/07/how-to-fix-the-curl-error-error-setting-certificate-verify-locations/

You should consult your hosting provider about this permission issue and show them the screenshot and links that I provided for reference.

For now, you can disable this option in recaptcha settings first since the SSL option is hitting that permission issue on the server: http://take.ms/kzjDU
·
Friday, 09 March 2018 16:25
·
0 Likes
·
0 Votes
·
0 Comments
·
I have similar issues with Komento V3.0.12 which started with that version upgrade.

Can you check if you maybe have something like:

/www_run/components/com_komento/themes/wireframe/comment
If yes rename the folder to:
/www_run/components/com_komento/themes/wireframe/comment_OLD

and

www_run/templates/<YourTemplate>/html/com_komento
if yes rename that to:
www_run/templates/<YourTemplate>/html/com_komento_NoLongerWorking

This solved the issue for me, however this isn´t a solution for me (more here) but maybe for you...
·
Monday, 12 March 2018 22:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for sharing!
·
Monday, 12 March 2018 22:33
·
0 Likes
·
0 Votes
·
0 Comments
·
suggest that error is due to a permission issue


Hello Raymond,

no isn't a permission issue. Did we set "everyone full control" we have the same issue.
The issue exist after Komento update!!! So thing, Komento have made changes, that generated compatibility issues on IIS.

Now, we need a solution from KOMENTO
·
Friday, 16 March 2018 00:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Tela Performance,

thanks, but this didn't solve the issue
·
Friday, 16 March 2018 00:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Klaus,

I tried using google Recaptcha on Komento and it's working fine(http://take.ms/0Tzfe).

Am I missing something here?


@Ramond,

in my first post, i ask, if the attached fix (i get it from KOMENTO at Sept 2017) will be fixed this issue in the last KOMENTO Version. About my question i get no answer

Now we test the Fix on last KOMENTO Version and it works

So, that is confirm, that we have no permission issue, thats only a KOMENTO issue.
I hope, that the dev-team will be implemented this fix in future versions.

It does not help anyone if an error analysis confuses the user. Especially when the indication comes that the error has already appeared in earlier versions and KOMENTO has created a fix for it. Since then you have to ask yourself, why KOMENTO does not implement this fix and the customer is referenced with a wrong analysis on a wrong possible error.

Kind Regards
Klaus
·
Friday, 16 March 2018 00:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Klaus,

My apologies as I forgot to mention that the fix that you mentioned in the beginning is actually forcefully disabling this SSL setting under Recaptcha settings(http://take.ms/A1Uyz).

This is why it works for you. I did mention in my previous reply that disabling this option should allow the recaptcha to work. But this is just a workaround and does not solve the error when SSL setting is enabled(http://take.ms/MY4Ps).
·
Friday, 16 March 2018 11:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello to Stackideas support Team,
i have exactly the same issue here. Joomla 3.8.8 with SSL , Komento 3.0.12, Recaptcha Version 2.0

My contact form in joomla is working fine with recaptcha. But Komento gives me exactly the same trouble as mentioned above.

Is there something new about this?
·
Tuesday, 19 June 2018 03:11
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello to Stackideas support Team,
i have exactly the same issue here. Joomla 3.8.8 with SSL , Komento 3.0.12, Recaptcha Version 2.0

My contact form in joomla is working fine with recaptcha. But Komento gives me exactly the same trouble as mentioned above.

Is there something new about this?


- i use a fix that KOMENTO team wrote me for an older version and this work. Hope the Support can send you the same fix.
·
Tuesday, 19 June 2018 09:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Frank,

I already replied this on your new thread https://stackideas.com/forums/i-can-t-post-a-comment-recaptcha-issue , please have a check.
·
Tuesday, 19 June 2018 09:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex, your Link, you send has an Error: "Sorry, but the post that you are trying to access is not available. "
·
Tuesday, 19 June 2018 10:04
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Klaus,

Frank's thread was on a incorrect category so I have moved it to Komento. Frank should be able to access it now.

However, it is a private thread so you will not be able to access it.
·
Tuesday, 19 June 2018 10:38
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Arlex, your Link, you send has an Error: "Sorry, but the post that you are trying to access is not available. "


Sorry Klaus,
I had previously made a request here in the forum, but immediately opened a private ticket to speed up the process.

I was responsible for the error described.

It was actually a conflict with Google's recaptcha.
I had already created a reCaptcha key for this homepage the year before and had not named it correctly.
So I didn't notice that there was another one. I deleted the old key and checked the entries again.

Now it works the way it's supposed to.

Thank you for your attention.
Cheers Frank
·
Tuesday, 19 June 2018 15:13
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating us on your issue Frank.

Regards.
·
Tuesday, 19 June 2018 17:39
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post