The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
So, if you have a form like:
for example, as part of a community photo gallery, you won't be able to process any photos uploaded via your scripts.
Similarly, if you've got an online shop where you could previously upload product photos, you'll find this no longer works either.
Freeola's response is: tough! If you don't like it, move your site to someone else!!!
Surprised? I definitely was.
A gold star for you all!
On the issue of file uploads we should be able to resolve this with the current measures and hopefully they will start working again in the next few days. Sorry for the inconvenience folks.
By the looks of it, that isn't strictly true - all it needed was a more carefully worded response that suggested that PHP was now going to run in safe mode and therefore any copying of files outside of my webspace wouldn't work, unless I updated the script, so maybe take a look at [... useful reference ...], etc.
Anyway - thanks for the explanation and clarification from everyone on here. Much appreciated.
Does this mean, however, that other uses of "copy" will now no longer work? e.g. If I had a "duplicate product" script that simply made a copy of an existing product's images (as the files being copied wouldn't be "just uploaded" files, so move_uploaded_file wouldn't work).
I'll read further on this but if you know off hand, that would be helpful.
> Warning: copy(): open_basedir restriction in effect.
> File(/var/tmp/phpRHJTJL) is not within the allowed path(s): ...
>
> Obviously, this could have a big effect on a number of sites -
> I'm going to have to transfer my sites across to a different
> hosting company...
Ah ok... I'd imagine you'll have some difficulty finding a host thats not running with open_basedir restrictions though. Most hosts these days run PHP in safe mode (which includes the open_basedir restrictions).
In this case it just appears to be a script using out of date methods. PHP has built in functions to deal with file uploads which arent affected by this problem, ie the script should be using move_uploaded_file instead of copy.
"Please be advised that we do not explicitly support PHP uploads. The upgrade we have made to the security of PHP has stopped these scripts from working. Unfortunately we have no current plans to fix this scripts in the near future."
I think the problem comes when you try to make a copy of an uploaded file (from /var/tmp) - typical error message that we get now (that we didn't before Freeola made their "security fix") is:
Warning: copy(): open_basedir restriction in effect. File(/var/tmp/phpRHJTJL) is not within the allowed path(s): ...
Obviously, this could have a big effect on a number of sites - I'm going to have to transfer my sites across to a different hosting company...
Can somebody from Freeola confirm this? I have a couple of Freeola hosted clients that this might impact.