|
9.
|
|
|
IP address bans restrict access to the website on a low level. Be careful to [url="know an IP address"]{1}[/url] before you ban it to avoid inadvertently banning a shared computer/Internet-gateway. Please also be advised that [abbr="Internet Service Provider"]ISP[/abbr]-assigned addresses are often not fixed: a computer's IP address might vary substantially from one day to the next.\n\nAddresses may contain ‘wildcards’ (asterisks) between dotted segments to symbolise that any number in that segment will match.\n\nIt is usual to have an asterisk as the final (fourth) part, as a user's IP address is very likely to change in that final component and at the same time it is very unlikely that wildcarding that last portion would result in any unintended bans. This said, extreme care is advised using wildcards at other points.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]IP_BANNING_WILDCARDS
|
|
13.
|
|
|
Submitter banned
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SUBMITTER_BANNED
|
|
16.
|
|
|
Submitter unbanned
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]SUBMITTER_UNBANNED
|
|
26.
|
|
|
A ban on <tt>{1}</tt> could not be added, as the IP address is not valid (must contain 4 numeric/wildcarded sections, with dots in-between each).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]IP_ADDRESS_NOT_VALID
|
|
28.
|
|
|
Related screens
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]RELATED_SCREENS
|
|
29.
|
|
|
The following additional members were also found to have used this IP address: {1}. It may be the address of a shared computer, or gateway, or it may be that the member's are one-and-the-same -- further investigation of the member's history may reveal a clearer picture and help you decide what to do (e.g. warnings, member-merging).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MEMBERS_ALSO_ON_IP
|
|
30.
|
|
|
This screen to find information relating to a website user. It's purpose is as a hub for information, and does not provide any information that is not also available elsewhere in the software. The primary screen for managing a joined member is the member's profile screen.\n\nThe software has tried to pull together as much as it can, by trying to match against the triad of [b]IP address[/b], [b]member ID[/b], and [b]username[/b]/[b]author[/b]. Links are provided that correspond to each of these, each link providing a different perspective on what is likely a single user.\n\nIf you would like to ban the member, it is advised that this be done through their member profile. If you would like to provide a more low-level ban against IP address, note down their IP address groups and then proceed to the [url="IP ban"]{1}[/url] screen. Before proceeding though, it is advisable to carefully research the usages of each IP address set by performing additional IP-based lookups (following the IP addresses as linked will lead you to the appropriate screens).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_ACTIONLOG_BAN_HELP
|
|
32.
|
|
|
IP address bans
|
Context: |
|
[strings]MODULE_TRANS_NAME_admin_ipban
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]MODULE_TRANS_NAME_admin_ipban
|
|
34.
|
|
|
{1} ({2} logged actions)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ACTIONLOG_USERCOUNT
|
|
35.
|
|
|
{1} ({2} logged action)
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ACTIONLOG_USERCOUNT_UNI
|