```
### Login Redirect
Dalam `login-web` page layout, redirect selepas login berjaya:
```php
$redirect = "/" . request()->segment(1) . "/user-dashboard";
throw new HttpResponseException(redirect()->to($redirect));
```
---
## $_shared Object
`$_shared` adalah stdClass object yang disediakan oleh PortalHandler untuk berkongsi data antara Entry Script, Components, Page Content, dan Layout.
### Cara Kerja
```
PortalHandler:
$shared = new \stdClass();
$vars['_shared'] = $shared;
Entry Script:
$_shared->user = Auth::guard('user')->user();
↓ (object pass by reference — semua komponen guna object sama)
Layout:
{{ $_shared->user->name }}
```
### Kenapa Guna $_shared?
Entry script jalan dalam closure berasingan di PortalHandler. Variable PHP biasa (`$user`) mungkin tak sampai ke layout disebabkan cara Blade compile. `$_shared` adalah object — pass by reference — jadi apa-apa property yang set dalam entry script automatik nampak di layout.
### Peraturan
1. **Guna `@php ... @endphp`** untuk PHP code (atau `` jika prefer — kedua-dua berfungsi)
2. **Guna `$_shared->key = value`** untuk set data — bukan `$key = value`
3. **Guna `$_shared->key`** dalam Layout untuk access data
4. **Jangan guna variable biasa** — `$user` tak akan sampai ke layout
### Contoh Lengkap
**Entry Script:**
```blade
@php
use Illuminate\Support\Facades\Auth;
use Illuminate\Http\Exceptions\HttpResponseException;
if (!Auth::guard('user')->check()) {
throw new HttpResponseException(redirect()->to('/' . request()->segment(1) . '/login-web'));
}
$_shared->user = Auth::guard('user')->user();
$_shared->pageTitle = 'User Dashboard';
@endphp
```
**Layout:**
```blade
{{ $_shared->pageTitle }}
Welcome, {{ $_shared->user->name }}
```
---
## Email Notifications
### Password Reset Email
Di override dalam `FrontendUser@sendPasswordResetNotification` — generate URL ke CMS page menggunakan `SettingHelper::defaultSiteSlug()`:
```php
public function sendPasswordResetNotification($token)
{
$slug = SettingHelper::defaultSiteSlug();
ResetPassword::createUrlUsing(function ($notifiable, $token) use ($slug) {
return url('/' . $slug . '/reset-password-web?token='
. $token . '&email=' . urlencode($notifiable->email));
});
$this->notify(new ResetPassword($token));
}
```
### Email Verification
Di override dalam `FrontendUser@sendEmailVerificationNotification` — generate URL ke CMS page:
```php
public function sendEmailVerificationNotification()
{
$slug = SettingHelper::defaultSiteSlug();
VerifyEmail::createUrlUsing(function ($notifiable) use ($slug) {
return url('/' . $slug . '/email-verify-confirm?id='
. $notifiable->getKey() . '&hash='
. sha1($notifiable->getEmailForVerification()));
});
$this->notify(new VerifyEmail());
}
```
> **Nota:** Email notifications guna `defaultSiteSlug()` (bukan `authSiteSlug()`) kerana ia jalan dalam queue/notification context — tiada HTTP request untuk dapatkan site slug.
---
## Session Handling
### Guard Configuration (`config/auth.php`)
```php
'defaults' => [
'guard' => 'user',
'passwords' => 'user',
],
'guards' => [
'user' => ['driver' => 'session', 'provider' => 'frontend_users'],
'admin' => ['driver' => 'session', 'provider' => 'backend_users'],
],
'providers' => [
'frontend_users' => ['driver' => 'eloquent', 'model' => FrontendUser::class],
'backend_users' => ['driver' => 'eloquent', 'model' => BackendUser::class],
],
```
### Session Conflict Fix
Guna `session()->regenerateToken()` (bukan `session()->invalidate()`) untuk elakkan session ID berubah — supaya user guard dan admin guard boleh aktif serentak tanpa saling logout.
Dalam CMS page direct @php, guna manual login:
```php
$guard = Auth::guard('user');
session()->put($guard->getName(), $user->getAuthIdentifier());
$guard->setUser($user);
session()->regenerateToken();
```
---
## Password Reset Throttle
| Setting | Location | Default |
|---|---|---|
| Throttle duration | `config/auth.php:70` | 60 saat |
| Error message | `vendor/laravel/.../passwords.php` | "Please wait before retrying." |
---
## PortalHandler Additions
File: `app/Services/PortalHandler.php`
### `$_shared` Object
```php
$shared = new \stdClass();
$vars['_shared'] = $shared;
```
### `$errors` Variable
`ViewErrorBag` ditambah ke `$layoutVars` supaya `@error`, `$errors->any()`, `$errors->first()` boleh guna dalam mana-mana CMS page layout.
```php
$layoutVars = array_merge($vars, [
'__header__' => $header,
'__page__' => $pageHtml,
'__footer__' => $footer,
'errors' => session('errors') ?: new ViewErrorBag,
]);
```
### `HttpResponseException` Catch
Catch `HttpResponseException` sebelum `\Throwable` untuk allow redirect dari dalam CMS page layout.
```php
} catch (HttpResponseException $e) {
throw $e;
} catch (\Throwable $e) {
// show error
}
```
---
## Redirect Pattern
Untuk redirect selepas success dalam Web approach, guna `HttpResponseException` — bukannya `header()` + `exit`. Ini penting untuk pastikan session tersimpan dengan betul.
```php
throw new HttpResponseException(redirect()->to($redirect));
```
PortalHandler dah diubah suai untuk re-throw `HttpResponseException`.
> **Entry Script syntax:** Boleh guna sama ada `@php ... @endphp` (Blade) atau `` (PHP native) — kedua-dua berfungsi melalui `Blade::compileString()`. Pilih yang paling selesa dengan editor masing-masing.
---
## Ringkasan Fail
| Fail | Fungsi |
|---|---|
| `routes/web.php` | Route definitions + redirect closures (guna `SettingHelper::authSiteSlug()`) |
| `app/Models/Backend/FrontendUser.php` | Override email notifications (guna `SettingHelper::defaultSiteSlug()`) |
| `app/Http/Controllers/Frontend/Auth/LoginController.php` | POST login/logout/reset logic |
| `app/Http/Controllers/Frontend/Auth/RegisterController.php` | POST register logic (accept `site_slug`) |
| `app/Http/Controllers/Frontend/Auth/VerifyEmailController.php` | POST resend verification |
| `app/Services/PortalHandler.php` | CMS page renderer (`$_shared`, `$errors`, `HttpResponseException`) |
| `app/Http/Helpers/SettingHelper.php` | `authSiteSlug()` + `defaultSiteSlug()` helpers |
| `config/auth.php` | Guard, provider, password config |
| `resources/views/vendor/mail/html/header.blade.php` | Email template logo override |
---
## Cara Tambah Site Baru
1. Buat site baru kat Admin → CMS Builder → Sites
2. Create CMS pages yang diperlukan dalam site tu:
- Web approach: login-web, register-web, forgot-password-web, reset-password-web, email-verify, email-verify-confirm
- Controller approach: login, register (tambah hidden `site_slug` field)
3. Create user-dashboard page untuk post-login redirect
4. Route redirect automatik guna `SettingHelper::authSiteSlug()` — tak perlu setting apa-apa
5. Pastikan slug page layout guna `request()->segment(1)` untuk dynamic site links
6. Email notifications akan guna default site — set default site di Admin → CMS Builder → Sites