From d58a8478f659dfc6e1cc063acb9daf06e7ff914f Mon Sep 17 00:00:00 2001
From: Samuel Georges <sam@daftspunk.com>
Date: Sat, 27 Feb 2016 14:07:21 +1100
Subject: [PATCH] FTFY Refs #1796 The event should come after the logic as per
 the developer guidelines. If the event comes before the logic, it should be
 called beforeLogin. In this case, beforeLogin doesn't make sense, so just
 move the event after the parent::afterLogin call.

---
 modules/backend/models/User.php | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/modules/backend/models/User.php b/modules/backend/models/User.php
index 4644bdcea..def0a1b6f 100644
--- a/modules/backend/models/User.php
+++ b/modules/backend/models/User.php
@@ -1,9 +1,9 @@
 <?php namespace Backend\Models;
 
 use Mail;
+use Event;
 use Backend;
 use October\Rain\Auth\Models\User as UserBase;
-use Event;
 
 /**
  * Administrator user model
@@ -108,11 +108,11 @@ class User extends UserBase
             $this->sendInvitation();
         }
     }
-    
+
     public function afterLogin()
     {
-        Event::fire('backend.user.login', [$this]);
         parent::afterLogin();
+        Event::fire('backend.user.login', [$this]);
     }
 
     public function sendInvitation()