Redirection customization about fortify

[nadhifikbarw]

Here's a simple workaround if you need to implement it right now. However I would too absolutely prefer much more cleaner solution, such as adding new dedicated config key would be the easiest implementation, but for now this should do.

---

Add new config key in config/fortify.php

'registered' => '/onboarding',

or you could also make it use RouteServiceProvider const

// app/providers/RouteServiceProvider.php
public const REGISTERED_REDIRECT = '/onboarding'


// app/config/fortify.php
'registered' => App\Provider\RouteServiceProvider::REGISTERED_REDIRECT,

Create new class App\Responses\RegisterResponse

<?php

namespace App\Responses;

use Illuminate\Http\Response;
use Laravel\Fortify\Contracts\RegisterResponse as RegisterResponseContract;

class RegisterResponse implements RegisterResponseContract
{
    public function toResponse($request)
    {
        return $request->wantsJson()
            ? new Response('', 201)
            : redirect(config('fortify.registered'));
    }
}

Bind new interface implementation inside FortifyServiceProvider.php

use App\Responses\RegisterResponse;
use Laravel\Fortify\Contracts\RegisterResponse as RegisterResponseContract;

/**
* Register any application services.
*
* @return void
*/
public function register()
{
    $this->app->bind(
        RegisterResponseContract::class,
        RegisterResponse::class
    );
}

[rafayrty]

Hi There Add This To The Route File It Should Work.

Route::get('/login',function(){
    return redirect()->route('index');
})->name('login');

[fantomas-code]

Ya lo solucione ....
en el archivo RouteServiceProvider.php escribi esta linea

public const LOGOUT_REDIRECT = '/login'; <------ que redirecciona al login

luego en el archivo fortify.php la mande a llamar con el nombre 'salir'

luego cree una carpeta llamada Responses dentro de la carpeta app. Ahí cree un archivo llamado LogoutResponse.php y en ese archivo mande a llamar a la constante (no me queda claro si es constante o variable) con el nombre salir

[jonasvanderhaegen]

Using Laravel v8.9.0, On top of RouteServiceProvider:

/**
 * The path to the "home" route for your application.
 *
 * This is used by Laravel authentication to redirect users after login.
 *
 * @var string
 */
public const HOME = '/';

[taylorotwell]

Feel free to send a PR.

[sambindoff]

@c0nst4ntin that's exactly what @nadhifikbarw's suggestion above accomplishes, simply create a response class and bind this to the container as the Fortify register response.

[fantomas-code]

Hello, I would like to know how I can do to customize the redirection after logging out.
I see that by default it redirects you to the index of your project, I don't like that .. please help

[jimgwhit]

Custom redirection has been handled, see https://laracasts.com/discuss/channels/laravel/version-8-redirects

That was resolved immediately when laravel version 8 came out.

[Adhik13th]

i think its not like that

[joshmorel]

@jonasvanderhaegen this is okay for certain use cases. But imagine I wanted to customize further, e.g. redirect to a variable path after profile update (imagine -> profile/MyNewUserName)

[mrpritchett]

+1 for this feature request

[c0nst4ntin]

I'm not too familiar with this, but couldn't publishing single response classes or controllers and then having the possibility to overwrite these work? If so, is there a way?

[nadhifikbarw]

@betopicapiedra You could use the same method like my previous suggestion, but instead of rebinding the RegisterResponse contract, rebind the LogoutResponse contract instead.

[fantomas-code]

I already did what you suggested but it doesn't work
@nadhifikbarw

[victoralbino]

In the pull request implemented the possibility to perform some action after the user registers
Now it is only necessary to implement the afterRegister() method in the App\Actions\Fortify\CreatesNewUsers Class and what is in it will be executed after registration.

[nadhifikbarw]

@betopicapiedra Please use English so it's easier for everyone, but assuming from your screenshot, you haven't bind your LogoutResponse implementation with LogoutResponseContract via FortifyServiceProvider

[fantomas-code]

Ya esta solucionado ....gracias ...

It is already resolved, thank you ...