consultant1027

I was wondering about a feature like that. Rollback option should be a standard feature of WordPress! I manage too many sites to do manual updates and test. If a down monitor is trigger then I investigate, backup the database, then restore the backup before the plugin was updated, restore the database backup (assuming the update didn’t make changes to it’s DB table structure) and then exclude it from auto updates until the problem is resolved.

That rollback plugin is a much more elegant solution.

I would disagree about the problem being Google Search Console simply from the fact none of my 6.0.1 sites were having the problem. Could Google Search Console been changed about the same time 6.0.2 was released? Not likely.

In any case it’s not a major factor for search implications in my opinion. Just a minor annoyance.

Google doesn’t give any more detailed information. I’m not the only one. It’s something that started happening with 6.0.2. The fact probably a lot of WordPress sites out there have yet to update to 6.0.2 combined with many WordPress users are probably not signed up with Google Search Console combined with Google can crawl different sites with less frequency doesn’t surprise me there isn’t a flood of inquiries about this yet. It may not have any significant consequence from Google rankings standpoint but my stance is that it’s better to fix it to remove the chance of that happening.

There’s another thread that just got started on it but the title of it in my opinion is not well written as to make people having the issue easily find the right thread, hence why I started a separate thread with a more accurate title description.

https://www.ads-software.com/support/topic/wordpress-6-0-2-update-gsc-showing-5xx-errors/

The full path of the problem page will be {domain name}/wp-admin/admin-ajax.php

• This reply was modified 2 years, 2 months ago by consultant1027.

Just happened to one of my sites using the plugin but not the other. Had to login via Recovery Mode. Interestingly, no update available message. Had to click the Details link on the plugin and update from there. .08 version fixed it here too.

I am working with support and I pointed out the fact the plug documentation says “By default, duplicate entries can’t be submitted within 60 seconds of each other.”

Like others, I’ve seen BOTH duplicate entries with the same date and time and duplicate entries hours apart. I brought this to support’s attention in my reply. They said…

“it is possible that this is caused by server cache, this is well documented here https://formidableforms.com/knowledgebase/why-am-i-receiving-duplicate-entries/”

The caching plugin I use (WP Fastest Cache) has not been recently updated nor have there been any setting changes. I’ve not had this duplicate problem before for at least 2 years (at least not that I noticed as this is a client’s website and they may have only starting noticing recently due to it happening more often.)

And the database corruption problem mentioned here https://formidableforms.com/knowledgebase/why-am-i-receiving-duplicate-entries/ per the description causes duplicates with the same datetime stamp.

So logic seems to indicate it’s not the cache plugin. As I mentioned before only two things changed with the site right before I was notified this was happening. Manual update to WordPress 5.7 and update to Formidable Forms 4.1 about 10-14 days ago.

The crazy thing is I see messages from many months ago in this support forum describing the same issues and it’s not always duplicate entries with the same time but hours or days apart. This seems to me it’s a bug in the core code of Formidable that has somehow resurfaced, or, it’s a plugin conflict that only affects certain combinations of plugins and therefore only certain user’s websites. But I’ve not installed any new plugins.

