Site Crashed with PHP and MySQL error

You just need to copy your php/php.ini handler htaccess code into this BPS Root Custom Code text box: 1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE
Click the Save Root Custom Code button.
Go to the Security Modes tab page and click the Root Folder BulletProof Mode Activate button.

You can get your web host’s php/php.ini handler htaccess code by going to the BPS > htaccess File editor tab page > click the Root htaccess File tab.

php/php.ini handler htaccess code will look similar to this code below. DO NOT USE this example code.
Note: Most web hosts no longer use php/php.ini handler code because of the exact problem scenario you ran into.

# php -- BEGIN cPanel-generated handler, do not edit 
# Set the "ea-php74" package as the default "PHP" programming language.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php74 .php .php7 .phtml 
</IfModule> 
# php -- END cPanel-generated handler, do not edit

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

Another possibility is that you have old php/php.ini htaccess code saved in this Custom Code text box: 1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE.

Delete any old php/php.ini htaccess code saved in Custom Code.
Add new php/php.ini htaccess code if needed/required by your web host.
Click the Save Root Custom Code button.
Go to the Security Modes tab page and click the Root Folder BulletProof Mode Activate button.

But when I clicked “deactivate”, the site went down again.

Ok that confirms that your web host requires php/php.ini htaccess code. You will also need to add your web host’s php/php.ini htaccess code in the BPS default htaccess file. When you click the Deactivate button the BPS default htaccess file replaces the BPS secure htaccess file. Do the steps below to add/save your web host’s php/php.ini htaccess code in the BPS default htaccess file.

You can create a Custom default.htaccess file that will be saved permanently by editing the default.htaccess file using the htaccess File Editor. Your Custom default.htaccess file will be saved permanently to this folder: /bps-backup/master-backups/default.htaccess. If you have created a Custom default.htaccess file then it will be automatically copied from the /bps-backup/master-backups/ folder during a BPS plugin upgrade and will replace the default BPS default.htaccess Master file.

Go to the BPS > htaccess File Editor tab page,
Click the default.htaccess tab.
Add/copy your host’s php/php.ini htaccess code in the BPS default htaccess file right after this text: # BULLETPROOF PRO DEFAULT .HTACCESS
Click the Update File button.

Hi AITpro,

Wow! That’s a fast and thorough reply.

I don’t think I mislead anyone, but I don’t have the “Pro” version.

Would “# BULLETPROOF DEFAULT .HTACCESS” be an OK line to put the new text under?

At any rate, I don’t understand code and need to study this a few times. I may even get the hosting company involved.

There is one more factor, I did mention that I use this plugin on several WordPress sites on the same host and those have no trouble. Does this change anything?

You and the plugin are amazing and I thank-you so much,

Mike.
P.S. The only thing keeping me from going Pro is my own ignorance. It has more features and I’m a bit intimidated by it. Is there a way to run the Pro version in some sort of “basic” mode?

Would “# BULLETPROOF DEFAULT .HTACCESS” be an OK line to put the new text under?

Yep, that’s correct.

The error message is a typical error message that indicates a missing or incorrect php/php.ini handler htaccess code problem.

My guess would be that since you activated root folder BulletProof Mode on the site that crashed, you most likely have old php/php.ini handler htaccess code saved in this BPS Root Custom Code text box: 1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE. But since clicking the BPS Deactivate button also caused the site to crash then that means your host requires using php/php.ini handler htaccess code in your Root htaccess file.

Once you get the problem figured out on the site that crashed, you would check your other sites to see if the same problem exists on those sites and make the same changes on your other sites.

Oh and BPS Pro is completely automated like BPS free. So BPS Pro is just as easy and simple to use as BPS free.

Did you get everything figured out?

Hi AITpro,

It’s nice of you to follow-up.

Yet, at the moment I have only a small bit of news.
And let’s remember that I am not code literate and needed more time than others.

Just yesterday, I figured out what to do by following your excellent instructions.

As per your example, I updated the “BPS Root Custom Code text box” on one site.

But, on three of the others, this part: ” AddHandler application/x-httpd-ea-php74 .php .php7 .phtml ” contains “php71”, and “php73” and “php72” on another. (this might be your reference to ‘old code’)

So I stopped for now.

I thought it would be a good idea for me to contact the hosting company and find out what PHP version settings they think I should add.

When I know their preference, I aim to restore BPS to the new site as well.

Then I plan to go with the BPS-Pro version one site at a time.

Many thanks!

Mike.

That just means you are running different PHP versions on your sites. It would be good to switch to PHP 8.x if your web host offers that PHP version. PHP 8.x is around 20% faster than PHP 7.x versions. You would make that change in your web host control panel. If you have cPanel you would change your PHP version using the cPanel > MultiPHP Manager.

In the Set PHP Version per Domain section, use the search bar to search for your domain and then click the checkbox to the left of the domain name. (Do this for each domain that requires the same PHP version.)
In the top right of the Set PHP Version per Domain section, click the drop-down menu next to PHP Version and select the desired PHP version.
Click the Apply button to change the PHP version of each of the selected domains to the selected PHP version.

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

Assuming all questions have been answered – the thread has been resolved. If the issue/problem is not resolved or you have additional questions about this specific thread topic then you can post them at any time. I still receive email notifications when threads have been resolved.

HI again AITpro,

Thanks for the follow-up!

And I’m sorry that I did not close this myself.

You have gone above and beyond the standards for free help in a free version, and I am so grateful.

If I have any farther trouble I will touch base again.

No need to reply to this note as I know you are busy.

Mike.

No worries. I like to leave threads open for at least a week just in case other problems come up. ??