locatejp

Hey Patrick, I had a feeling that reproducing the error was going to be challenging. Editing that section seemed like an unlikely reason to make the website crash, but so far it has proven to be consistent. As you suggested, it could be the result of interplay between two plugins, or some setting that we have enabled.

I enabled the debugging. There were other errors when I made sure the logging was working correctly. I’m going to put my fingers in my ears on those errors for now and deal with them later.

When the website crashes, it comes up quickly, so for the better of the community I’m going to take the same actions again and see if it gives us some workable logs.

Instruction was blank (using default text) so I added in the string “Use the password provided to you via email.”. I noticed a banner at the top that appeared that said “Connection lost.?Saving has been disabled until you are reconnected.?This post is being backed up in your browser, just in case.” The update button was not available, neither was the Preview button. I opened up a new tab for the website and it showed a crashed site. Message: This site can’t be reached boomerangtransport.net unexpectedly closed the connection.

I went into my hosting firewall and cleared the cache and reset the connection so that no users would see it go down (we are using CDN caching).

The logs don’t give us a lot to go on. There are 2 messages that show up over and over again, and then one new one that showed up right around the time that this action crashed the site. Here they are:

[21-Jul-2023 18:30:50 UTC] PHP Deprecated:  Function add_custom_background is <strong>deprecated</strong> since version 3.4.0! Use add_theme_support( 'custom-background', $args ) instead. in /home/XXX/public_html/wp-includes/functions.php on line 5413
[21-Jul-2023 18:30:50 UTC] PHP Deprecated:  Function add_custom_image_header is <strong>deprecated</strong> since version 3.4.0! Use add_theme_support( 'custom-header', $args ) instead. in /home/XXX/public_html/wp-includes/functions.php on line 5413
[21-Jul-2023 18:30:50 UTC] PHP Notice:  Only variables should be assigned by reference in /home/XXX/public_html/wp-content/plugins/exclude-pages/exclude_pages.php on line 92

So, it looks like this could be an issue with the exclude_pages even though it appears to be the use of your plugin that triggers it. The first two messages are the ones that just repeat over and over again and don’t seem to crash the site.

I hope this is helpful. I also hope that it identifies a way to improve the app to reduce cross plugin issues. Do you have any suggestions as to how we should proceed? Thank you

Hi Patrick-

Thank you for your prompt response. We are using Version 4.2.1. The steps I took were:

• Navigate to the page in the WordPress dashboard editor
• Find the Passster widget on the right hand side
• Click the radio button to Overwrite defaults
• Change the Headline (that worked)
• Change the Instruction (at some point in here something failed). The text I was adding did not have any HTML or tags, it was just normal text. Example- “Use the password sent to you via email in the box below”
• Click Update for the page
• The website crashed

I don’t really want to mess with it more as I don’t want my website to crash again. I duplicated this result twice. I updated the Placeholder afterwards and it did not crash the site. I’m happy to do whatever else I can to help troubleshoot this issue.

@naa986 Here is a video that appears to identify the plugin. Let me know what you think – https://drive.google.com/file/d/1GQeLoM_ZCJ1fNS6K7boB8YNwN_3O1Cp1/view.

@naa986 thanks again for your prompt responses. You said:

Version 1.2.1 uses WordPress’s mail filter, pre_wp_mail which was introduced in 5.7, instead of redefining the wp_mail function

So it sounds like it could be an issue where pre_wp_mail is causing my messages to fail. I’m not sure if this is within the scope of support you are able to suggest or not, but then again maybe it could affect a lot of your user base. How would I test that and what would the suggested course of action be to put in a fix? Thanks-

Thank you for your prompt response! I do not have a staging site. Do you think it could have to do with Contact Form 7? As I mentioned previously I had the same issue when updating to a new version on that plugin. What is the suggested ‘fix’ for this?

Hi! Is there any movement on this? I keep skipping updates for fear that it will break again. I have provided as much information as I can and hopefully you are able to troubleshoot and find a solution. Thanks!

I disabled most of them during the testing phase (at least the ones that I thought could possibly interfere) and it didn’t resolve the issue. Only rolling back to a previous version solved it.

Here are the ones still active:
Autoptimize
Classic editor
Contact Form 7
EWWW Image Optimizer
Exclude Pages from Navigation
Flamingo
Get-a-Post
Gmail SMTP
Google Analytics for WordPress by MonsterInsights
Google Tag Manager for WordPress
Meks Quick Plugin Disabler
mTouch Quiz
PHP Compatibility Checker
Really Simple SSL
Simple Calendar
Updraft Plus
WP Rollback
Yoast SEO

Hi, sorry for not including that earlier. The website with some contact form examples are https://boomerangtransport.net/contact-us/ and https://boomerangtransport.net/coordinator-position/. Those are live forms. You can test on https://boomerangtransport.net/airport-transportation/ all you want and those emails just get sent to me. I’m happy to help troubleshoot in any way to do my part to get this resolved. Thanks!