Fossil SCM
Improvements to the wording on the setup options related to self-registration.
Commit
6faaa91b3710bf91492a313c372636dbc5b2459f2222deca67846a1cfc13d03a
Parent
d048d86d0d76b91…
1 file changed
+14
-12
+14
-12
| --- src/setup.c | ||
| +++ src/setup.c | ||
| @@ -500,31 +500,33 @@ | ||
| 500 | 500 | @ (Property: "public-pages") |
| 501 | 501 | @ </p> |
| 502 | 502 | |
| 503 | 503 | @ <hr /> |
| 504 | 504 | onoff_attribute("Allow users to register themselves", |
| 505 | - "self-register", "selfregister", 0, 0); | |
| 506 | - @ <p>Allow users to register themselves through the HTTP UI. | |
| 507 | - @ The registration form always requires filling in a CAPTCHA | |
| 508 | - @ (<em>auto-captcha</em> setting is ignored). Keep in mind that anyone | |
| 509 | - @ can register under any user name. This option is useful for public projects | |
| 510 | - @ where you do not want everyone in any ticket discussion to be named | |
| 511 | - @ "Anonymous". (Property: "self-register")</p> | |
| 505 | + "self-register", "selfreg", 0, 0); | |
| 506 | + @ <p>Allow users to register themselves on the /register webpage. | |
| 507 | + @ A self-registration creates a new entry in the USER table and | |
| 508 | + @ perhaps also in the SUBSCRIBER table if email notification is | |
| 509 | + @ enabled. | |
| 510 | + @ (Property: "self-register")</p> | |
| 512 | 511 | |
| 513 | 512 | @ <hr /> |
| 514 | 513 | onoff_attribute("Email verification required for self-registration", |
| 515 | - "selfreg-verify", "selfregver", 0, 0); | |
| 514 | + "selfreg-verify", "sfverify", 0, 0); | |
| 516 | 515 | @ <p>If enabled, self-registration creates a new entry in the USER table |
| 517 | - @ but with provide any new capabilities until the email address provided | |
| 518 | - @ with registration has been verified. | |
| 516 | + @ with only capabilities "7". The default user capabilities are not | |
| 517 | + @ added until the email address associated with the self-registration | |
| 518 | + @ has been verified. This setting only makes sense if | |
| 519 | + @ email notifications are enabled. | |
| 519 | 520 | @ (Property: "selfreg-verify")</p> |
| 520 | 521 | |
| 521 | 522 | @ <hr /> |
| 522 | 523 | onoff_attribute("Allow anonymous subscriptions", |
| 523 | 524 | "anon-subscribe", "anonsub", 1, 0); |
| 524 | - @ <p>Are email notification subscriptions allowed for users Nobody and | |
| 525 | - @ Anonymous? | |
| 525 | + @ <p>If disabled, email notification subscriptions are only allowed | |
| 526 | + @ for users with a login. If Nobody or Anonymous visit the /subscribe | |
| 527 | + @ page, they are redirected to /register or /login. | |
| 526 | 528 | @ (Property: "anon-subscribe")</p> |
| 527 | 529 | |
| 528 | 530 | @ <hr /> |
| 529 | 531 | entry_attribute("Authorized subscription email addresses", 35, |
| 530 | 532 | "auth-sub-email", "asemail", "", 0); |
| 531 | 533 |
| --- src/setup.c | |
| +++ src/setup.c | |
| @@ -500,31 +500,33 @@ | |
| 500 | @ (Property: "public-pages") |
| 501 | @ </p> |
| 502 | |
| 503 | @ <hr /> |
| 504 | onoff_attribute("Allow users to register themselves", |
| 505 | "self-register", "selfregister", 0, 0); |
| 506 | @ <p>Allow users to register themselves through the HTTP UI. |
| 507 | @ The registration form always requires filling in a CAPTCHA |
| 508 | @ (<em>auto-captcha</em> setting is ignored). Keep in mind that anyone |
| 509 | @ can register under any user name. This option is useful for public projects |
| 510 | @ where you do not want everyone in any ticket discussion to be named |
| 511 | @ "Anonymous". (Property: "self-register")</p> |
| 512 | |
| 513 | @ <hr /> |
| 514 | onoff_attribute("Email verification required for self-registration", |
| 515 | "selfreg-verify", "selfregver", 0, 0); |
| 516 | @ <p>If enabled, self-registration creates a new entry in the USER table |
| 517 | @ but with provide any new capabilities until the email address provided |
| 518 | @ with registration has been verified. |
| 519 | @ (Property: "selfreg-verify")</p> |
| 520 | |
| 521 | @ <hr /> |
| 522 | onoff_attribute("Allow anonymous subscriptions", |
| 523 | "anon-subscribe", "anonsub", 1, 0); |
| 524 | @ <p>Are email notification subscriptions allowed for users Nobody and |
| 525 | @ Anonymous? |
| 526 | @ (Property: "anon-subscribe")</p> |
| 527 | |
| 528 | @ <hr /> |
| 529 | entry_attribute("Authorized subscription email addresses", 35, |
| 530 | "auth-sub-email", "asemail", "", 0); |
| 531 |
| --- src/setup.c | |
| +++ src/setup.c | |
| @@ -500,31 +500,33 @@ | |
| 500 | @ (Property: "public-pages") |
| 501 | @ </p> |
| 502 | |
| 503 | @ <hr /> |
| 504 | onoff_attribute("Allow users to register themselves", |
| 505 | "self-register", "selfreg", 0, 0); |
| 506 | @ <p>Allow users to register themselves on the /register webpage. |
| 507 | @ A self-registration creates a new entry in the USER table and |
| 508 | @ perhaps also in the SUBSCRIBER table if email notification is |
| 509 | @ enabled. |
| 510 | @ (Property: "self-register")</p> |
| 511 | |
| 512 | @ <hr /> |
| 513 | onoff_attribute("Email verification required for self-registration", |
| 514 | "selfreg-verify", "sfverify", 0, 0); |
| 515 | @ <p>If enabled, self-registration creates a new entry in the USER table |
| 516 | @ with only capabilities "7". The default user capabilities are not |
| 517 | @ added until the email address associated with the self-registration |
| 518 | @ has been verified. This setting only makes sense if |
| 519 | @ email notifications are enabled. |
| 520 | @ (Property: "selfreg-verify")</p> |
| 521 | |
| 522 | @ <hr /> |
| 523 | onoff_attribute("Allow anonymous subscriptions", |
| 524 | "anon-subscribe", "anonsub", 1, 0); |
| 525 | @ <p>If disabled, email notification subscriptions are only allowed |
| 526 | @ for users with a login. If Nobody or Anonymous visit the /subscribe |
| 527 | @ page, they are redirected to /register or /login. |
| 528 | @ (Property: "anon-subscribe")</p> |
| 529 | |
| 530 | @ <hr /> |
| 531 | entry_attribute("Authorized subscription email addresses", 35, |
| 532 | "auth-sub-email", "asemail", "", 0); |
| 533 |