allow_url_fopen: Google Maps API - Bad coding or Difficult host?

[Colink2]

I have limited coding skills, even less cPanel skills. I am stuck between a developer and web host.

I am keen to know if my developer needs to be using different coding or my web host has unreasonable security protocols in place,

My developer requires at least 2 of the following features enabled - allow_url_fopen, allow_url_include or ini_set (not sure which 2).

php.ino has the following settings
allow_url_fopen = On
allow_url_include = On

His code for connecting to Google Maps API worked fine until my Web Host moved me to a newer server, now one page is being blocked and web host is inflexible. This page sends an address to google via the Maps API, to return Lat, Lng values.

I have copied the code to another web host and all is back to what it was.

Web original web host blames developer, developer blames web host. Should the developer be using different code that does not require allow_url_fopen, allow_url_include or ini_set?

Old server: Centros 6.9, New server Centros 7.1 Both using PHP 5.6 and MySQL 5.6.35

 

[cPanelMichael]

Hello,

You'd have to check with your hosting provider to see if they have added ini_set to the disable_functions list in the PHP configuration file on the system. If so, your developer should be able to use an alternate method of fetching the required data, like the method mentioned on the StackOverflow thread:

Are server security restrictions causing issues with allow_url_fopen & allow_url_include

Thank you.