FatalErrorException when calling action() with a non-existing route results is vacuous

[dhardtke]

In Laravel 4 you could easily see where in your code (template i.e.) you have called URL::action() and with what Controller and Method as parameter you called it, so you could easily find that and fix it...

now in Laravel 5, all you get is:

Call to a member function domain() on null

and the stack trace isn't helping either.

[GrahamCampbell]

Looks like you're using it wrong. Ask on the forums.

[dhardtke]

I don't think so, but thank you for closing the issue without asking for more details.

Anyway:
If I write this in my code:

action("DummyController@nonExisting");

I expect to get an exception that tells me where I called action() and with what parameters I called it and most importantly telling me, that it cannot find that route.
But I get

Call to a member function domain() on null

[GrahamCampbell]

but thank you for closing the issue without asking for more details.

I shouldn't need to ask. I should have just straight closed this without comment due to insufficient info.

[dhardtke]

Now you have the info.
In L4 we got a precise Exception, and now we get this rubbish...

[GrahamCampbell]

Your info means you are indeed using this wrong. That message you provided is the expected behaviour. Sorry.

[dhardtke]

http://laravel.com/docs/5.0/helpers#urls

action('HomeController@getIndex', []);

I am not using "action()" wrongly...

[siavash13]

I am suffering from the same issue as well, I have this {{ action('MyController@methodName') }}
which used to work in Laravel 4.2 but it doesn't work anymore in Laravel 5 and I get the following error
Call to a member function domain() on null

[siavash13]

my issue is solved now this error comes up when there is some namespace issue, for some reason I had to change the namespace in the action method the one which used to work for laravel 4 doesn't work for me

[mikerogne]

What OP is saying is that in L4 if you specified a route and it did not exist, it would throw an exception that the route does not exist. Whereas now, it fails in a much less-obvious way.

Can we please not close stuff without more than .02 seconds of thought? These are real issues that affect the community, and seriously a LOT of the folks are starting to feel shut out because of this type of behavior.

[dhardtke]

Alright, at least now theres #7424 going on