pandorawombat

Well, as I said, it only occurs on some of our sites – not all of them. And I personally am using version 52.0.2743.82 m on Windows 7, but clients have reported the same problem on Windows 10. I don’t think it’s the browser because if I open these same sites in Firefox, the CAPTCHA shows up, but refuses to accept any answer as the right answer. I’m just saying the Google disappearing CAPTCHA was the common thing that tipped me off that something was wrong on these few sites. And most of the sites, where I did a clean install of the plugin after this problem was FIRST reported (before they released the second patch after this thread was started) worked fine after that. So it’s hard to nail down. I’m really just trying to add data to your problem at this point, because I have been forced to find workarounds for these remaining couple of sites – disabling CAPTCHA. On other sites we have, it works just fine. Exact same server settings. Of course, there’s any number of differences in other plugins, etc. I’m just saying the common denominator is that none of this happened before the day this problem first started showing up for so many other people – after the 4.1.3 update. And the 4.1.4 update that was supposed to fix it “rebroke” at least 2 of our sites after we’d already fixed them the first time around. Most of our sites run on NGINX on Ubuntu. So I’m just keeping an eye on this thread to see if anyone else is experiencing similar issues. Before that 4.1.3 upgrade, we have run this plugin on about 200 client sites for quite some time and never had an issue before, so this caught us kind of by surprise.

The one “symptom” that always seems to occur in common on a site that is the dead giveaway that this problem has occurred is that even though you have login CAPTCHA turned on, the CAPTCHA does not show up in Google Chrome on Windows. Not even if you Inspect Element and try to find it in the DOM to see if it’s hidden. But then it fails to log in no matter what because “incorrect answer.” And then your clients call you panicking because they’ve locked themselves out from too many tries.

Yes, it’s weird. Before you pushed the “fix” yesterday, I had successfully fixed all my broken sites by forcibly nuking the settings, clearing the cache, and reloading them. After upgrading to your fix, the problem reappeared on at least one of my sites and would not go away until I completely disabled CAPTCHA. But not all my sites. It’s frustrating because I don’t have time to microanalyze all these sites to figure out the pattern of what’s causing it to fail for some and not for others.

I’m having this same problem, but it occurred right after I turned on the “firewall” portion today on a site that previously didn’t have it turned on. And then, it outright doesn’t even SHOW the CAPTCHA field on Chrome, but fails login because “answer is incorrect” (I did an F12 inspect, and I don’t even see it as a hidden field). The field shows up in FireFox, but the answer is never accepted as correct. So I’ve disabled the plugin and am getting ready to just reset all the settings as you were talking about directly in the database, but I just wanted to add that yes, this is a thing that happened to me too today.

That is what we ended up doing. Thanks for your help.

Just to clarify, we are using jQuery infinitescroll – not any wordpress plugin with a similar name.

I am having the exact same problem, and a quick search of the web and this site reveals that tons of people are having this problem even with every imaginable configuration, and there seems to be no definitive answer. I am convinced it is a bug. I’ve tried it across several browsers, on Mac and PC, logged in vs. not logged in, clear cache, switch themes, disable all plugins – you name it, I tried it. Maybe somebody will figure it out someday.

I’d certainly like to know the answer to this as well. I’m searching all over the web, and it seems like people all over are having this problem but no one has a definitive solution to it. This leads me to believe it’s a bug.

Also, just an fyi, my email address is also specified in the readme.txt file that comes with the plugin, for anyone who needs it.

Hi! I am the developer, and if you’ll scroll down to the bottom of that page, you’ll notice it has commenting turned on – this was designed to make it easy to contact me. A French version sounds awesome, by the way!

You might also have noticed within the thread of comments that I stated my email address a number of times to assist people – if you want it, it is pandorawombat at gmail dot com (you obviously replace the at and the dot – I am trying to avoid email harvesting). I apologize for not having a contact form per se – people seemed to be ok with just using the comment function to contact me about the plugin.

The whole purpose of this plugin is to allow end users to submit large files to an ftp site. It is a php implementation of a very simple ftp client. Javascript is used only to validate the form for required fields.

It’s very simple. The person uploading fills out the form to explain what to do with the upload, then selects a file and clicks Upload. The file they have selected then gets put onto the ftp site you have designated in the settings, and a notification email is sent to the email address you have also specified in the settings.

There is no automatic post-processing of any sort. This was not designed to enhance WordPress functionality – it was designed entirely to allow places such as print shops and graphic houses to provide their customers an easy way to submit files. Thus, this plugin probably wouldn’t work for what you want to do with it.

I have just made a 2.7 upgrade available that should solve the problem people were experiencing with getting it to reuse existing directories.

As for securing FTP access, if this is a concern, you might want to consider forcing people to become users before uploading, then restricting the page to be used by registered users only. Then you could have some control by “vetting” the person before giving them an account.

I had no desire to add any restrictive code, because the whole reason I wrote the plugin was so any customer of ours could upload without any sort of hassle or hoops to jump through. But I will try to give some thought to how I could make that an option.