fuel/core — pull request #1238 by iturgeon (2012-12-12 04:19:27+00:00)
Title: File move & copy methods require very loose areas

I tend to make my file areas pretty strict. This becomes a problem with the methods in File that can copy/move/rename between two endpoints.

If I need to copy a file from /fuel/app/uploads to /public/assets/img I need to make an area that is too lenient to enforce any real restriction.

For instance:

`public static function rename($path, $new_path, $area = null)`

The area sent would need to contain $path and $new_path. This may require that the area be the root of the entire project.

So my proposal is to add a second area argument to these methods that will allow the methods to operate in two strict areas.

This implementation should still support setting a single area making it backward compatible. The new area argument defaults to the first area.

I haven't tested this yet, just getting some feedback before I go off to bed.

Thoughts?

Signed-off-by: Ian Turgeon