mountaininteractive

I have only been using that one method and only checking for group changes. It appears to me that the user object is not being rehydrated with the most recent data after the DB transaction. It is always one step behind. Within the listener method, the $member object reflects the most recent object state - not the updated state. Once the request finishes, and you fetch a user (Member::loggedIn() or Member::load(...)) then the user reflects the most current state.

The red room? Jesus christ lord have mercy

Help me understand that. On line 543 of Member.php, the model is persisted to the DB. Not until line 562 is the event fired.

Correct, on V5.

> Thanks matt for pointing me here Here's the work i've done so far, let me know if I should do something differently or what yall think about it.

Hi there, I am running into an issue using the new Member listener. When updating a members groups, and using the onProfileUpdate callback, the member object does not reflect the latest changes and its always one iteration behind. The $changes array has the correct updates. Even when calling a load to attempt to get the latest DB results, it it still one iteration behind. The DB updates correctly, To reproduce: Update a members secondary groups Log the $changes array, $member->groups and MemberClass::load($member->member_id)->groups. The results in the $changes array will not be the same as $member->groups. It will be the results of your previous save.

I observed this too

I see, thank you.

Hi, Either API section fails or website fails to load, this occured after enabling friendly urls and then we setup the .htaccess Afterwards when I attempted to go to the API settings I was given the same "download ht access files"

Hi, Upon enabling google authenticator I am seeing that it does not work. A system error appears as the following Sorry, there is a problem Something went wrong. Please try again. Technical Details Error: Class "DASPRiD\Enum\AbstractEnum" not found (0) #0 /var/www/html/init.php(650): include_once() #1 /var/www/html/system/3rd_party/BaconQrCode/src/Writer.php(43): IPS\IPS::autoloader('BaconQrCode\\Com...') #2 /var/www/html/system/MFA/GoogleAuthenticator/Handler.php(145): BaconQrCode\Writer->writeString('otpauth://totp/...') #3 /var/www/html/applications/core/modules/front/system/settings.php(880): IPS\MFA\GoogleAuthenticator\Handler->configurationScreen(Object(IPS\Member), false, Object(IPS\Http\Url\Friendly)) #4 /var/www/html/applications/core/modules/front/system/settings.php(120): IPS\core\modules\front\system\settings->_mfa() #5 /var/www/html/system/Dispatcher/Controller.php(139): IPS\core\modules\front\system\settings->manage() #6 /var/www/html/applications/core/modules/front/system/settings.php(105): IPS\Dispatcher\Controller->execute() #7 /var/www/html/system/Dispatcher/Dispatcher.php(169): IPS\core\modules\front\system\settings->execute() #8 /var/www/html/index.php(16): IPS\Dispatcher->run() #9 {main} These details only show because you are logged in as an administrator. You can view them again later in the System Logs section of the AdminCP.