Thread

Hello,

I’ve searched through the Forum a fair amount and am unable to find a solution or similar scenario, so I’d be grateful for help in the midst of a pressing client deadline.

My captcha images are not displaying in the browser on my website (here’s an example of a recent article:  http://www.englishcompass.org/articles/a_simple_prayer).

My client’s site is hosted on EngineHosting, and here are the current Captcha preferences:

Server Path to CAPTCHA Folder: /www/eh14086/public_html/images/captchas/
Full URL to CAPTCHA Folder: http://www.englishcompass.com/images/captchas/
Use TrueType Font for CAPTCHA? No
Add Random Number to CAPTCHA Word: Yes
Require CAPTCHA with logged-in members? Yes

Both the /images and /images/captcha/ folder are set to 777.

The captcha images are actually generated, as I see several of them generated from today through my FTP client, and when I try to download one of them, I see a typical captcha image.  But when I try to grab the image URL from the page’s source code and paste it into a new browser tab, it gives the page not found error message.

Lastly, here’s my current captcha section in between the {exp:comment:form} tags:

{if captcha}
            <div class="comment_label">
                Enter this word:
            </div>
            <div class="comment_field">
                {captcha}
            </div>
            <div class="comment_label">
                Here:
            </div>
            <div class="comment_field">
                
                <input type="text" class="textbox" name="captcha" value="{captcha_word}" 
                size="20" maxlength="20" />
                
            </div>
        {/if}

It stopped working for me a while back, but the client had let the site go dormant for a while.  It’s being re-launched, and I’ve updated EE to 2.5.3 with all the corresponding modules/plugins updates as well. 

What gives?  What am I missing? 

Thanks so much for any help!

Robert

Well this is embarrasing, after not having visited the forum for a while.  After glancing the post after publishing, I noticed the browser URL path field had a .com in it, and the client switched to .org a while back.

So I must have missed it, and changing it made it work now - so never mind. 😊

Glad you figured it out, Robert. 😊

Let us know if we can help again!