David M Hodges

This issue seems to have related somehow to when the carousels were created for use in Divi global sections. Though no variety of fix could get them to function properly after they’d been created, recreating them later did fix the issue. When the global sections were initially created, none of our three video categories had more than a few videos in it. As videos were later added, the carousels could scroll through the full collection when dragged, but the arrows to previous and next videos never displayed. They only finally displayed when the carousels were recreated with the same settings. Bizarre.

Though this might be purely a Divi issue, I’ll leave this post unresolved in case it turns out there is a tweak you can make to the plugin to prevent similar behavior in the future.

The plugin can now be activated and usually displays the feed as before. However, it is unusually slow and sometimes fails to load. This may be a site issue rather than due to your plugin. Any other plugin users reporting problems?

After upgrading this and a few other plugins simultaneously, my site stopped displaying on the Web. During one-plugin-at-a-time reinstallation (through my Web host, since I lacked access to the WordPress Dashboard) and reactivation, I got the following WordPress message when I attempted to activate this plugin: “Parse error: syntax error, unexpected T_FUNCTION in …. jp_get_rss_feed_items.php on line 704.

Hi, bestfrenchmortgage.

Before reading your procedure, and believing my test proved that Limited Login Attempts (LLA) was the problem, I switched from LLA to a compatible plugin that also permits limiting login attempts, then reactivated Captcha. The plugin I switched to is Wordfence. If you try it, be aware of this issue, which gave me some problems.

Anyway, Captcha’s people now appear to accept that Captcha was the cause, but say that the problem has been fixed.

Before getting notice of the bug fix, and believing my test proved that Limited Login Attempts (LLA) was the problem, I switched from LLA to a compatible plugin that also permits limiting login attempts, then reactivated Captcha. The plugin I switched to is Wordfence. If you try it, be aware of this issue.

Anyway, thanks for the quick fix.

Followup. I tried deactivating Captcha and keeping Limit Login Attempts running. My “tries remaining” continued to count down. I think this means Limit Login Attempts alone is the problem, not the combination of Limit Login Attempts and Captcha.

Followup. I tried deactivating Captcha and keeping Limit Login Attempts running. My “tries remaining” continued to count down. I think this means Limit Login Attempts alone is the problem, not the combination of Limit Login Attempts and Captcha. I look forward to hearing that this has been fixed or that someone else in the forum has found a good replacement plugin.

I had the same problem as Howdy_McGee. FYI, I had these two plugins running together for some time with no problems. Presumably a recent update to one of them (or perhaps to WordPress?) broke something. I look forward to hearing this problem is fixed so I can resume using Captcha.

My mistake; I was using the same Captcha plugin. I note that I had these two plugins running together for some time with no problems. Presumably a recent update to one of them (or perhaps to WordPress?) broke something.

I have the same problem, but appear to be using a different Captcha plugin than Howdy_McGee. This seems like a problem the Limit Login Attempts developer should be able to fix, not something every Captcha provider should have to work around.