{"id":3576,"date":"2011-12-29T14:50:40","date_gmt":"2011-12-29T21:50:40","guid":{"rendered":"http:\/\/www.ait-pro.com\/aitpro-blog\/?p=3576"},"modified":"2016-05-20T09:48:29","modified_gmt":"2016-05-20T16:48:29","slug":"custom-php-ini-faq","status":"publish","type":"post","link":"https:\/\/www.ait-pro.com\/aitpro-blog\/3576\/bulletproof-security-pro\/custom-php-ini-faq\/","title":{"rendered":"Custom php.ini FAQ – Custom php.ini Terms, PHP Errors, Web Hosts List, General Website Terms, General Hosting Terms"},"content":{"rendered":"

Frequently Asked Questions About Custom php.ini files, .user.ini files, PHP errors, Partial List of Web Hosts that BPS Pro has been installed on, General website and Hosting terms.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
What is my Hosting Account Name?<\/a><\/td>\n<\/tr>\n
What is my Document Root Folder?<\/a><\/td>\n<\/tr>\n
Do I need to create a custom php.ini file for each of my websites?<\/a><\/td>\n<\/tr>\n
Does each website need to have its own PHP Error log?<\/a><\/td>\n<\/tr>\n
List of Web Hosts that BPS Pro has been installed on and custom php.ini file requirements<\/a><\/td>\n<\/tr>\n
Why am I seeing PHP errors and what do they mean?<\/a><\/td>\n<\/tr>\n
PHP5.3.x .user.ini Known Problem & Solutions<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/a><\/p>\n

What is my Hosting Account Name?<\/span><\/h2>\n

The Hosting Account name causes a lot of confusion because this term is used broadly to describe many different things about a Hosting Account – cPanel name, username, user account name, etc. \u00a0The example below shows what the literal meaning of a Hosting Account name when looking at your Hosting Account folder structure. \u00a0For this example I have 2 separate Hosting Accounts. \u00a0One example Hosting Account is named frog000 and another example Hosting Account is named bird444.<\/p>\n

The Hosting Account name is frog000 and this example Hosting Account has 3 example websites in this Hosting Account.<\/strong><\/span>
\n\/home\/frog000<\/span>\/public_html\/example-website-frog.com
\n\/home\/frog000<\/span>\/public_html\/some-other-example-website-frog.com
\n\/home\/frog000<\/span>\/public_html\/another-example-website-frog.com<\/p>\n

The Hosting Account name is bird444 and this example Hosting Account has 3 example websites in this Hosting Account.<\/strong><\/span>
\n\/home\/bird444<\/span>\/public_html\/example-website-bird.com
\n\/home\/bird444<\/span>\/public_html\/some-other-example-website-bird.com
\n\/home\/bird444<\/span>\/public_html\/nother-example-website-bird.com<\/p>\n

The Hosting Account name is a folder name above your Document Root folder (\/public_html, \/html, \/htdocs, etc. depending on what folder naming convention your particular web host uses). \u00a0Your web host creates a folder name for your Hosting Account so that all of your websites under your Hosting Account are stored under you Hosting Account folder and are separate and unique from all other Hosting Accounts (folders) on the Server that your websites are hosted on.<\/p>\n

<\/a><\/p>\n

What is my Document Root Folder?<\/span><\/h2>\n

A Document Root folder can be named \/public_html, \/html, \/htdocs or some other name depending on what naming convention your particular web host is using. The Example below shows several example Document Root folders. As you can see this can be very confusing because every host uses their own unique folder naming structure (the x’s are used to hide actual folder naming conventions for web hosts. You would see your host’s actual folder naming convention in place of the x’s). The important thing to notice is that typically your individual website folder names would come after your Document Root folder path. Note:<\/strong> A Hosting Account folder is going to be one folder level above your Document Root folder (the folder name that comes before \/public_html, \/html, \/htdocs, etc.), but typically the Document Root folder is called your Hosting Account Root<\/strong> folder.<\/p>\n

\/home\/xxxxx\/public_html\/
\n\/home\/username\/public_html\/
\n\/www\/yourdomain.com\/public_html\/
\n\/username\/homepages\/xx\/xxxxxxxx\/htdocs\/
\n\/data\/xx\/x\/xx\/xxx\/xxxxxx\/user\/xxxxxx\/htdocs\/
\n\/home\/content\/xx\/xxxxxx\/html\/
\n\/home\/xxxx\/domains\/example.com\/html\/<\/p>\n

Document Root folder path with website folder name added to the folder path<\/strong><\/span>
\n\/home\/xxxxx\/public_html\/example.com
\n\/home\/username\/public_html\/example.com
\n\/www\/yourdomain.com\/public_html\/example.com
\n\/username\/homepages\/xx\/xxxxxxxx\/htdocs\/example.com
\n\/data\/xx\/x\/xx\/xxx\/xxxxxx\/user\/xxxxxx\/htdocs\/example.com
\n\/home\/content\/xx\/xxxxxx\/html\/example.com
\n\/home\/xxxx\/domains\/example.com\/html\/example.com<\/p>\n

<\/a><\/p>\n

Do I need to create a custom php.ini file for each of my websites?<\/span><\/h2>\n

No (unless your Web Host requires multiple php.ini files per directory – most Hosts do not require this). You only need to create 1 custom php.ini file per Hosting Account. If you have 1 website or 100 websites under your Hosting Account then you only need to create 1 custom php.ini file to protect all of your websites under your Hosting Account. Some web hosts require that you create or add your custom php.ini file in your Document Root folder and other web hosts require that you add your custom php.ini file in another folder location. Please see this post and locate your particular web host to see exactly where your web host requires that you create or add custom php.ini files – custom php.ini Host Specific Information<\/a>\u00a0. \u00a0 If you have multiple separate Hosting Accounts for your particular Web Host then for each separate Hosting Account you would only need to create 1 custom php.ini file for each separate Hosting Account. If you are not sure what this means then please see What is my Hosting Account Name?<\/strong> for examples of separate Hosting Accounts.<\/p>\n

<\/a><\/p>\n

Does each website need to have its own PHP Error log?<\/span><\/h2>\n

If you use ini_set Options you can create separate PHP Error Logs for each of your websites.<\/p>\n

If you create a custom php.ini file (PHP5.2.x) or .user.ini file (PHP5.3.x) the path to your php error log can be\u00a0overridden\u00a0by using ini_set Options on an individual website. \u00a0If you do not use ini_set Options then the path in your php.ini or .user.ini file will be applied to all of your websites under your Hosting Account and all of your websites will log php errors to 1 php error log file.<\/p>\n

IMPORTANT NOTE 4-1-2013: \u00a0<\/strong><\/span><\/p>\n

It appears that most web hosts are not choosing to use FastCGI and .user.ini files instead of php.ini files by default for PHP5.3.x and higher versions. I assume this is because of the known problematic issues that come with FastCGI and PHP applications such as WordPress, Joomla, etc. In regards to BPS Pro directly I have noticed that using the automated P-Security php.ini tools to create custom php.ini files causes the custom php.ini file to be ignored\/rejected or worse. At this time the best method to create a custom php.ini file if your PHP Server version is 5.3.x or higher is to manually create the custom php.ini file using the setup steps in this Forum Topic: http:\/\/forum.ait-pro.com\/forums\/topic\/custom-php-ini-file-setup-php5-3-x\/<\/a>.<\/p>\n

To simplify this setup a new tool will be added to P-Security that will copy the Server’s Default php.ini file to the Document Root folder. Manually editing of the custom php.ini file will still be required since automating this process causes the Server to reject\/ignore the custom php.ini file, but a simpler manual editing method will created when the new tool is created in P-Security. Pending for BPS Pro 5.8.<\/p>\n

Using the same ini_set Options php error log path for all of your websites to log php errors to 1 php error log file<\/strong><\/p>\n

On the ini_set Options page enter in the php error log path that you would like to use in the ini_set PHP Error Log Location Set To: option setting. \u00a0Click the Save Options button, Click the Enable Options button, after clicking the Enable Options button you will see this success message displayed – Your ini_set Options have been Enabled successfully, Click the Refresh Status button,\u00a0After clicking the Refresh Status button. Go to the PHP Error Log tab page. Copy the Error Log Path Seen by Server: file path to the PHP Error Log Location Set To: text box and click the Set Error Log Location button.<\/p>\n

Using the same php.ini or .user.ini php error log path for all of your websites to log php errors to 1 php error log file<\/strong><\/p>\n

This example is assuming that you have created this php error log path in your custom php.ini file or .user.ini file – \/home\/content\/xx\/xxxxxx\/html\/websiteA\/wp-content\/plugins\/bulletproof-security\/admin\/php\/bps_php_error.log<\/p>\n

I have copied the P-Security PHP Error Log page options for choosing your PHP Error Log Location. In the example I am on a website called websiteB and the Default BPS Error Log Location:\u00a0<\/strong> folder path displays the location of the PHP Error Log file for this site. This example also displays that websiteA is the location I have chosen for my PHP Error Log Location for both websiteA and websiteB. I am not using the websiteB folder location because I want all of my websites to use the websiteA PHP Error Log file to log php errors too. If I had another website named websiteC then I would also choose the websiteA PHP Error Log Location folder path. This would mean that websiteA, websiteB and websiteC would all log php errors to the 1 PHP error log file located in the websiteA folder location.<\/p>\n

IMPORTANT: <\/strong>BPS performs a check that compares your PHP Error Log Location Set To:\u00a0<\/strong> and Error Log Path Seen by Server:\u00a0<\/strong> folder paths to ensure that your PHP error log path has been added to your custom php.ini file and that the folder path is correct. If these 2 folder paths do not match then BPS will display an error message informing you that these 2 folder paths do not match. Check that the folder path you added in your custom php.ini file matches the PHP Error Log Location Set To:\u00a0<\/strong> folder path the added. For additional sites that you are installing BPS on copy the Error Log Path Seen by Server:\u00a0<\/strong> folder path to the PHP Error Log Location Set To:\u00a0<\/strong> text box and click the Set Error Log Location button.<\/p>\n

PHP Error Log Location<\/strong><\/p>\n

ini_set PHP Error Log Location (Recommended):<\/strong> \/home\/content\/xx\/xxxxxx\/html\/websiteB<\/span>\/wp-content\/bps-backup\/logs\/bps_php_error.log
\nDefault BPS Error Log Location:\u00a0<\/strong>\/home\/content\/xx\/xxxxxx\/html\/websiteB<\/span>\/wp-content\/plugins\/bulletproof-security\/admin\/php\/bps_php_error.log<\/p>\n

PHP Error Log Location Set To:\u00a0<\/strong> \/home\/content\/xx\/xxxxxx\/html\/websiteA<\/span>\/wp-content\/plugins\/bulletproof-security\/admin\/php\/bps_php_error.log
\nError Log Path Seen by Server:\u00a0<\/strong>\/home\/content\/xx\/xxxxxx\/html\/websiteA<\/span>\/wp-content\/plugins\/bulletproof-security\/admin\/php\/bps_php_error.log<\/p>\n

 <\/p>\n

<\/a><\/p>\n

Partial List of Web Hosts that BPS Pro has been installed on and custom php.ini file requirements<\/span><\/h2>\n

This is a list of Web Hosts that we have personally installed BPS Pro on. If you would like to have your Web Host added then please send us an email.<\/p>\n

BPS Pro will automatically detect your web host if it is listed below and will automatically create \/ write your custom php.ini handler code to your Root .htaccess file (if your web host is listed below and your web host requires this code and if your PHP version is PHP5.2.x.). \u00a0If you do not see your web host listed here please send us an email and we will set up your custom php.ini file for your particular Web Host and add your web host to the list. \u00a0If you have a Private Name Server or are using CloudFlare or are using Pipe DNS or some other DNS service that changes, hides or masks your true Web Host then you will need to add your php.ini handler code into B-Core Custom Code. \u00a0The B-Core Custom Code feature allows you to add and permanently save any custom .htaccess code that you want to have automatically created in your Root .htaccess file with B-Core AutoMagic. \u00a0To use Custom Code go to B-Core Custom Code, add your custom .htaccess code (php.ini handler code and \/ or other miscellaneous custom .htaccess code), save it and then use AutoMagic to create new Master .htaccess files. \u00a0You should then check to see if your custom .htaccess code was created in the Master .htaccess files by looking at the B-Core Edit\/Upload\/Download page and look at the secure.htaccess file Tab. \u00a0If it is correct then you would then Activate BulletProof Modes.<\/p>\n

NOTE:<\/strong><\/span> \u00a0The Web Hosts List is assuming that you have Shared Web Hosting. \u00a0If you have VPS or Dedicated Hosting then you will have direct access to the Default Server php.ini file and you will be able to upload a new custom php.ini file using SSH. \u00a0You can use the Php.ini Master File Maker to create your new custom php.ini file and then upload it to your VPS or Dedicated Server using SSH. \u00a0See BPS Pro VPS or Dedicated Custom php.ini File Help<\/a>. \u00a0If you have a Web Host that does not allow adding a custom php.ini file for Shared Hosting then you can upgrade to VPS or Dedicated Hosting or just find another Web Host that does allow custom php.ini files for Shared Hosting or just set up the BPS Pro PHP error logging to use the Default Server PHP Error log location, which is usually error_log by default on most Web Hosts.<\/p>\n

NOTE:<\/strong><\/span> \u00a0If your PHP version is PHP5.3.x or above use the BPS Pro ini_set Options to setup your PHP Error log. \u00a0To create a custom php.ini file for your website see this Forum Topic: \u00a0http:\/\/forum.ait-pro.com\/forums\/topic\/custom-php-ini-file-setup-php5-3-x\/<\/a>.<\/p>\n

Click the Show button below for Table Column Abbreviation information. \u00a0Click on the Host name to go to custom php.ini setup steps or ini_set setup steps for that Host.\u00a0<\/strong><\/span><\/p>\n

IS<\/strong><\/span> = ini_set Options will allow you to set your PHP configuration settings on web hosts that do not allow custom php.ini files to be created. Using ini_set Options also provides a solution to the known WordPress\/FastCGI problem. For first time installations of BPS Pro it is recommended that you use the ini_set Options to quickly setup your PHP Error Log file and location. The ini_set Options can be used as an alternative to creating a custom php.ini file or .user.ini file (if your PHP version is PHP5.3.x or above) or in addition to creating a custom php.ini file or .user.ini file (if your PHP version is PHP5.3.x or above).<\/p>\n

php.ini handler<\/strong><\/span> = Either requires custom php.ini .htaccess code in your Root .htaccess file or not. BPS automatically creates \/ writes this code into your Root .htaccess file with AutoMagic if your Web Host is listed below, your PHP version is 5.2.x (if your PHP version is 5.3.x BPS will NOT automatically create your php.ini handler code) and your Web Host requires this code. If you have a Private Name Server or are using CloudFlare or are using Pipe DNS or some other DNS service that changes, hides or masks your true Web Host then you will need to add your php.ini handler code into B-Core Custom Code.<\/p>\n

BPSA<\/strong><\/span> = BPS automatically writes the custom php.ini handler code to your Root .htaccess file (if your web host requires custom php.ini handler code) when you click the AutoMagic buttons in B-Core to create your Master .htaccess files \u00a0if your Web Host is listed below, your PHP version is 5.2.x (if your PHP version is 5.3.x BPS will NOT automatically create your php.ini handler code)\u00a0. \u00a0As of BPS Pro 5.1.5 a new feature called Custom Code has been added. \u00a0You can now add your Host’s php.ini handler code in the Custom Code Top box if you see CC listed under the BPSA column. \u00a0If you have a Private Name Server or are using CloudFlare or are using Pipe DNS or some other DNS service that changes, hides or masks your true Web Host then you will need to add your php.ini handler code into B-Core Custom Code.<\/p>\n

CP<\/strong><\/span> = Requires cPanel or Control Panel setting or configuration change.<\/p>\n

CT<\/strong><\/span> = Combined Total of all php.ini files. Some web hosts use a combined total of all the php.ini files in your Hosting Account. The Server’s default php.ini file and your custom php.ini file will both be looked at and a combined total of both of these files will be applied to all your websites under your Hosting Account. Your custom php.ini takes priority over the Server’s default php.ini file and the BPS Pro optimum security and performance settings will be applied to your websites instead of the Server’s default php.ini file settings. Important!<\/strong> If your Web Host is using this Combined Total php.ini method then DO NOT<\/strong> use your Host’s default php.ini file as your new custom php.ini file. What will happen is that php.ini Modules will be loaded twice and your website will crash. php.ini Modules can only be loaded once and both your Server’s default php.ini file and your custom php.ini file will load the php.ini Modules.<\/p>\n

SA<\/strong><\/span> = Stand Alone php.ini file. Some web hosts use a stand alone custom php.ini set up method. Only 1 php.ini file is looked at as the Loaded Configuration file (php.ini file) for your Hosting Account and these php.ini settings will be applied to all your websites under your Hosting Account. Your custom php.ini file should contain all of your Web Host’s default php.ini files settings and have the BPS Pro optimum security and performance settings added into it.<\/p>\n

SA\/CT<\/strong><\/span> = This Host allows both a Stand Alone and a Combined Total method for custom php.ini files. \u00a0If php.ini Modules exist in both a custom php.ini file and the Server Default php.ini file they will NOT be loaded twice.<\/p>\n

S<\/strong><\/span> = Single custom php.ini file used for an entire Hosting Account to protect all websites under that Hosting Account. Most web hosts require that you create a single custom php.ini file for your entire Hosting Account and it is usually created in your Document Root folder. Some web hosts require that you create your custom php.ini file in a specific folder other than your Document Root folder. See custom php.ini Host Specific Information<\/a> for host specific requirements by Web Host.<\/p>\n

M<\/strong><\/span> = Multiple php.ini files required per each directory \/ folder \/ website. Very few web hosts require this custom php.ini set up method. Some web hosts allow this as an option.<\/p>\n

Mo<\/strong><\/span> = Multiple php.ini files per directory is available as an option. The recommended set up for a custom php.ini file for your Hosting Account is to set up 1 custom php.ini file for your entire Hosting Account to protect all or your websites under your Hosting Account with that single custom php.ini file instead of creating multiple custom php.ini files per directory \/ folder \/ website.<\/p>\n

DR<\/strong><\/span> = Your custom php.ini file is created in your Document Root folder for your Hosting Account (not Document Root folder per website). If your web host requires that you add \/ create your custom php.ini file in your Document Root folder then any additional custom php.ini files that you add in other folders will not be seen by your Server.<\/p>\n

HS<\/strong><\/span> = Your custom php.ini file is created in a folder that is specified by your Web Host. If you web host requires that you add \/ create your custom php.ini file in a folder that they specify then it will not be seen by your Server if you create a custom php.ini file in your Document Root folder. Note:<\/strong> This folder location could be one folder above your Document Root folder, which is your Hosting Account Root folder.<\/p>\n

PD<\/strong><\/span> = Custom php.ini files are created per directory \/ folder \/ website folder. This is ONLY for Web Hosts that require that you create your mulitple custom php.ini files for each directory and do not allow a single site-wide custom php.ini file in your Document Root folder.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Host<\/strong><\/span><\/td>\nIS<\/strong><\/span><\/td>\nphp.ini handler<\/strong><\/span><\/td>\nBPSA<\/strong><\/span><\/td>\nCP<\/strong><\/span><\/td>\nCT\/SA<\/strong><\/span><\/td>\nS\/M\/Mo<\/strong><\/span><\/td>\nDR\/HS\/PD<\/strong><\/span><\/td>\n<\/tr>\n
1&1<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
4UHosting<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
AptHost<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Arvixe<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
AussieHQ<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Blacknight Solutions<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
BlueHost<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
BrainHost<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
Canadian Web Hosting<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nCT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Canvas Dreams<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
CiviHosting<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR11<\/sup><\/td>\n<\/tr>\n
Clook<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nCT<\/td>\nS<\/td>\nDR9<\/sup><\/td>\n<\/tr>\n
Compitent Web Hosting<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo*<\/td>\nSA\/CT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Continuum Data Center<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo*<\/td>\nSA\/CT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
DreamHost<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA\/CT<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
Host<\/strong><\/span><\/td>\nIS<\/strong><\/span><\/td>\nphp.ini handler<\/strong><\/span><\/td>\nBPSA<\/strong><\/span><\/td>\nCP<\/strong><\/span><\/td>\nCT\/SA<\/strong><\/span><\/td>\nS\/M\/Mo<\/strong><\/span><\/td>\nDR\/HS\/PD<\/strong><\/span><\/td>\n<\/tr>\n
eUKhost<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A7<\/sup><\/td>\n<\/tr>\n
EZPZ Hosting<\/a><\/td>\nYes<\/td>\nFlag\/Value<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nFlag\/Value<\/td>\n<\/tr>\n
FastDomain<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
GigaPros<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
GoDaddy<\/a><\/td>\nYes<\/td>\nYes1<\/sup><\/td>\nYes1<\/sup><\/td>\nYes1<\/sup><\/td>\nSA\/CT1<\/sup><\/td>\nS1<\/sup><\/td>\nDR 1<\/sup><\/td>\n<\/tr>\n
GVO Hosting<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
Hawk Host<\/a><\/td>\nYes<\/td>\nFlag\/Value<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nFlag\/Value<\/td>\n<\/tr>\n
Heart Internet Ltd<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes8<\/sup><\/td>\nCT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Host Europe GmbH<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Host The Name<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nCT<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
HostDime<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
HostGator<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
Hosting 2GO<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nHS3<\/sup><\/td>\n<\/tr>\n
HostMedia<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A7<\/sup><\/td>\n<\/tr>\n
HostMonster<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
Host<\/strong><\/span><\/td>\nIS<\/strong><\/span><\/td>\nphp.ini handler<\/strong><\/span><\/td>\nBPSA<\/strong><\/span><\/td>\nCP<\/strong><\/span><\/td>\nCT\/SA<\/strong><\/span><\/td>\nS\/M\/Mo<\/strong><\/span><\/td>\nDR\/HS\/PD<\/strong><\/span><\/td>\n<\/tr>\n
HostUpon<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nCT<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
ICDSoft<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR11<\/sup><\/td>\n<\/tr>\n
Infonet.com.br<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
InMotion<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
InoxHost<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nCT<\/td>\nM<\/td>\nPD2<\/sup><\/td>\n<\/tr>\n
IT Comtech<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
IX Web Hosting<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA++<\/td>\nS++<\/td>\nHS++<\/td>\n<\/tr>\n
Jumba<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
JustHost<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR5<\/sup><\/td>\n<\/tr>\n
KnownHost<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
LiquidNet Ltd<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
Lunarpages<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA\/CT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
MDDHosting<\/a><\/td>\nYes<\/td>\nFlag\/Value<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nFlag\/Value<\/td>\n<\/tr>\n
MediaLayer<\/a><\/td>\nYes<\/td>\nFlag\/Value<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nFlag\/Value<\/td>\n<\/tr>\n
MediaTemple<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA\/CT<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
Host<\/strong><\/span><\/td>\nIS<\/strong><\/span><\/td>\nphp.ini handler<\/strong><\/span><\/td>\nBPSA<\/strong><\/span><\/td>\nCP<\/strong><\/span><\/td>\nCT\/SA<\/strong><\/span><\/td>\nS\/M\/Mo<\/strong><\/span><\/td>\nDR\/HS\/PD<\/strong><\/span><\/td>\n<\/tr>\n
Namecheap<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD6<\/sup><\/td>\n<\/tr>\n
Netfirms<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nM<\/td>\nPD<\/td>\n<\/tr>\n
netINS<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A7<\/sup><\/td>\n<\/tr>\n
Network Solutions<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA\/CT<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
Open Host<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
pair Networks<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
ProudHosts<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A7<\/sup><\/td>\n<\/tr>\n
Routhost<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
SAKURA Internet<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
SEO Hosting<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n
ServInt<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo*<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Shopaserver<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
SingleHop<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
SKGOLD<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA<\/td>\nS<\/td>\nHS<\/td>\n<\/tr>\n
SoftLayer Inc<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Host<\/strong><\/span><\/td>\nIS<\/strong><\/span><\/td>\nphp.ini handler<\/strong><\/span><\/td>\nBPSA<\/strong><\/span><\/td>\nCP<\/strong><\/span><\/td>\nCT\/SA<\/strong><\/span><\/td>\nS\/M\/Mo<\/strong><\/span><\/td>\nDR\/HS\/PD<\/strong><\/span><\/td>\n<\/tr>\n
StableHost<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
Strato<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
Sub 6 Limited<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nCT<\/td>\nS<\/td>\nDR9<\/sup><\/td>\n<\/tr>\n
TMDHosting<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
Tsohost<\/a><\/td>\nYes<\/td>\nYes<\/td>\nCC<\/td>\nNo<\/td>\nCT<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
UberGlobal<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
UK2<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nNo<\/td>\nSA<\/td>\nS<\/td>\nDR<\/td>\n<\/tr>\n
UOL Host<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
Web Drive<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A4<\/sup><\/td>\n<\/tr>\n
Webmasters.com<\/a><\/td>\nYes<\/td>\nNo<\/td>\nN\/A<\/td>\nYes<\/td>\nSA<\/td>\nS<\/td>\nPD10<\/sup><\/td>\n<\/tr>\n
WestHost<\/a><\/td>\nYes<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A<\/td>\nN\/A7<\/sup><\/td>\n<\/tr>\n
WiredTree<\/a><\/td>\nYes<\/td>\nYes<\/td>\nYes<\/td>\nNo*<\/td>\nSA<\/td>\nS\/Mo<\/td>\nDR<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

*<\/strong><\/span> Requires that your website is configured for suPHP. \u00a0suPHP is usually the default PHP configuration. \u00a0If your Server API is CGI under BPS System Info then your website is most likely configured for suPHP.
\n++<\/strong><\/span> IX Web Hosting requires that an IX Tech creates your initial custom php.ini file, which you can then edit.
\n1<\/sup><\/strong><\/span>\u00a0GD Linux Shared Hosting may require that you do an additional Control Panel step – Kill Web System Processes on Linux Shared Hosting Accounts<\/strong>\u00a0\u00a0in order to see your new custom php.ini settings. \u00a0Click to view php.ini set up steps for GoDaddy<\/a>.
\n2<\/sup><\/strong><\/span>\u00a0This Host requires that you create your custom php.ini file in cPanel. In cPanel under 1H Software – PHP Variables Manager you must choose –\u00a0Apply changes to all sub-directories?<\/strong>. Click to view php.ini setup steps for InoxHost.<\/a>
\n3<\/sup><\/strong><\/span>\u00a0This Host is currently using an older MySQL DB Version. \u00a0Please contact AITpro for additional assistance.
\n4<\/sup><\/strong><\/span>\u00a0This Host does not allow you to create custom php.ini files for Shared Hosting. \u00a0Use ini_set Options.
\n5<\/sup><\/strong><\/span>\u00a0This Host uses Pipe DNS to hide your true Name Servers. This means BPS cannot detect your true Name Server. You will need to manually enter your php.ini handler code into your Root .htaccess file. Click to view php.ini setup steps for JustHost.<\/a>
\n6<\/sup><\/strong><\/span>\u00a0This Host has the Suhosin-Extension installed, but the suhosin.executor.func.blacklist directive is not being used. Click to view php.ini setup steps for Namecheap.<\/a>
\n7<\/sup><\/strong><\/span>\u00a0This Host has PHP5.3.x with Zend Guard Loader. \u00a0Use ini_set Options.
\n8<\/sup><\/strong><\/span>\u00a0This Host has both PHP 5.3.x Zend Guard Loader and PHP 5.2.x Zend Optimizer available to choose from. In order to create a custom php.ini file you will need to set your environment to PHP5.2 using the “Switch PHP Versions” tool in eXtend. You cannot create a custom php.ini file if your Server is using PHP 5.3.x Zend Guard Loader and .user.ini files currently have a known ongoing issue – PHP5.3.x .user.ini Known Problem & Solutions<\/a>. Click to view php.ini setup steps for Heart Internet.<\/a>
\n9<\/sup><\/strong><\/span>\u00a0This Host is using PHP 5.3.x with Zend Guard Loader and requires that you use .user.ini instead of a php.ini file. \u00a0Click to view Web Hosts php.ini and .user.ini setup steps.<\/a>
\n10<\/sup><\/strong><\/span>\u00a0This Host requires that you create your custom php.ini file using the [PHP Manager] tool in the control panel. There are a few settings that are not available in the control panel [PHP Manager] Tool and if you ask nicely your Host will add these additional settings for you.
\n11<\/sup><\/strong><\/span>\u00a0This Host requires that you create your custom php.ini file in your control panel using the PHP Control Panel feature.
\nFlag\/Value<\/strong><\/span> – This Host has a LiteSpeed SAPI w\/DSO and php_flag and php_value can be added to the Root .htaccess file using the B-Core Custom Code feature. \u00a0Click to view php_flag and php_value setup steps for Hawk Host.<\/a>
\nP<\/strong><\/span>\u00a0– Pending – php.ini handler code will be added in the next release of BPS Pro. \u00a0The new BPS Pro Custom Code feature allows you to add your Host’s php.ini handler code.
\nCC<\/strong><\/span>\u00a0= Custom Code. \u00a0Add the php.ini handler code for your Web Host in the \u00a0

 <\/p>\n

<\/a><\/p>\n

Why am I seeing PHP errors and what do they mean?<\/span><\/h2>\n

BPS is alerting you that php errors have occurred on your website and logging these errors. BPS is not generating these php errors. In general php errors are a natural thing that will occur on every website intermittently.\u00a0What is not natural or normal is to see the same php error happening repetitively and continuously. Logged\u00a0PHP errors should be considered as helpful. PHP errors very accurately display exactly where coding issues or problems are occurring on your website that need to be either looked into or fixed. \u00a0Fatal php errors need your immediate attention and should be fixed right away.<\/p>\n

PHP Error Types\/Levels\/Severity<\/strong><\/span><\/p>\n

Strict –\u00a0<\/strong><\/span>PHP will suggest making changes to the code which will ensure the best interoperability and forward compatibility of the code.
\nNotice –\u00a0<\/strong><\/span>Run-time notices. Indicate that the script encountered something that could indicate an error, but could also happen in the normal course of running a script.
\nParse –\u00a0<\/strong><\/span>Compile-time parse errors. Parse errors should only be generated by the parser. Indicates a syntax error in the code.
\nWarning –\u00a0<\/strong><\/span>Run-time warnings (non-fatal errors). Execution of the script is not halted.
\nFatal –\u00a0<\/strong><\/span>Fatal run-time errors. These indicate errors that cannot be recovered from, such as a memory allocation problem. Execution of the script is halted.<\/p>\n

Repetitive or continuous php errors usually means that there is a problem with some coding in a plugin or theme (common issue\/problem) and can also mean that there is a conflict with the BPS security settings in your custom php.ini file (rare issue\/problem). If you see that a php error is happening over and over again repeatedly you can usually see what the problem is from the error that is logged. If the php error is not obvious you can Google the php error message to find out what it could mean. Copy the portions of the php error that contain the error level, the error description and file name and code line into the Google search window and search for what the error means and the solution. Example: \u00a0PHP Fatal error: Call to undefined function w3_url_format() in\u00a0PgCacheAdmin.php on line 213. Do not include your website path in your Google search because the search will probably not return any search results since your website path is unique to only your website.<\/p>\n

php.ini settings in your custom php.ini file can sometimes cause issues\/problems with some plugins or themes that may need to use one of the risky or dangerous php functions in a way that appears to BPS as attack against your website. In general BPS starts from the maximum security settings and then allows you to decrease that security on an as needed basis. Example: \u00a0If a plugin or theme needs to use one of these php functions – allow_url_fopen or register_argc_argv, which are set to Off by default in your custom php.ini file, then you would simply need to set them to On. BPS has several layers of overlapping security protection and fallbacks so if you need to allow a php function that is disabled in the disable_functions directive or set to Off in your custom php.ini file this can be done safely without any significant security risk.<\/p>\n

Another thing that can generate repetitive php errors in your php error log is that a hacker is repetitively trying to exploit some code that may have a known vulnerability in that coding.<\/p>\n

The important thing to note with php errors is that intermittent php errors are considered normal and repetitive or continuous php errors are not normal. So when BPS alerts you that a php error has been logged in your php error log, you want to take a look at the php error in your php error log and if it does not appear to be a serious problem or is just an intermittent php error you can then just click the Reset Last Modified Time in DB button to make the BPS php error notification go away. Php errors are logged by date in descending order. Your php error log is a static log file and php errors will remain in your php error log file until you manually delete them. It is completely up to you to decide whether or not you want to keep these php errors in your log file or delete them.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Frequently Asked Questions About Custom php.ini files, .user.ini files, PHP errors, Partial List of Web Hosts that BPS Pro has been installed on, General website and Hosting terms. What is my Hosting Account Name? What is my Document Root Folder? Do I need to create a custom php.ini file for each of my websites? Does […]<\/p>\n","protected":false},"author":167,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[393],"tags":[469,473,470,472,471],"class_list":["post-3576","post","type-post","status-publish","format-standard","hentry","category-bulletproof-security-pro","tag-custom-php-ini-faq","tag-custom-php-ini-php-errors","tag-custom-php-ini-terms","tag-general-hosting-terms","tag-general-website-terms"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/posts\/3576","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/users\/167"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/comments?post=3576"}],"version-history":[{"count":0,"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/posts\/3576\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/media?parent=3576"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/categories?post=3576"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ait-pro.com\/aitpro-blog\/wp-json\/wp\/v2\/tags?post=3576"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}