laoren

Dear Sybre,

Thank you for your swift and thoughtful reply, and for the work you’ve already put into investigating this issue.

I’d like to express my gratitude for pointing me towards the sitemap endpoint workaround. Following your insights, I’ve created a custom robots.txt file which has been acknowledged and accepted by the Google Search Console with great results. Your expertise has not only helped me navigate this hiccup but also enhanced the functionality for others who may face similar challenges.

With the solution in place and functioning correctly, I’m happy to move forward and close this case. Your willingness to explore this matter and the plugin’s robust performance are much appreciated. I look forward to the continued success and evolution of your work.

Best wishes and thank you once again for your exceptional assistance.

Kind regards,

Laoren

@mada99
Same problem here. Thanks for reporting it first.

@keramikoch
I get the same error message. Thank you for reporting to the developer.

@Plugin-Developer
On my setup, the error only occurs, when I’m on the Simple History Page in the backend and a new event happens during that duration. IMHO there is no need to have the page updated while viewing.
Otherwise, your tool is very helpful.
Thank you

Hello, @tanya357
I finally solved this by using the acceptance checkbox as described here:
https://contactform7.com/acceptance-checkbox/
For my forms, it’s fine.
Best wishes
Laoren

@tanya357 Hello
No improvement on update 5.6.2 for our case.

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

I had the same problem. It can be solved very easy by hiding the submit button when the spinner is visible. It’s only css:

form.submitting input {
visibility: hidden;
}

@tanya357 Hello,
I checked with the yesterday’s update 5.6.1
No improvement.

Sure, we try after the next update(s).
Please post here, in case you can confirm the fix.
I’ll do the same.

I’ve noticed the same since the last update (5.6). It’s only related to the checkbox validation. I solved the problem temporary by removing the ‘is mandatory (*) marker’ from the checkbox in the form.

I have the same question.

Thanks again, Elvira
I figured it out. My bad with a single line of silly php.
Sorry for keeping you busy.

Cheers, Lao

Hi Elvira,
thanks for following up and for confirmation that this is an individual problem.
I use the Russian translation for monitoring (due to low traffic). We are using Polylang, so the behaviour is for all languages the same. In the other languages the widget is deactivated for pages.
Activities:
I reviewed the HTML widget content, it holds only the MailPoet shortcode.
Then I replaced the widget with the MailPoet Form 3 widget.
I also switched the PHP back to 7.4
The behaviour is still the same.
Sorry for contacting you, sooner or later I’ll find out the reason for the interaction between Query Loop and MailPoet form.
If you are interested, you can see the effect on the bottom right side:
Homepage with Query Loop -> no form
About Us page without Query Loop -> normal appearance of form and footer.

Thank you again for taking care.
If you have another suggestion, please let me know. Otherwise, mark it as resolved.

Cheers

Update
The forms show up on pages without Gutenberg Query Loop. When I put a query loop on the page, the form is gone.
I simulated it, the bug is reproducible on a test page.
Seems that there is a conflict between the query loop block and MailPoet.

Additional info
I just figured out that the error only occurs, when I mark an image as already compressed by another plugin.
Then the column WP-Optimize in the list view shows:
The file was compressed to N/A using WP-Optimize
Hope it’s helpful to reproduce the error.

Your Version 3.75.1 has fixed the error messages.
Thank you