aimeos/aimeos-laravel · error

abort( 404 );

Error message

abort( 404 );

What it means

The Aimeos ResolveController::indexAction() resolves a URL path via registered resolver functions (product, catalog, ...). It aborts with HTTP 404 when no path is present in the route or request input at all — i.e. the endpoint was hit without anything to resolve. The route/resolve controller requires a 'path' route parameter or '?path=' query/input parameter to work.

Solutions

1. Ensure the route to ResolveController includes a {path} placeholder, e.g. Route::get('/shop/{path}', ...)->where('path', '.*')
2. Call the endpoint with the path either as a route segment or as ?path=... query parameter
3. Check that any redirect/rewrite pointing to the resolve route actually forwards the original path
4. Compare your routes with the packaged aimeos-shop routes file after upgrades

Example fix

// before
Route::get('/resolve', [\Aimeos\Shop\Controller\ResolveController::class, 'indexAction']);
// after
Route::get('/resolve/{path}', [\Aimeos\Shop\Controller\ResolveController::class, 'indexAction'])->where('path', '.*');

$path = $request->route('path', $request->input('path'));
if( !is_string( $path ) || $path === '' ) {
    abort( 404, 'No path given to resolve' ); // fail fast before calling the controller
}

function hasResolvePath( \Illuminate\Http\Request $request ): bool {
    $path = $request->route( 'path', $request->input( 'path' ) );
    return is_string( $path ) && $path !== '';
}

try {
    return $controller->indexAction( $request );
} catch( \Symfony\Component\HttpKernel\Exception\NotFoundHttpException $e ) {
    if( !hasResolvePath( $request ) ) {
        return response()->view('errors.no-path', [], 404);
    }
    throw $e;
}

When it happens

Trigger: A request reaches the resolve route without a {path} route parameter and without a 'path' query/input parameter, so $request->route('path', $request->input('path')) returns null and abort(404) is raised at src/Controller/ResolveController.php:63.

Common situations: Route definition changed or was overridden without the {path} placeholder; a client or redirect calls the resolve endpoint without the path parameter; custom middleware/URL rewriting strips the path; upgrading Aimeos and copying an old route that doesn't pass 'path'.

Understand the failure class

Background: "missing required argument" and "the following required arguments were not provided": what required-argument errors mean and how to fix them — this error's family across 20 libraries.

Related errors

• abort( 404 );

AI-assisted analysis of aimeos/aimeos-laravel@9879c60332 (2026-09-12). Data as JSON: /api/errors/3acd0eda6d9a3f1a. Report an issue: GitHub.

Appendix: source

Thrown at src/Controller/ResolveController.php:63

			return $this->product( $context, $path );
		};

		self::$fcn['catalog'] = function( \Aimeos\MShop\ContextIface $context, string $path ) {
			return $this->catalog( $context, $path );
		};
	}


	/**
	 * Returns the html of the resolved URLs.
	 *
	 * @param \Illuminate\Http\Request $request Laravel request object
	 * @return \Illuminate\Http\Response Laravel response object containing the generated output
	 */
	public function indexAction( \Illuminate\Http\Request $request )
	{
		if( ( $path = $request->route( 'path', $request->input( 'path' ) ) ) === null ) {
			abort( 404 );
		}

		$context = app( 'aimeos.context' )->get( true );

		foreach( array_reverse( self::$fcn ) as $name => $fcn )
		{
			try {
				return call_user_func_array( $fcn->bindTo( $this, static::class ), [$context, $path] );
			} catch( \Exception $e ) {
				if( $e->getCode() !== 404 ) throw $e;
			}
		}

		abort( 404 );
	}


	/**

View on GitHub (pinned to 9879c60332)