Tread wrote: ↑Mon Jan 30, 2023 8:33 pm
BF79 wrote: ↑Mon Jan 30, 2023 5:18 pm
this ext is for new register..doesnt allow new members register twice..
its not my idea of request.. my idea its just inform admin about double accout with same ip login
Then use the link i posted too it will inform you of a double account with info.
good ext bro but will work with phpbb 3.3 ?? as its old from 2015 ??
I translate it
“Detects and prevents cloning of accounts by the same forum members (multi-registrations / multi-registrations / duplicates / clones). Is my portmod for phpBB 3.0.x. For those who install for the first time: read the paragraph "Important notes about the detection of clones by Cookie" at the link of the mod.
Supported versions of phpBB : 3.1.x , 3.2.x , 3.3.x
phpbb3-ext-double-account-preventer-1.0.3.zip
(42.02 KB) Downloads: 1733
Installation and configuration:
Unzip and upload the contents of the archive to the ext folder in the root of the forum, then enable the extension in the "Personalization" tab in the administrator section and configure in the "Extension settings" by choosing the options you need. To clear the list of possible clones, the user must be given the global administrative right "Can clear the list of clones", which is located on the "Miscellaneous" tab. For phpBB version below 3.1.3 , this extension is not installed, because. only in this version the necessary functions for its operation appeared.
Opportunities and a brief job description:
Each user's browser (cookie) contains data about his account, under which he first registered or logged in. With each registration or entry to the forum, this data will be checked, and if they do not match the data under which the user registers again or logs in, the mod will conclude that this is a clone, which will notify you in all ways selected for this in the settings .
The same principle is used for the ban, which externally functions exactly the same as a normal ban. There is a separate page "Cookie ban" in the admin panel of the mod. The difference between a cookie ban and a regular ban is that it is not a nickname that is banned, but rather the user's browser. In other words, if the user does not delete cookies in his browser or uses another browser under which he has not previously received a ban, then he will not be able to enter the forum. Instead, it will be immediately thrown out - both at the first moment after the ban, and immediately after entering, showing the corresponding screen: "You are blocked on the forum, contact the administrator to find out the reason.." and the reason for the ban specified in the mod settings.
Keep in mind that the founder cannot be banned - just like in the case of a regular ban. The founder account can log into the forum even if he has a ban cookie in his browser.
There are several degrees of "ban" and the designation of each of them in a separate color. In the "Cookie ban" list, the usernames themselves are highlighted in color, and on other pages of the mod, in order not to conflict with the standard coloring of phpBB nicknames, a corresponding color inscription appears under the name. Users from the black list are marked in red: when entering under this name, a special ban cookie is set in the user's browser, and the browser becomes blocked on the forum until the user clears the cookie, deletes the ban cookie manually, or logs in under an account that is in the white list (green color). The cookie will be set again if he enters under a name from the black list. Users from the white list are highlighted in green: when you log in under this name, the cookie ban in the browser is removed.Please note that if a user has blocked the acceptance of cookies in his browser, enters through an anonymizer of a high degree of anonymity, or enters in some kind of "private browser mode" designed specifically to bypass bans on sites, then a cookie ban will not work for him. But under the name from the black list, he will not be able to enter anyway.
It is possible to prevent registration for users blocked by cookies by enabling the corresponding option in the configuration.
Autoban: when this option is enabled, if a user enters the forum with a ban cookie in the browser, and is not on the whitelist or in the exceptions from the ban check, then the mod is automatically blacklisted. Users who are on the black list cannot log in under their own name in any case, even if they do not have ban cookies in their browser (for example, if someone has cookies completely disabled).
Suspicious login log: when a user enters the forum, the user's ID is checked against the ID stored in the cookie. If they do not match, such an entry is logged and may indicate a clone or an illegal entry under someone else's nickname. In cases where you know for sure that some of the user pairs are not clones, you can add this pair to the exclusion list, after which their logins with each other's data will not be logged.
There are several ways to notify about detected clones: creating a topic on the forum, private messages and email, as well as entering information about suspicious registrations and logins in user notes that will be visible to moderators. When entering into notes, information about identical suspicious entries (committed at different times) will not be duplicated.
Recording of all actions to ban / unban users, incl. autobahn is logged in phpBB logs.”