Nevermind.
I had to upgrade from Laravel 4.1.21 to the latest version (4.1.29).
This was a bug and at some point it was fixed.
I thought I did the upgrade but something went wrong with my deployment script and I just now realized the upgrade never happened.
Well, that was a little bit embarrassing but I'm glad this issue is now resolved.
I hope this helps someone in the future who might have a similar problem. Or forgets to upgrade. Or make sure he did...
Thank you! Was banging my head for a couple hours trying to figure out how to route to a *.domain.com and you fix pointed me in the correct direction.
Thanks for explaining the fix :)
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community