pbik

It never hurts to ask. ?? Thanks for considering.

For now, we can’t go the GitHub pull route, but hopefully someone will take this missing integration as a challenge/opportunity.

@webtoffee
I’d like to share some in-depth details that might change your mind. This is what happens exactly:

1. New user visits the site, so the Cookie Banner pops up.
2. User now clicks the [cookie_settings] button to learn more, so the Cookie Settings window opens.
3. This time the user correctly sees that non-necessary cookies are OFF (which is my default setting and required by GDPR), so he is calm that he is not tracked.
4. After this he messes with the non-necessary checkbox and turns it ON, but shortly after he decides just to “cancel the whole thing” by clicking outside of the cookie settings window (note: or click the window’s X button | note2: hitting ESC won’t close it)
5. At this stage the cookie settings window is closed now, the non-necessary cookie is set to “yes”, but the cookie banner is still up.
6. My user then starts to read/navigate/return after a day/etc. without ever giving consent, while having the cookie banner up the whole time.
7. Eventually he meets a form that is disabled (via custom coding) that also tells him to enable non-necessary cookies in order to use the form.
8. Now he opens the Cookie Settings window again and sees that the checkbox for the non-necessary cookies is enabled. This is the point when he is falling into panic that he was tracked the whole time. Which was never the case, but he still quits the site in an angry mood without even considering to submit on that form.

I completely understand that the above story is a fine example of the user making an error: i.e. not completely understanding what is going on when the window is closed or forgetting what he set previously. But I think there is room for improvement here and patching it up would also help the premium version of the product -assuming its category checkboxes work the same way.

I could clean up this UX issue on my site only but I believe an official fix would benefit everyone using this plugin.

Sincerely,
pbik

I’ve found a similar issue here: https://www.ads-software.com/support/topic/cf7-siteground-sg-optimizer-update/page/2/

Following the thoughts in it I could track back my issue to SiteGround’s “Defer Render-blocking JS” functionality:

• When it is turned on as before, sending the form produces the error I’ve reported above.
• When it is turned off, CF7 is properly sending.
• If I turn it on and put the /plugins/contact-form-7/modules/recaptcha/index.js on the exclusion list, then the error still appears in the console, but everything seems to be working.

Since this looks like an issue with SiteGround, I’m closing this ticket as resolved.
@thenewguy_14 I hope this can help you too.

Just checked it out and indeed it’s awesome! I’s a breeze now to remove leads that look invalid or of low interest.

And you have added exporting to CSV too! Big thanks for that as well!

Sounds awesome, thank you!

Hi John,

I’ve rolled back to the 5.1.3 version of the plugin, and have tried updating to 6.0.8.3 in the hopes of that it would migrate correctly, but it didn’t help. This is a hint to me that something went wrong in the database.

Since I have no direct access to the database, I’ve decided to restore the website before the plugin was updated and continue using the 5.1.3 stable version for now.

Hi @alaasalama
it’s good to know, thanks for the confirmation.

FYI: I’ve seen some topics that suggest there is a whitelist (in the PHP Compatibility Checker plugin) for plugins that maintain backwards compatibility like yours.

Not sure how to get on the whitelist, but getting on it might save time for others like me wanting to upgrade their PHP version.

Thanks again,
pbik

@clinicaleger
I believe the issue was fixed in version 2.4 (at least what I can tell after comparing source code), however the author ( @mndpsingh287 ) has not explicitely answered here like before.

I’ve moved to WP 5.5 since the update and haven’t faced any problems yet, but I can’t be totally sure that everything works as it should.

Still, marking this now as resolved and hope for the best.