Function.realpath error due to open_basedir restrictions

Hey Jonathan, I'll do some testing to see if I can replicate this. Asset doesn't try to access any files outside the web directory so it should be playing nicely with open_basedir restrictions (if they are correctly set of course, which they appear to be in your case). I think this is happening because asset is trying to check "/", by which Drupal's base_path is meant of course, not the root of the server.

This has to do with sections of code like:

$asset->filepath = file_create_path($asset->dirname .'/'. $asset->filename);
$asset->url = file_create_url($asset->dirname .'/'. $asset->filename);

What happens when $asset->dirname is empty? You try to create a path at '/filename' which is outside of the allowed area. This throws the error.

I have a workaround for this. (Sorry, I have not had a chance to roll a patch for this yet.)

In asset_load of asset.module after the db_object_fetch and the check to make sure something loaded add the line that tests dirname and adds the / if it exists.

$asset = db_fetch_object(db_query('SELECT a.* FROM {asset} a WHERE '. $cond, $arguments));
if (!$asset) {
  return false;
}
$asset->dirname = $asset->dirname ? $asset->dirname .'/' : $asset->dirname; 

Then modify the filepath and url to look like:

$asset->filepath = file_create_path($asset->dirname . $asset->filename);
$asset->url = file_create_url($asset->dirname . $asset->filename);

A similar solution is needed where ever $form_values['parent'] is used with file_create_path. $form_values['parent'] may be empty.

Is it a good approach to modify $asset->dirname and $form_values['parent'] or should a new variable be created as a temp variable instead of the modification? Or should an if statement be used with:

$asset->filepath = file_create_path($asset->dirname . $asset->filename);
$asset->url = file_create_url($asset->dirname . $asset->filename);

????

I noticed this same problem in asset_bonus for embedded objects. Haven't traced the cause of it yet.

I have the problem in the 1.0-beta1 release. I'll roll a patch in the next day or so.

Attached is a patch that removes this error for me.

I'm moving this over to bugs and upping the priority to critical. If you don't have your directory structure setup (for example a first tie install) you will get these errors because there is no root dirname.

Committed to dev, thanks so much! You just brought Beta 2 a lot closer.