Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@bittersweet the god of Laravel, or so.
-
@bittersweet thanks. I will check that.
I saw the mistake, too. But it was too late to edit. But thanks for the answer. Now I understand life better. -
@bittersweet should be Platupi, no?
-
@bittersweet Platitudes
-
@bittersweet @sjw-brah platyporum.
-
@bittersweet thanks man, that totally was the solution. I didn't even know about that file. :D
-
@Wombat No problem... I'm also pretty sure it's platypuddings.
-
@bittersweet 😂 u win.
-
@Wombat
So did we discuss the fuss about Platypus? Is it unanimous or did it sadden us? Gelatinous platypuddings twiddle their middleware with little care, platipodes... codes.... fuck this I'm too high... craving platupie 🍰 -
@bittersweet you are poet, also? 🤔
-
@Wombat Everyone is.
This happens when production issue comes between Onam (Hindu festival) celebration.
Render issues IRL
I have an issue with my Laravel routing. Can you help me out, @bittersweet?
I have a custom "/home" route called "/admin" and I set the protected property in the LoginController:
$redirectTo = "/admin";
And it works fine, if I log in from guest. But when I navigate to "/login" as auth-user it still redirects me to "/home".
What the fuck is this? What do I have to change to make this work? Who has to be fucked? Is it possible to solve this without sacrificing a virgin at bloodmoon? And why are Platypus so fucking ugly?
question
routing
issue
laravel