Paddy Landau

Thank you, Andrew. I appreciate your time.

Andrew, that’s what I’m talking about. When I fill in that form, I get the error message:

Sorry, post is too old.

Back to WordPress ? Support.

Perhaps as moderator you can delete my previous review and then I can recreate it?

@andrew, it’s for WP Statistics.

@murphy18241, I think that you have been unlucky. A friend and I have both used WordPress for quite some time, and never had the problems that you have experienced.

Well, I did have a serious problem recently, but that was due to a silly mistake that I had made in my .htaccess file. That was my fault, not WordPress’s, and as soon as I located and fixed the error, everything worked again.

Thank you for the list. There are one or two that may be of use (the automatic translaters are not what we are after; we have volunteers from throughout the world).

I shall check them out and keep searching if necessary.

@nofearinc: Thank you for your response.

I went into the Administration back-end > Plugins > Add New, and searched for WPML. I get 105 results, some of which refer to WPML, but I don’t seem to find WPML itself!

Oh… having just written that, I found what seems to be the WPML site.

WPML looks fantastic. Unfortunately, I don’t see the team getting a sponsor to cough up the $80 to buy it plus $40 each year.

I shall have to keep looking for an alternative option.

The only things that come to mind are your permissions and .htaccess file. For example, on the OP’s site, if I try to view a thumbnail independently (right-click, view image), I get 403 Forbidden.

1) Check that the relevant directories have read and execute access to all, and that the relevant files have read access to all.

2) Check that your .htaccess file does not have some line that accidentally prevents viewing pictures under some circumstances (e.g. if you are trying to prevent bandwidth-theft (hotlinking) and you have mistyped something).

HTH

That sounds bizarre, Jase. Good luck with finding a replacement.

I’m sorry, I don’t know what else to suggest. I’m hardly an expert with these things. Try contacting your host’s support; with luck, the support person will have some idea. Also Google for this problem.

Oh yes, one more thing. Each directory inherits its parent .htaccess (which in turn inherits its parent’s one). Whenever there is conflict between two levels, the lowest level takes priority. So, check all the .htaccess files (if any) between / (your root directory) and /wp-content/uploads/wpcf7_captcha inclusive.

Good luck. I hope you find the problem.

The WordPress part looks fine.

The line RewriteRule .*\.()$ - [F,NC] does look odd. I’m struggling to understand its purpose. If I have understood it correctly, it is a poorly-written command to say that any URL ending in a dot (e.g. www.example.com/abc.) will fail. See the Apache reference on regexp.

I would comment out this line (add a # at the beginning of the line), or just delete the line.

On some servers, it can take a few minutes to show up changes to your page — or, your browser may be remembering the previous result. So, make your change to .htaccess; wait five minutes; clear your browser’s cache; then try again.

If you want to prevent hot-linking, try this code (replace example.com with your domain name excluding the www.), and place it before the WordPress section in .htaccess.

RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^https://(www\.)?example.com [NC]
RewriteRule \.(jpg|jpeg|gif|png|bmp|pdf)$ - [NC,F,L]

Let us know if this helps.

Did it work previously, when you posted one week ago?

I would suggest you double-check your .htaccess; maybe post it here if it’s not confidential, so we can have a look.

Thanks, I’ve marked the thread as resolved now. I’m glad it helped you.

Little things like that are so hard to trap, but I’ve learned a good lesson from it.

@jasewatson: I had put an entry in my .htaccess file to prevent bandwidth-theft (I forget the correct technical name) for images and documents. It runs as follows (replace “example.com” with your own website address, omitting the “www.” if you use it):

RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^https://(www\.)?example.com [NC]
RewriteRule \.(jpg|jpeg|gif|png|bmp|pdf)$ - [NC,F,L]

I had misspelled my website address (doh!). This caused intermittent problems in Firefox, also giving different results with different browsers, which is why it took so long to catch the cause. It also prevented the CAPTCHA from displaying.

I found the problem on my server. See my previous thread on this issue.

I hope it helps you.

I have discovered the problem.

I had made a small change to the .htaccess file on the server, and accidentally introduced a small error. Small, but important; it affected the loading of images in a small number of specific situations, and even then only with certain browsers. The CAPTCHA was one of the situations.

If you have this problem, check your .htaccess file carefully.

How do I mark this thread as solved?