ktaylor310
Forum Replies Created
-
I marked this resolved because I read your notice above and decided to reach out directly to MainWP support, however the issue is not resolved.
I am still having issues. I installed the reset plugin, removed the website from my mainWP dashboard and then reinstalled the child. When I tried to add the website back to the dashboard I received the same error as before, “MainWP Child plugin not detected or could not be reached! Ensure the MainWP Child plugin is installed and activated on the child site, and there are no security rules blocking requests. If you continue experiencing this issue, check the MainWP Community for help. Click here to see response from the child site.” When I went back into the plugin list the child plugin was still not showing.
When I click the response link, I see [hidden response data], but I’m not sure why. I have over 100 websites using mainWP, have never used any type of white label add-on, and this is the only website effected. Could it have something to do with Cloudflare rules? Or Cloudflare turnstile?
- This reply was modified 2 months ago by ktaylor310.
Forum: Plugins
In reply to: [WooCommerce] Cannot view ordersI found a conflict with a plugin that was not installed on the website but had lingering tables in the DB.
Hello, I just heard back from the Post SMTP authors that they have fixed the issue:
Thank you so much for your patience and understanding while we worked on resolving the issue. I’m pleased to inform you that our technical team has successfully implemented a fix. I personally tested the Forminator plugin with the updated version, and it is now fully functional.
The solution has been officially released in version 3.1.1. Kindly update the plugin to the latest version to benefit from this fix.
Thank you.
Post SMTP just came out with an update. I’ve held off updating any other websites, but the two that I updated throw the error. I did deactivate Post SMTP and the error did not occur. When I reactivated the error returned. When I installed a different SMTP Plugin (SMTP2Go) everything worked. Load form using ajax is enabled and your MU cache clearing plugin is installed on the server. That is the correct plugin that you are linking too.
I use Forminator + Post SMTP on all of my websites. I disabled Post SMTP and the form worked, enabled again and it did not. Next I installed a different SMTP plugin and the form worked, so it seems as though that is where the conflict lies. I just recently updated Forminator and Post SMTP, so something in the update is causing the conflict. Post SMTP is a very popular plugin and installed on about 120 of my websites, so hoping you can help with this quickly.
- This reply was modified 10 months, 3 weeks ago by ktaylor310.
Second website experiencing the same issue: https://protechnetworksolutions.com/contact/
Thank you, but all of the templates are the same. Tiny fonts, prefilled placeholders, etc.
I think I found it. I disabled WAF7 and it is working now. Thank you for all of your help.
Kimi
Hi, sorry for the delay but I was too busy to do the testing until now. I am still getting the error with all plugins except Smush deactivated, also when switching to 2024 theme. There are no errors under site health, just a warning that they could not find a page cache plugin. I use server side Redis caching. Also no errors in the Nginx error log. It also did not help to disable wpFail2Ban.
WP Debug only shows deprecation warnings:
[12-Nov-2024 17:42:43 UTC] PHP Deprecated: Hook wp_smush_should_skip_parse is <strong>deprecated</strong> since version 3.16.1! Use wp_smush_should_skip_lazy_load instead. in /var/www/winkpanels.com/htdocs/wp-includes/functions.php on line 6085Console error:
media-library-scanner.js:38 Error: {success: false}
(anonymous) @ media-library-scanner.js:38
Promise.catch
value @ media-library-scanner.js:37
value @ media-library-scanner-on-bulk-smush.js:39
(anonymous) @ media-library-scanner-on-bulk-smush.js:395Switching to Microsoft Edge did allow the form to go through, however I was originally using Chrome (most popular). I do not use any browser extensions except for screenshot.
This issue was actually not solved. I provided the information requested above the same day it was requested, but I have not heard back regarding any solution.
Kimi
No, the problem is still occurring. One of our employees tried the form and it worked, but it has not worked the two times I have tried.
Here is a link to the form export: https://www.dropbox.com/scl/fi/sdpa37f3jli0fcmf7qagr/forminator-employment-candidate-form-export.txt?rlkey=xqrhw5cj6tedin01lu17fpy4r&st=9c9qiw17&dl=0
Here is a link to a screen capture: https://www.dropbox.com/scl/fi/tdaliha8z3lpz830a1zw3/CareersForm.mp4?rlkey=q69v5fow9el0aun04l5ac2q0h&st=jh4ln4oh&dl=0
Thank you for your help!
I found the issue. The posts were actually there, but the DB prefix did not match the DB prefix on the destination server.
Thank you so much for your time!! I looked on the backend and payments are showing as completed. I did find one mistake in the conditional logic for one of the behaviors (heavy, heavy conditional logic) and fixing that also fixed the success message. I have re-tested the forms, success messages and various emails and everything seems to be working now. Thank you again for looking into this.
