Contact us not working in V18.2.2

[Buzby]

We have just realised that the contact us page is going to an internal 500 error when the submit button is pressed.

Host-it have been looking into this as it was thought to be a server issue, however they are saying that V18.2.2 does not have an active contact us page in the latest version, instead just having a page of contact details.

They are advising I either update the code to work on the new version, or change over to the current version of a static page of contact details.

Can anyone confirm what is standard in the new version so that I can look into what the issue is, and of course rectify.

I will open a ticket with support in the morning when I have more info.

[John Ennals]

It might be worth checking that ReCAPTCHA is enabled and your keys are still set up in Site Options | Properties. If they're not, I believe the Contact Us page will just appear as a static page of contact details.

John

[Buzby]

Hi John,

All that side of it is fine and working. It is after you press the submit button that it goes to a 500 error.

This is across 5 websites, same issues.

I'm sure its a hosting issue, but Host-it say they can't do any more.

Have tried 5 websites across 3 copies of Sellerdeck on 3 computers and get the same 500 error.

[Goz]

I've just tested my 18.2.2 sites - the contact forms are working fine. All hosted with 20i

[Goz]

If one of your websites is titanjewellery then I've just sent you a test message through your contact form (if not then apologies to the owner )

[Buzby]

If one of your websites is titanjewellery then I've just sent you a test message through your contact form (if not then apologies to the owner )

Hi Goz, it is indeed, many thanks.

After John’s post yesterday I looked more at the captcha. All looked ok with it, keys were fine, but if I turned it off then the email works ok.

so as of last night all sites are working fine with the capture turned off. Something to investigate.

[zgap111]

I'm having this problem too... I'm also with host-it
Any progress?
Disabling RECAPTCHA v2 = works, but now getting lots of SPAM... (also had SPAM when v2 was working, but not so much)
Checked the v2 keys = v2 on = goes to 500 Error
(I even tried v3)

I've also raised a ticket with host-it... but... this was working in v18.0.6... since updating to v18.2.2 it doesn't, is it really a hosting issue?

Searching Release Notes has 1 mention of "recaptcha"
v18.2.0 : Recaptcha is now verified correctly, SD-8370

[zgap111]

host-it advised:

This appears to be a script error, it seems you are missing a file server.svg? I cannot find it in the cgi-bin directory.

I can't find this file " server.svg " either...

[Goz]

This appears to be a script error, it seems you are missing a file server.svg? I cannot find it in the cgi-bin directory.

The only items in the cgi-bin are Sellerdeck Perl scripts. My websites don't have a file anywhere named server.svg - I've never seen a SD file with this name.

I am on 18.2.2 and have Recaptcha switched on. My contact form works perfectly fine on all my own sites.

I run a hosting company specialising in Sellerdeck..... in my opinion, this is a hosting issue. Ask them

I'm not using Swift though... are you?

[Buzby]

I'm having this problem too... I'm also with host-it
Any progress?
Disabling RECAPTCHA v2 = works, but now getting lots of SPAM... (also had SPAM when v2 was working, but not so much)
Checked the v2 keys = v2 on = goes to 500 Error
(I even tried v3)

I've also raised a ticket with host-it... but... this was working in v18.0.6... since updating to v18.2.2 it doesn't, is it really a hosting issue?

Searching Release Notes has 1 mention of "recaptcha"
v18.2.0 : Recaptcha is now verified correctly, SD-8370

I’m no closer to resolving this.

I have an open ticket with Host-it, after them saying they have had no other reports of this issue I have just updated my ticket advising of your report of the same issue.

I am getting so much spam with the captcha turned off it is ridiculous. 1 particular email we get every minute. We do have to resolve this, or change hosts which would be a shame.

[zgap111]

We're not using Swift

I checked the logs myself, and I noticed one of the sites does not show the "server.svg" file error.
I tried sending messages today and both sites do not have that "server.svg" error,
logs only shows the first error :
site1 : End of script output before headers: mf000003.pl
site2 : End of script output before headers: mf000042.pl

[Buzby]

We have a mixture of Swift and non swift sites. All have the same issue.

[Buzby]

The latest from Host-it

Hi Jason,

I've manually added a little bit of debugging on the "mf000001.pl" by adding the line use CGI::Carp 'fatalsToBrowser'; close to the top, which will output any errors to the browser window. Upon doing this, it now returns the follow when the form is submitted, and the CAPTCHA is completed.

Software error: Operation "==": no method found, left argument in overloaded package JSON::PP::Boolean, right argument has no overloaded magic at mf000001.pl line 278.
Looking at line 278 in the file this is..
if ($JsonResponse->{'success'} == $::TRUE)

It's basically complaining about the syntax of ==. If I change this to ```if ($JsonResponse->{'success'} eq $::TRUE)`` as a test, it appears to work.

This is certainly a code issue, perhaps the CAPTCHA code is not compatible with later version of perl, or one of it's modules, and this is causing the error. I'm not sure where the perl CAPTCHA code is originally from, but it may be worth looking if a newer version is available.

I've left it in place with the original ==, and the error display so you can see this yourself. Unfortunately there's no way I can make this a permenant change, or resolve it permenantely from the server-side as the Sellerdeck software will no doubt overwrite the file on next update.

Many thanks

Jon
Host-IT Support

[gcamley]

Your fix was almost correct. The line should read: -

if ($JsonResponse->{'success'} eq 'true')

[zgap111]

I uploaded v1806 and it works...
then uploaded v1822 and it errors 500...

see attached image of comparing the files for mf*.pl

seeing the last two posts about the "=="
there are more than one "==" seen in the image

- searching I found this :

The eq operator in Perl tests for string equality, while the == tests for numerical equality only.

I guess the ==1 works and the others with TRUE / FALSE / FAILURE are not numerical and would fail?

how do we amend if upload changes it back to default?