By roaming on

My host (Media Temple) announced that they will soon disable "allow_url_fopen" on their servers.
They also give a code line that a site can use to reverse the change in their default.
This is an issue I can can't find much info on through search.
Can anyone explain what exactly "allow_url_fopen" is, and what disabling it would do.
Thanks!

Comments

strawman’s picture

strawman commented

I wish I knew more about that end of things. I've already played with the sample php.ini file that media temple gave to me but when I upload it, the file crashes my site.
So Yes this would be a great help if anybody knows how to resolve this issue. I'm sure there's a few of us that are running Drupal on Media Temple.
If anyone can give a hand on this information that would be great. Thanks

strawman’s picture

strawman commented

so...after some research I found that what media temple is changing won't effect drupal sites at all unless you are running modules that use the "get_header" function. One in particular might be the private_upload module...here your own research will have to come in to figure out what modules use that function. There might be some other stuff but as it stands things should be god to go...
Media Temple also put up this page in order to give some ideas and work arounds.
http://kb.mediatemple.net/article.php?id=793

Hope this helps. If there is any other information that people have come across, please post them here. I may have missed some stuff in my research so if someone knows more then I do please post here.

Thanks

roaming’s picture

roaming commented

I read the Media Temple info page. They sent the link when they informed us of the change.
They are actually very good at working with their clients, and I expect that things should go smoothly.

Thanks for your info about what should be affected. That's exactly the kind of things that I have trouble finding.
I'm trying to find out as much as possible before I modify a file on a live site.
I'll be out on a job over the week-end, but at the beginning of next week I'll do the test they suggest and will post the results.

roaming’s picture

roaming commented

I just did the change in php.ini as suggested by Media Temple (and also renamed the file as required).
My sites are working fine, as far as I can see.
If anything shows-up later on that is not immediately obvious, I'll post it.
But right now it doesn't seem to affect anything (the way my sites are set).

syturvy’s picture

syturvy commented

I also did the test, and it worked fine.

I am using Drupal 5.5 with the following modules:
- i18n
- countdown
- captcha
- guestbook
- tinymce
- gmaps
- google analytics

roaming’s picture

roaming commented

Media Temple has now implemented the new settings and everything works fine for me.
I deleted the temporary line of code that I inserted in php.ini

Strawman, it's most probably one of your modules that causes that.
It wouldn't be a bad thing if Media Temple could make a list of the modules that are proven not to be a problem.

If this can help, in addition to the core modules, I have:
audio, boost, captcha, category, civicrm, extlink, formblock, formdefault, forms, image, img_assist, textimage, themsetingsapi, views, cck, advanced_forum.

They are not all in the same site, but none of them presents a problem right now.