It's true for me. Of course i am not 100% sure i had it set like others in the thread. All i know is it kept reporting the same nickname against the same nickname: like:
Joe is an alter ego of Joe.
Alter Ego Detector 1.7.8
- Thread starter Liam W
- Start date
Joe is an alter ego of Joe.
zastavra
Active member
Liam, will you check this please?
Code:
#0 /var/www/vhosts/domain.com/publicsite/library/XenForo/Model/User.php(2156): XenForo_Application::handlePhpError(8, 'Undefined index...', '/var/www/vhosts...', 2156, Array)
#1 /var/www/vhosts/domain.com/publicsite/library/XenForo/Model/Conversation.php(1203): XenForo_Model_User->canBypassUserPrivacy(NULL, Array)
#2 /var/www/vhosts/domain.com/publicsite/library/XenForo/DataWriter/ConversationMaster.php(152): XenForo_Model_Conversation->canStartConversationWithUser(Array, NULL, Array)
#3 /var/www/vhosts/domain.com/publicsite/library/LiamW/AlterEgoDetector/Extend/ControllerPublic/Login.php(154): XenForo_DataWriter_ConversationMaster->addRecipientUserNames(Array)
#4 /var/www/vhosts/domain.com/publicsite/library/LiamW/AlterEgoDetector/Extend/ControllerPublic/Login.php(66): LiamW_AlterEgoDetector_Extend_ControllerPublic_Login->_alterEgoDetected(18506, 18506)
#5 /var/www/vhosts/domain.com/publicsite/library/XenForo/FrontController.php(347): LiamW_AlterEgoDetector_Extend_ControllerPublic_Login->actionLogin()
#6 /var/www/vhosts/domain.com/publicsite/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#7 /var/www/vhosts/domain.com/publicsite/index.php(13): XenForo_FrontController->run()
#8 {main}
kontrabass
Well-known member
After updating, the user links in the post messages are incorrect. The userlinks in the posts are linked to
Code:
http://{userlink2}So {userlink2} and {userlink1} aren't getting parsed or whatever you call it
New Joe
Well-known member
New Joe
Well-known member
No idea about that, why would it show up on your add on though?
New Joe
Well-known member
So with this add on disabled when creating a new account the error doesn't happen as per my post above
But once enabled and I create a new account then the error as per my post above happens.
But no idea why...
JamesBrown
Well-known member
Anyone else experiencing this issue?
Southfork1
Active member
Thank you for doing this.
edit... Sorry I didn't read through the others posts before hand. I see the following suggestion is not new.
Suggestion... Change the subject line...
Before: {username} is an alter ego!
After: AE: {username1}, {username2}
Tried changing it but the subject doesn't recognize username1 / username2 values, only username.
edit... Sorry I didn't read through the others posts before hand. I see the following suggestion is not new.
Suggestion... Change the subject line...
Before: {username} is an alter ego!
After: AE: {username1}, {username2}
Tried changing it but the subject doesn't recognize username1 / username2 values, only username.
Last edited:
Southfork1
Active member
Mine is. With that....
Suggestion: If the cookie registers more than two ID's on the computer, posts them all on the AE report. Not separate posts for A-B, A-C, etc.. but A, B, C, D, E, F all included. It takes care of the next step which is associating a group, or group of puppet accounts.
Scenario one most are familiar with, which is the troll who has multiple puppet accounts. The second scenario, for me, is a shop (store) spamming or attacking. While this AE add-on focuses on puppet accounts, group association can be equally as useful especially when dealing with flareups. I've seen as many as 7 puppet accounts, and over 10 active ID's playing angles during an attack from a shops computer.
Last edited:
CTXMedia
Well-known member
That would be handy info to see in the report - a reason why the accounts were flagged as possible alter-egos!
I'm not sure how I missed that, thanks!
