Skip to content

Commit

Permalink
Updated config docs for anonymization of ips
Browse files Browse the repository at this point in the history
For #1090
  • Loading branch information
eSilverStrike committed Mar 14, 2022
1 parent 881ffa6 commit a0ce93d
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 3 deletions.
9 changes: 7 additions & 2 deletions public_html/docs/english/config.html
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,12 @@ <h3><a name="site_site">Site: Site</a></h3>
<tr>
<td valign="top"><a name="desc_ip_anonymization">ip_anonymization</a></td>
<td valign="top"><span class="tt">-1</span></td>
<td valign="top">IP anonymization policy. -1 if you don't want to anonymize IP addresses, 0 for instant anonymization. If you set X (an integer), IP anonymization will be performed after X seconds have passed.</td></tr>
<td valign="top">IP anonymization policy. -1 if you don't want to anonymize IP addresses, 0 for instant anonymization. If you set X (an integer), IP anonymization will be performed after X seconds have passed.<br><br>
<b>Please note</b> that the Geeklog Cron (<a href="#desc_cron_schedule_interval">cron_schedule_interval</a>) needs to be enabled to anonymize IPs.<br><br>
This only anonymizes IP addresses stored in the Geeklog database (that supports this feature). To remove all IP data, the Geeklog log files and web server log files should be deleted as well.<br><br>
Anonymization only happens after the cron job is triggered. This means there most likely will be a delay in anonymization until the cron job is run.<br><br>
Setting anonymization to instant (0) or a low value may interfere with plugins and/or the functionality of Geeklog. For example, in some cases IPs are used to determine if a visitor is behaving badly by submitted spam or content to often.
</td></tr>
</table>

<h3><a name="site_mail">Site: Mail</a></h3>
Expand Down Expand Up @@ -1786,7 +1791,7 @@ <h3><a name="misc_misc">Miscellaneous: Miscellaneous</a></h3>
interval in which the code should be executed (e.g. 86400 for daily
activation).<br />
Please note that to trigger this action, you will need to have someone
visit your site at around the specified time. On a site with few visitors,
visit your sites homepage (or front page) at around the specified time. On a site with few visitors,
the code may only be executed with considerable delay.<br />
Set to 0 to disable.</td></tr>
<tr>
Expand Down
7 changes: 6 additions & 1 deletion public_html/docs/japanese/config.html
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,12 @@ <h3><a name="site_site">サイト: サイト</a></h3>
<tr>
<td valign="top"><a name="desc_ip_anonymization">IP匿名化</a></td>
<td valign="top"><span class="tt">-1</span></td>
<td valign="top">IP匿名化の方針を指定します。-1を指定すると、匿名化を行わず、0を指定すると即座に匿名化を行います。整数Xを指定すると、X秒後に匿名化を行います。</td></tr>
<td valign="top">IP anonymization policy. -1 if you don't want to anonymize IP addresses, 0 for instant anonymization. If you set X (an integer), IP anonymization will be performed after X seconds have passed.<br><br>
<b>Please note</b> that the Geeklog Cron (<a href="#desc_cron_schedule_interval">cron_schedule_interval</a>) needs to be enabled to anonymize IPs.<br><br>
This only anonymizes IP addresses stored in the Geeklog database (that supports this feature). To remove all IP data, the Geeklog log files and web server log files should be deleted as well.<br><br>
Anonymization only happens after the cron job is triggered. This means there most likely will be a delay in anonymization until the cron job is run.<br><br>
Setting anonymization to instant (0) or a low value may interfere with plugins and/or the functionality of Geeklog. For example, in some cases IPs are used to determine if a visitor is behaving badly by submitted spam or content to often.
</td></tr>
</table>

<h3><a name="site_mail">サイト: メール</a></h3>
Expand Down

0 comments on commit a0ce93d

Please sign in to comment.