plugin:preregister
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
plugin:preregister [2017-11-22 18:39] – [PreRegister Plugin] 36.79.137.253 | plugin:preregister [2022-07-31 02:45] (current) – [PreRegister Plugin] 143.198.35.37 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== PreRegister Plugin ====== ---- plugin ---- description: | + | ====== PreRegister Plugin ====== |
- | ===== Installation ===== Install | + | |
+ | ---- plugin ---- | ||
+ | description: | ||
+ | author | ||
+ | email : turnermm02@shaw.ca | ||
+ | type | ||
+ | lastupdate : 2021-12-08 | ||
+ | compatible : Hrun, Ponder Stibbons, Binky, Weatherwax, Detritus, | ||
+ | | ||
+ | depends | ||
+ | conflicts | ||
+ | similar | ||
+ | tags | ||
+ | |||
+ | |||
+ | downloadurl: | ||
+ | bugtracker : https:// | ||
+ | sourcerepo : https:// | ||
+ | donationurl: | ||
+ | |||
+ | screenshot_img : | ||
+ | ---- | ||
+ | |||
+ | ===== Installation ===== | ||
+ | |||
+ | Search and install | ||
+ | |||
+ | ===== Examples/ | ||
+ | |||
+ | This plugin adds an extra layer of security to the registration process. It accepts registration data from a new user and sends the potential registrant an email with a link back to the wiki. When the link is processed, | ||
+ | |||
+ | It has its own CAPTCHA, which is based on a deck of playing cards, or it can use the [[plugin: | ||
+ | |||
+ | It is also possible to bypass the email stage and have the coded link printed to the screen and when the registrant clicks on that link, the registration will be processed and the user sent the password. This is also controlled from the Configuration Manager. | ||
+ | |||
+ | There is an administration panel which enables the administrator to prune back the data file where the temporary registration data is kept. Entries are deleted when the links are processed, but if a link is not used, the entry will remain in the data file until deleted using the admin panel. | ||
+ | |||
+ | ===== Configuration and Settings ===== | ||
+ | |||
+ | ^ Option ^ Choices ^ Default ^ | ||
+ | | captcha | builtin, captcha plugin, none|builtin| | ||
+ | |send_confirm | 1, 0 | 1| | ||
+ | |list_age| user set| 2*24*60*60 (i.e. 2 days)| | ||
+ | |||
+ | ==== captcha ==== | ||
+ | |||
+ | It is possible to use this plugin without a CAPTCHA by selecting '' | ||
+ | |||
+ | {{ http:// | ||
+ | |||
+ | If you have need for a CAPTCHA with more possiblities, | ||
+ | |||
+ | ==== send_confirm ==== | ||
+ | |||
+ | This option is either '' | ||
+ | |||
+ | ==== list_age ==== | ||
+ | |||
+ | This option is for use in the preregister admin panel. It determines how long to keep entries in the data file before they will be deleted. Entries are deleted when they have been processed using the return link, but this feature takes care of entries where the links are never returned to the wiki. | ||
+ | |||
+ | ===== FAQ ===== | ||
+ | |||
+ | The plugin checks to see whether a userid is already in use, so it will prevent a new registrant from submitting a userid that is already in use. However, it does not check to see whether or not a userid in its own data file is waiting to be processed. So, it is conceivable that two registrants could create the same userid, in which case the first one to process the return link would get the id and the other would get Dokuwiki' | ||
+ | |||
+ | ===== Recaptcha2 ===== | ||
+ | |||
+ | For users of [[: | ||
+ | | ||
+ | |||
+ | ===== Change Log ===== | ||
+ | |||
+ | {{rss> | ||
+ | |||
+ | ===== Discussion ===== | ||
+ | |||
+ | Use GitHub |
plugin/preregister.1511372350.txt.gz · Last modified: 2017-11-22 18:39 by 36.79.137.253