Resourceful controller broken after L4 update

[driesvints]

For some reason I can't get my resourceful controller back to work after updating L4. I updated both the framework through composer and development version at laravel/laravel.

I'm getting errors while doing (in a view):

URL::action('UsersController@show', array($user->id))

Error:

ErrorException: Warning: array_combine(): Both parameters should have an equal number of elements in
/foo/bar/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php line 185

I also can't seem to go to admin/users/1. It gives me a NotFoundHttpException:

I have my route set up as

Route::resource('admin/users', 'UsersController');

The resourceful controller was generated through artisan.

Can anyone perhaps help me out?

[JoostK]

Try using the following:

Route::group(array('prefix' => 'admin'), function()
{
    Route::resource('users', 'UsersController');
});

The prefix option was only introduced a couple of days ago.

[driesvints]

Ah yes now I see. I saw that it was added to the docs recently but didn't paid further attention to it. Should have tested that. Everything is working fine now again.

Thanks a lot!

[driesvints]

If I may ask.. what is the reason why this breaks backwards compatibility? And why should it be a convention on using the prefix option instead of prepending the prefix directly on the path?

[JoostK]

I don't actually know. The first argument to Route::resource really is the resource's name, not some path. I guess that's why it doesn't work.

It should be easy to extract every additional path segment and append it to the prefix, that would fix this issue.

[taylorotwell]

It's because we support nested resources. Also, resource controllers are new to L4 and L4 hasn't been released out of beta, so there really is no backwards compatibility to break.

[JoostK]

@taylorotwell Will you accept a PR to extract any additional path segments into prefix automatically? I understand why it doesn't currently work but it is probably easy to fix.