Alter Ego Detector

Alter Ego Detector 1.7.8

No permission to download
Hi Chimpie, I've taken over development & support for this addon.

Please make sure your account/user group has the "View Alert Ego Report" usergroup permission.

Right... my question is, where is the report? Is this referring to the Reports in the upper left corner or an actual report in ACP?
 
Right... my question is, where is the report? Is this referring to the Reports in the upper left corner or an actual report in ACP?
The Report Centre accessible from the front-end. Assuming you haven't redirected it to post as a thread.
 
The Thread Titel looks like this.

{username} ist ein Alter Ego!

and the links into the thread and also in the reports are like this

Es sieht so aus, als wäre Karl Auer25 ein Alter Ego von Karl Auer...

Where are the links for the first name is http://{userlink2}/ and for the second this http://{userlink1}/

Using your latest release and Xenforo 1.4.5
 
@teletubbi do you have the report center redirected to a forum? Or is this just the thread output option of this addon? (Both can result in threads being created)
 
Only the title of the report is the same as in the thread. {username}
Into the report the names are correct and the links are working.
 
Only the title of the report is the same as in the thread. {username}
Into the report the names are correct and the links are working.
Can you check the contents of the phrases: aed_thread_subject and aed_thread_message ?

The correct english contents are:

aed_thread_message:
Code:
It looks like [url="{userLink2}"]{username2}[/url] is an alter ego of [url="{userLink1}"]{username1}[/url]...

aed_thread_subject:
Code:
[{username1} & {username2} are alter egos!

aed_thread_subject_count:
Code:
{username} has {count} alter egos!

Changing from userlink2 -> userLink2 and userlink2 -> userLink2 in your versions should work.
 
After updating, the user links in the post messages are incorrect. The userlinks in the posts are linked to

Code:
http://{userlink2}
etc

So {userlink2} and {userlink1} aren't getting parsed or whatever you call it ;)
The correct variable names should be: {userLink2} and {userLink1}. The phrases aed_thread_message & aed_thread_subject likely need updating.
 
Will this work and do you recommend it?
upload_2015-3-30_15-39-39.webp

And should I enable "check IP" and how many minutes are recommended?
upload_2015-3-30_15-40-25.webp
 
Will this work and do you recommend it?
View attachment 102629
{userid} needs to be an actual member number. Either as a custom created user, or your default admin user.

And should I enable "check IP" and how many minutes are recommended?
View attachment 102630
The IP Check should have a default of ~15 minutes. In the future I may restrict it down to 5 minutes or even off.

I'ld recommend disabling the IP check, as it isn't terribly useful these days.
 
  • Like
Reactions: sbj
Works great, but is there a way to exclude specific users from this? I have a few Husband / Wives that use my sites, and I get a ton of reports from these users.

I would like to enter their user id number to ignore them. (and no I don't want to move them to a different / new usergroup. :))
 
I would like to enter their user id number to ignore them. (and no I don't want to move them to a different / new usergroup. :))

You'll need to create a new usergroup that is able to bypass the alter ego detector; put any pairs or groups into this additional group and the reports will stop.

It's the only way to do it. (y)
 
Works great, but is there a way to exclude specific users from this? I have a few Husband / Wives that use my sites, and I get a ton of reports from these users.

I would like to enter their user id number to ignore them. (and no I don't want to move them to a different / new usergroup. :))
If you are using the report option; just resolve the report and ensure the reports are not bumped when in the resolved state (but it can be handy to bump them in the rejected state).

IMO, This is better than completely disabling the alter-ego detector for that set of users.

It's the only way to do it. (y)
You can just setup the reports stuff so it reports once, then resolve it as a known pair.
 
You can just setup the reports stuff so it reports once, then resolve it as a known pair.

Ah, yes, sorry Xon - I'm using v1.4.1 - I notice that there has since been an update to allow you to only report once. (y)
 
  • Like
Reactions: Xon
Back
Top Bottom