Have you ever found that a WordPress plugin that works fine on one web host isn’t working as you would have expected when you move it to a new webhost? We recently experienced this with a plugin that reaches out to a remote server to collect XML data to be displayed by the plugin. The problem manifested itself as a blank page where the plugin’s shortcode SHOULD have displayed formatted version of the remote data.
The quickest way to diagnose issues like this is to modify the wp-config.php so that the line “define(‘WP_DEBUG’, false);” reads as “define(‘WP_DEBUG’, true);” temporarily so you can view the errors that WordPress by default will hide from you.
Doing so in this case returned the following error:
Warning: file_get_contents() [function.file-get-contents]: http:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/overthet/public_html/domainname.com/wp-content/plugins/someplugin/someplugin.php on line 37
By going back and searching the php.ini file in the root website for the phrase “allow_url_fopen” we were able to find the appropriate line and set it to read as follows: allow_url_fopen = On
A quick solution to a vexing problem. If you search for that in your local php.ini file and don’t find it, you might try adding the command to that file in order for this to take effect.
Do you have any other tips on tweaking your WordPress site using hte php.ini file? If so, use the comments below to post legitimate comments!
- Setting up SSL on Amazon Linux Instance under EC2 - July 26, 2018
- Method Chaining of Objects in C# - January 16, 2017
- Native SQL Backup And Restores on AWS RDS - November 9, 2016