Laravel 5.4 :: Session to hold parent ID's

@Sven0188 If you have resourceful controllers, then you can just have a controller for uploading an item’s images and redirect to that:

// Items
Route::post('items', [
    'uses' => 'ItemController@store',
    'as' => 'item.store',
]);

// Item Images
Route::get('items/{item}/images', [
    'uses' => 'ItemImageController@index',
    'as' => 'item.image.index',
]);

Route::get('items/{item}/images/create', [
    'uses' => 'ItemImageController@create',
    'as' => 'item.image.create',
]);

Route::post('items/{item}/images', [
    'uses' => 'ItemImageController@store',
    'as' => 'item.image.store',
]);

class ItemController extends Controller
{
    public function store(CreateItemRequest $request)
    {
        $item = Item::create($request->all());

        return redirect()
            ->route('item.images.create', $item)
            ->withSuccess('Item created. Now add images.');
    }
}

class ItemImageController extends Controller
{
    public function index(Item $item)
    {
        $item->load('images');

        return view('item.image.index', compact('item'));
    }

    public function create(Item $item)
    {
        return view('item.image.create', compact('item'));
    }

    public function store(UploadImageRequest $request, Item $item)
    {
        $path = $request->image->store();

        $item->images()->create([
            'path' => $path,
        ]);

        return redirect()
            ->route('item.image.index', $item)
            ->withSuccess('Item image uploaded successfully.');
    }
}

you could do but your application will be confused if the user opens another tab and tries to perform similar functions in the other tab. This is because both tabs share the same session ID and therefore the same session variables

more common practice is to pass the id in the url, like /items/34/images

Thanks for both responses. Very valuable.

@martinbean: how would I manage to still use form request validation on my image controller? You example is very good and helpful but I was hoping I can still pass my form request to the controller methods? Or do I pass them as the first param and then the actual item as second object like:

    public function store(ItemImageCreateRequest $request, Item $item) {
        $item->images()->create($request->all());
}

Will this still be valid and working?

The order of the parameters in your controller actions does not matter. You just need to name the variables the same as the route parameters. Any other parameters will be pulled from the IOC container.

@Sven0188 Yes. I included a form request type-hint in my example. Laravel will then attempt to resolve the other parameters using route–model binding.

Aaah sorry my apologizes :) See your example does include request.