11
Quote:
ghia wrote:
Mine was tested on 2.4.0 (2.4.1 should go also)
AFAIK for 2.3.3 the same modifications should go in /Frameworks/captcha/ but not tested nor verified.
I tried to implement ghia's hacks on my 2.3.3 test site but could not. The files in Frameworks/captcha are different from what he describes. config.php is different (although there are some equivalent lines) and xoopscaptcha does not exist. There is a file captcha.php.
I tried making changes to config.php and captcha.php as near as I could to ghia's instructions but it did not work.
In my XOOPS 2.3.3 installations there are files in class/captcha corresponding to ghia's instructions but I gather that in 2.3.3 the captcha uses the files in Frameworks. I actually tried modifying both sets with no luck. In both cases the usual XOOPS captcha image came up on clicking on the register link.
One other point I'm not clear on: In recaptcha.php in the line:
$publickey = $this->config["public_key"]; // you got this from the signup page see config.captcha.php
should public_key be replaced with the public key one downloads or is it read from the config files?
I guess I'll have to wait until I upgrade to 2.4.1 to implement this but I am concerned about the reported problems with the Content module (version 1.3), which works well on 2.3.3 but apparently is broken under 2.4.1. Until that is fixed I can't upgrade as I use the Content module extensively on my site.
barryC