Customers can't create accounts after installing Recaptcha.

[Dungeonstone]

I installed Recaptcha a few weeks ago and everything was working fine through last Friday (the last time a new account was created) but suddenly today I am getting emails from customers stating that they can't create accounts.

I tried it myself and now once the "My account information" is filled out and ReCaptcha is checked the page just refreshes back to the (filled out) form rather than processing and creating the account.

I've tried enabling and disabling most of the fields in the form but the problem persists even when all that is required is the name, email address and password.

I've checked with my hosting service and they say that nothing was changed on their side over the weekend.

www.dungeonstone.com

[dbltoe]

I would recheck with bluehost to make sure they didn't drop your ancient PHP.

Most hosts are dropping PHP 5.6

and 1.3.9h Zen Cart has problems with 5.4.

Really is time to upgrade.

[Dungeonstone]

I've tracked down the issue.

It looks like the line..

$zco_notifier->notify('NOTIFY_CREATE_ACCOUNT_CAPTCHA_CHECK');

In : /includes/modules/YOUR_TEMPLATE/create_account.php

...is causing the glitch because the account system will process new accounts correctly once that line has been deleted.

Which makes me think that my site is either not processing or not receiving the confirmation from Google as to the ReCaptcha verification.

Of course that means that the Recaptcha system is also rendered ineffective with that line removed.

[dbltoe]

In : /includes/modules/YOUR_TEMPLATE/create_account.php

Unless you have that file and its buddies in darkness2 templlate folder, it ain't gonna work.

[Dungeonstone]

It's in darkness2.

/includes/modules/darkness2/create_account.php

I was just quick copying the folder information from the instruction file.

[DrByte]

I'm pretty sure that the ancient v1.3.9 doesn't have all the support for notifier/observer code in it the way recent versions do.
It's quite possible that if you've retrofitted your old version with parts and pieces that rely on the newer features of the notifier/observer functionality but haven't fully implemented all the ways it has been updated, but are using a plugin that depends on those features ... then it feels reasonable that you're triggering errors due to missing functionality that the plugin depends on.

Perhaps debug logs may reveal some PHP errors that are being triggered? Worth checking.

[lat9]

Perhaps debug logs may reveal some PHP errors that are being triggered? Worth checking.

Debug logging in v1.3.9 was pretty rudimentary. Be sure to look in the site's /cache directory, since the /logs directory didn't come into being until v1.5.1.

[Dungeonstone]

There are no recent debug logs.

I've also looked in the Cache directory.

There have been no new files created there in over three years. The ones from 2016-2017 are regarding problems related to a PHP board that I used to run that on my site I have since deleted.

[mc12345678]

There are no recent debug logs.

I've also looked in the Cache directory.

There have been no new files created there in over three years. The ones from 2016-2017 are regarding problems related to a PHP board that I used to run that on my site I have since deleted.

Unfortunately that too seems "unlikely" (awaiting return from recoil)... more than likely debug logging has been disabled in some way as it is unlikely that a system over the last three years that is still "declared" as 1.3.9 would *not* have a debug issue identified to it.

Such disablement may be associated to the error logging software not being present, the folder access rights not permitting generation, the folder being full (though that too would effect operation) or possibly a change made to the existing logging software to prevent logging. A backup check would be to look at the server logs.

It could be possible that there truly are no log worthy issues, but that would likely depend on keeping the code up-to-date, which also seems unlikely otherwise would expect the version to be up-to-date...

[Dungeonstone]

Folder rights (write access) is open on the logs and cache directories.

The folders are not full.

The most recent file in the cache directory is the .htaccess file created Oct. 19th 2019

The most recent file in the logs directory is a visitor access log I created also in Oct. of 2019.

The only errors that I am seeing on the hosting side of things are the daily list of AH01797 errors generated by my IP banning list blocking (most) Russian and Chinese IPs from accessing the site.