Laravel 5 Basics (Twelve) - Certification

Laravel is shipped with a user authentication system. Let’s take a look at routes.php. If deleted, add:

<code>Route::controllers([
    'auth' => 'Auth\AuthController',
    'password' => 'Auth\PasswordController'
]);</code>

You can use php artisan route:list to check it out. Visit /auth/login in the browser and you will see the login interface. It is best to comment out the things about Google in the system default app.blade.php, otherwise you will go crazy.

You can use register, login or even forget password.

The actual registration of a user failed after submission. In fact, it did not fail, but larave automatically jumped to /home. We have deleted this controller. You can use tinker to see if the user has been created.

In fact trait is used in AuthAuthController, what is triat? Well, PHP only supports single inheritance, and traits were added in PHP5.4. A trait is actually an encapsulation of a set of methods, and you can include it in another class. Like an abstract class, you cannot instantiate it directly.

There is a reference to the trait in AuthAuthController:

<code>use AuthenticatesAndRegistersUsers;</code>

Let’s find him and see how he jumps after registration. He is hidden quite deep, in vendor/laravel/framework/src/Illuminate/Foundation/Auth/AuthenticatesAndregistersUsers.php, wow.

<code>	public function redirectPath()
	{
		if (property_exists($this, 'redirectPath'))
		{
			return $this->redirectPath;
		}
        
        //如果用户设置了 redirectTo 属性，则跳转到用户设置的属性，否则到home
		return property_exists($this, 'redirectTo') ? $this->redirectTo : '/home';
	}
</code>

OK, we know, just set the redirectTo attribute to customize the jump after registration. We modified in AuthAuthContotroller:

<code> protected $redirectTo = 'articles';</code>

We start by using /auth/logout to make sure we log out, don’t be afraid if something goes wrong, we don’t have a default homepage, revisit: auth/register to create a new user, this time it should be ok.

Logout again, and then use login to log in.

Now we can delete the temporarily set hidden fields in form_partial and modify the controller:

<code>    public function store(Requests\ArticleRequest $request) {
        //你可以这样
        //$request = $request->all();
        //$request['user_id'] = Auth::id();

        //更简单的方法
        $article = Article::create($request->all());
        //laravel 自动完成外键关联
        Auth::user()->articles()->save($article);

        return redirect('articles');
    }</code>

Add an article and check it out using tinker.

Middleware

Of course we don’t want anyone to be able to publish articles, at least only by logging in. We add protection in the controller:

<code>    public function create() {
        if (Auth::guest()) {
            return redirect('articles');
        }
        return view('articles.create');
    }</code>

The above code can work, but there is a problem. We need to perform the above processing in every method that needs to be protected. This is too stupid. Fortunately, we have middleware.

Middleware can be understood as a processing pipeline. The middleware processes at a certain moment in the pipeline. This moment can be a request or a response. Depending on the processing rules of the middleware, the request may be redirected or passed.

There are three middlewares included in app/http/middleware. You can tell what they are doing by their names. Check them carefully. Note that Closure $next represents the next middleware.

Register the middleware in app/http/kernel.php. The $middleware section declares middleware that processes all http, $routeMiddleware only processes routes, and you must explicitly declare that you want to use one or more of these middlewares.

Suppose we want to protect the entire ArticlesController, we add middleware directly in the constructor:

<code>    public function __construct() {
        $this->middleware('auth');
    }</code>

Now, any method is protected.

But we probably don’t want the entire controller to be protected, what if it’s just one or two of its methods? We can handle it like this:

<code>    public function __construct() {
        $this->middleware('auth', ['only' => 'create']);
        //当然可以反过来
        //$this->middleware('auth', ['except' => 'index']);
    }</code>

We don’t have to introduce middleware in the constructor of the controller, we can declare it directly in the route:

<code>Route::get('about', ['middleware' => 'auth', 'uses' => 'PagesController@about']);</code>

The system middleware provided in kernel.php, such as 'IlluminateFoundationHttpMiddlewareCheckForMaintenanceMode', can allow us to enter maintenance mode. For example, the system is online, but now it needs to be temporarily shut down for a period of time for processing. We can do it on the command line Processing, take a look at the work of this middleware:

<code>php artisan down</code>

Visit the website and you can see that any URL request will be returned immediately. Website online:

<code>php artisan up</code>

Let’s make our own middleware:

<code> php artisan make:middleware Demo</code>

Then add the code:

<code>	public function handle($request, Closure $next)
	{
        //如果请求中含有 foo，我们就回到控制器首页
        if ($request->has('foo')) {
            return redirect('articles');
        }

		return $next($request);
	}</code>

If you want to use middleware for all requests, you need to register it in $middleware in kernel.php:

<code>	protected $middleware = [
		...
		'App\Http\Middleware\Demo',

	];</code>

Now we can test it, let’s say we visit /articles/create?foo=bar and we are redirected to the home page.

Let’s get rid of this display middleware and let’s create a middleware that actually works. Suppose we want to protect a page. This page must be accessible by administrators.

<code>php artisan make:middleware RedirectIfNotAManager</code>

Let’s add the processing code:

<code>	public function handle($request, Closure $next)
	{
        if (!$request->user() || !$request->user()->isATeamManager()) {
            return redirect('articles');
        }

		return $next($request);
	}</code>

Modify our model below:

<code>    public function isATeamManager() {
        return false;
    }</code>

For simplicity, we return false directly. This time we place the middleware in $routeMiddleware in kernel.php.

<code>	protected $routeMiddleware = [
		...
		'manager' => 'App\Http\Middleware\RedirectIfNotAManager',
	];</code>

Let’s make a test route to test it:

<code>Route::get('foo', ['middleware' => 'manager', function() {
    return 'This page may only be viewed by manager';
}]);</code>

guest identity access or login identity access will return to the homepage, but if you modify isATeamManager() to return true, login identity access can see the returned information.

The above introduces the basics of Laravel 5 (Twelve) - Certification, including aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials.