Browse Source

Workaround for verification and authentication conflict

master
Immanuel Onyeka 3 years ago
parent
commit
fbeb62710e
2 changed files with 9 additions and 2 deletions
  1. +2
    -2
      resources/views/home.blade.php
  2. +7
    -0
      routes/web.php

+ 2
- 2
resources/views/home.blade.php View File

@@ -157,7 +157,7 @@
<h2>Benefits of Buying Views</h2>
<div>
<p>We know that getting people to see your content can be an uphill
battle. Reaching just 10,1000 organic views can be tough because social networks give
battle. Reaching just 10,000 organic views can be tough because social networks give
the lion's share of exposure to the personalities who already have the biggest
following. The more views and impressions a post has, the more people are
willing to watch it, that's why consistent and high engagement is
@@ -193,7 +193,7 @@

<div class="collapsible"><button>Is buying views illegal?</button>
<div class="content"><p>
No, and there is no good reason why it should be.
No, and there is no good reason it should be.
</p></div></div>

<div class="collapsible"><button>How can I pay?</button>


+ 7
- 0
routes/web.php View File

@@ -44,6 +44,13 @@ Route::get('/verify-email', function() {
})->middleware('auth')->name('verification.notice');

Route::get('/verify/{id}/{hash}', function (EmailVerificationRequest $request) {
$user = User::find($id);

if ($user->email_verified_at) {
abort(404);
}

Auth::login($user);
$request->fulfill();
return redirect('/panel');
})->middleware(['signed'])->name('verification.verify');


Loading…
Cancel
Save