From c19742a031ccbaab2eae0363270b944ea26e17ad Mon Sep 17 00:00:00 2001 From: Ching Cheng Kang Date: Sat, 5 Nov 2022 15:41:49 +0800 Subject: [PATCH] Fix broken Link that link to freek's blog post --- docs/basic-usage/super-admin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basic-usage/super-admin.md b/docs/basic-usage/super-admin.md index d48ad254f..426bbc036 100644 --- a/docs/basic-usage/super-admin.md +++ b/docs/basic-usage/super-admin.md @@ -38,7 +38,7 @@ Jeffrey Way explains the concept of a super-admin (and a model owner, and model Alternatively you might want to move the Super Admin check to the `Gate::after` phase instead, particularly if your Super Admin shouldn't be allowed to do things your app doesn't want "anyone" to do, such as writing more than 1 review, or bypassing unsubscribe rules, etc. -The following code snippet is inspired from [Freek's blog article](https://murze.be/when-to-use-gateafter-in-laravel) where this topic is discussed further. +The following code snippet is inspired from [Freek's blog article](https://freek.dev/1325-when-to-use-gateafter-in-laravel) where this topic is discussed further. ```php // somewhere in a service provider