(https://formidableforms.com/knowledgebase/frm_time_to_check_duplicates/#kb-disallow-duplicate-entries-in-a-specific-form-for-one-year)

• This reply was modified 3 years, 7 months ago by consultant1027.

This thread is marked “Resolved?” LOL

As about March 25, 2021 we are starting to see this issue for the first time on one of my websites. Haven’t seen it happen on the other two running Formidable (yet). It’s happened with only two dupes at the exact same time and with 4 dupes spanning 2 days at randomnly spaced times. It’s as if the user is returning to our website and somehow triggering another form submission without actually submitting the form themselves. The contents are exactly the same.

The only thing that has changed is we updated to the latest wordpress and formidable forms plugin right before this started happing. But I see posts about similar things happening months and years ago!

Formidable has a published add-in hook to prevent duplicate entries, which to me, as a Software Developer for 30 years, is a definite BAND-AID approach to something that isn’t working right.

Got the same message from Support to install the add-in hook. Let’s have a REAL solution that doesn’t require makeshift patches.

• This reply was modified 3 years, 7 months ago by consultant1027.

I should add I doubt it’s a conflict with another plugin as disabling the conflicting plugin would have probably also solved the problem. My gut as a Sys Admin is that it is probably related to one or a combination of the WordPress version, PHP version, and using GD library instead of Imagick. I would start there as trying to get the exact combination of plugins is going to be time consuming.

PHP 7.3

I haven’t tested with posts. It’s directly adding via the Media library. I actually don’t need to use your plugin anymore, I just accidentally left it activated and when I couldn’t upload images starting a few days ago. I just thought it would be good to post about my experience in case any other users ran into this. I had to go through my entire list of plugins, disable one at a time, try to upload, then re-activate the plugin. I went down my entire list of plugins and I got to yours and when I deactivated it, it fixed the problem. I am running the latest Divi Theme. I’m a Sys Admin running on my own dedicated server so I have full control over all aspects of the server. It is running WHM/Cpanel on Centos 7. The Imagick PHP module is disabled. Enabling it makes no difference. WordPress will use the GD library instead automatically. No changes were made to the WordPress site when this started happening other than automatic updates of plugins and update to WordPress 5.5.3. I don’t upload images that often so trying to determine if a specific update caused the problem is virtually impossible.

These are the other plugins I have activated:

Better Search & Replace
Broken Link Checker
Divi Classic Editor
Divi-Modules – Table Maker
Duplicate Page
Easy Updates Manager
Email Address Encoder (by Till Kruss)
Formidable Forms
Formidable Forms Pro
Formidable Views
Funeral Press
Header Footer Code Manager
iThemes Security
ManageWP Worker
Popups for Divi
Smush
Sucuri Security
Ultimate FAQ
UpdraftPlus
WooCommerce
WooCommerce Catalog Visibility Options
WP Fastest Cache
WP FuneralPress Premium
Yoast SEO

More updates. The recaptcha fails on the first submit. Then if you just resubmit the form again without changing anything, it works!

I just tried testing my form without being a logged in user and got the recaptcha failure!

I just remembered that after installing Wordfence a few months back I had some issues with it blocking functions (form updating) in Formidable and you had to confirm to whitelist it.

So I disabled Wordfence and it worked. But nope I tried it again, and it failed even with the Wordfence plugin disabled!

Something odd going on.

• This reply was modified 4 years, 1 month ago by consultant1027.

I made no mention of having server load issue. Was just wondering if anyone did any before and after benchmarking to see the difference. I am using the Extended Mode.

I like using Sucuri as mentioned for the user activity logging feature without having to install an additional plugin (posts updated, plugins activated/deactivated, etc). I also like it’s external malware scan as I’ve seen posts when researching these plugins that in some cases Sucuri found some malware javascript on pages which Wordfence’s server-side scan didn’t. However Wordfence has FAR more hardening features where Sucuri is pretty basic and just makes a lot of recommendations for manual hardening config tasks.

Right now I’m trying to determine how much the Wordfence WAF (extended mode) increases the server load. I tested the scan by manually running it and on my server it only takes a minute and took the CPU load from 0.8 to 1.3 during the scan, virtually insignificant, which was refreshing.

The only reason I’m not using iThemes anymore is because it doesn’t have the ability for immediate lockout of users attempting to login with invalid username. I need that to de-clutter the user activity log in Sucuri from having tons of failed login attempt messages.

The only thing missing is real-time IP blacklist as that is a paid feature in Wordfence but is free in the Network Security feature in iThemes. However my Configserver firewall protecting the entire host through IPTables subscribes to all the major blacklists so that is protecting the server before the requests even get to WordPress so I don’t think I need to be concerned about a plugin for an individual WP site having that capability.

• This reply was modified 4 years, 6 months ago by consultant1027.

This is a Sitecheck error – Sitecheck is a scan run externally from the Sucuri server. It’s not a script running on your server. If you go here:

https://sitecheck.sucuri.net/

And enter your site URL, you’ll get the timeout error.

Unfortunately (for me) since I manage my own host, I turned off all other server firewall functions and disabled any WordPress security plugins other than Sucuri and it still fails and of course Sucuri can’t offer any specific info on what operation the Sitecheck scan is trying to perform that is timing out. It is almost like Sitecheck is broke and they just aren’t admitting it.

I took a look at the database tables for this plugin and it appears no where does it store the complete referrer URL. Was this functionality removed and then the screenshots in the documentation were not updated?