That’s always been a problem, things scattered everywhere. Will be nice to have a master directory Ryan.
Wish there was a site where EE users could be identified by location. Would be easy to set up get togethers. Been suggested many times but never implemented.

Well, I’ll tell you this much: I don’t see why devot:ee couldn’t help facilitate that. To get the most out of the site one will have to register, so why not include location information? I don’t want to hijack this thread, but I’m certainly open to suggestions above and beyond what I already have planned.

Are there any known bugs for this extension when viewing the captcha form on a Mac using Firefox?

I’ve got the extension working perfectly in everything apart from this combination of OS and browser.

...and yes it’s working on a PC using Firefox. Which does raise more than one eyebrow as to why this wouldn’t be working on a MAC, it seems to defy web-browser logic.

Any help would be greatly appreciated.

Hi Adhesion,

I’m afraid that I don’t know of any bugs/problem that prevent this working on any platform/browser combination. Do you have a URL where I can what’s happening?

Cheers

Dry

Thanks for your speedy response!

Well I’m going to look like an idiot now and say I can’t replicate the issue this morning, worked very late last night trying to resolve it. So I’m more than happy to say it’s working perfectly across every combination now. It’s good to know there are know ‘known’ bugs though.

I can only assume it would have been a caching issue with our development servers?

UPDATE: If any others were having the same issue as me, logout of Expression Engine and then view your website. You should be able to see the captcha form after hitting refresh on your browser.

It looks like there was a conflict between being ‘logged in’ to EE and the captcha form itself. I think this is the same issue you get if you use the native EE captcha forms.

Drylouvre - 20 April 2009 11:54 AM

Hi Adhesion,

I’m afraid that I don’t know of any bugs/problem that prevent this working on any platform/browser combination. Do you have a URL where I can what’s happening?

Cheers

Dry

Adam George - 05 August 2008 10:20 PM

This doesn’t show up for me in the extensions list. (Files uploaded to the appropriate places) EE ver 1.6.3

EDIT: It was a permissions issue. Weird though, that it hasn’t ever happened before with other extensions…

Extension & Language File are both set to 700 and should be set 644.

Hello,

This looks like a great captcha system.

Unfortunately, right after I initialized the captcha extension and visited a page with captcha(s), my browser locked up and it looked like the page was stuck in an endless loop. Here is the repeated error:

Notice Uninitialized string offset: 0 in /path/to/system/folder/extensions/ext.accessible_captcha.php on line 69
Notice Uninitialized string offset: 0 in /path/to/system/folder/extensions/ext.accessible_captcha.php on line 72

Some server details:

Ubuntu Jaunty 9.04 PHP5.x

Hmmm, looking at those lines in the code, I am wondering if it is because I did not fill-in all the question/answers?

This error pretty much brought our server to its knees. :(

Would be cool if you could test the captcha first, before implementing site-wide.

Any tips?

Thanks for this extension! I am excited to get it working.

Thanks,
Micky

Hi Micky,

I’ve not had this error type of error reported before. You shouldn’t need to fill all the Q&As;. I’m just wondering, are you running 5.3?

Cheers

Dry

Hi Dry! Many thanks for the reply, I really appreciate it.

Ah, it looks like we are running:

PHP Version 5.2.6-3ubuntu4.2

I am wondering if we need to upgrade to 5.3.x?

The IS dept. just setup a test server with these specs:

PHP Version 5.2.4-2ubuntu5.5

I will report back with my findings.

Thanks again Dry! I really appreciate it. We are looking forward to using something other than the standard Captcha.

Cheers,
Micky

Hi Micky,

No, you shouldn’t need 5.3 at all - in fact, that may cause more problems. I will set up a test server with the same specs as yours and test it out to try and find out what’s causing it. Did you get any other log file errors at all?

Cheers

Dry

Hi Dry!

Sorry for my late reply.

Many thanks for all of your help! I really appreciate it.

Looking at the error log, I do not see anything related to these notices.

I just installed and enabled it on our test server, and was able to reproduce the same error.

Steps:

1. Installed/enabled ext.
2. Navigated directly to page with CAPTCHA.
3. PHP notices appear.

I then went back to the ext. settings, and filled-in all the questions/answers, and the page loaded without problems.

Next, I went back to delete a few of the Q/A, and the page loaded just fine.

I was able to reproduce the notices again, by re-installing the ext., and then immediately visiting a CAPTCHA page.

Next, on our test server, I re-installed the ext. and then filled in a few questions… I then navigated to a CAPTCHA page and I did not receive any notices.

Lastly, I re-installed the extension and logged out of EE. I then navigated to a CAPTCHA page and received a blank page after about a minute of waiting. I assume this is because of the Output and Debugging Preferences of “1: PHP/SQL error messages shown only to Super Admins.”

So, in conclusion, it looks like if you are a complete noob and do not fill out any questions right away, a CAPTCHA page (at least this happens on our servers) will generate PHP notice messages.

Hmmm, maybe the ext. could fill-in the first Q/A with a default question/answer?

Let me know if you need more info!

Thank you!
Cheers,
Micky

Hi Micky,

You’re right! It really should provide a default Q & A on installation. I’ll update it.

Thanks for your detailed help.

Cheers

Dry

Hi Dry!

Thanks for the super quick replies! I really appreciate all of your help.

We are totally excited to start using this extension.

Have an excellent day!

Cheers,
M

I’m using this plugin and it works pretty good. I just noticed today that the site I’m using it on is getting the comments spammed. I only had one security question on there…“what does 2+2 equal?”

I deleted the comments, changed the question, and blacklisted the IP address. Are multiple questions necessary? Or one good one?

Hi Moxie,

Imho, I think you should max out your questions.

Having just one question would be pretty easy to bypass via automation.

Also, check out CP “Home” >> “Modules” >> “Blacklist/Whitelist”... I like using the “Write Blacklist to .htaccess file?” feature.

Also, don’t forget to download Blacklist/Whitelist from EE.

I’ve run into a bug/problem with my implementation of this extension.

If you submit a form with the wrong answer you receive a message saying the captcha was incorrect. If you then click back to the form correct the captcha answer and resubmit, the answer is still denied even if correct.

I’ve had 2 or 3 guests report that they’ve had problems with the captchas and I think this was the issue with each case. It may also be that for any reason you leave the form and then return (for example, maybe you didn’t fill in a required field and received a user message asking you to go back and fill in the field) this problem occurs.

Has anyone else had this problem? Is it possible that the captcha answer is refreshing when you return to the form but the question isn’t refreshing properly? Perhaps an issue with page caching? I have page caching set for nearly every page on the site.

Here’s a working example of what I’m talking about: http://www.weddingwise.co.nz/add-listing

We’re using the script for every form on the site so the same thing would happen on http://www.weddingwise.co.nz/contact or any other page with a form.

I’ve tested this and on many occasions have been able to reproduce the problem. Would appreciate any suggestions. Thanks.

Hi Benek,

Can you remove the caching on each template where you are using forms to see if the problem persists?

Cheers

Greg

Turning off template caching seems to have fixed the problem, at least in my initial test. I tried two different forms after turning off caching and did not repeat the problem. I’ll do some further testing and report if there are any other problems.

Is there no way to make this extension compatible with template caching?