Extension talk:NewSignupPage


recruiting

how does someone go about recruit a new user .... i have enabled $wgRegisterTrack and $wgUserStatsPointValues['referral_complete'] but im not sure how someone would go about recruiting a friend Aditaa (talk) 21:06, 16 March 2012 (UTC)

Code can't be downloaded

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


All download links seems to be dead.
Can anyone please fix this? Stefahn (talk) 14:58, 9 August 2012 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

No message if user doesn't check the terms box

When I installed the extension this worked.
Now (MediaWiki 1.19.7) if the user does not check the terms checkbox, there is no message appearing.
(I have set up a message at Mediawiki:shoutwiki-must-accept-tos)

Does anyone have the same problem?
A fix would be great. Stefahn (talk) 00:10, 15 June 2013 (UTC)

4 years later there is still the same issue - running MediaWiki 1.27.4 currently. Stefahn (talk) 07:20, 19 November 2017 (UTC)

Can one alter the path of the terms of service and privacy policy to pages included on my own wiki as opposed to pages outside of my wiki? The question below about recruitment is still valid. How does the system know that someone has been recruited by another, especially if the confirm account extension is used? Thanks for your response in advance. Donkey Kong Genius (talk) 06:29, 3 October 2014 (UTC)

Hardcoded URLs are a bug, please report on bugzilla. Nemo 12:37, 3 October 2014 (UTC)
@Donkey Kong Genius: Yes, you can edit these by editing the appropriate system message(s). In your case, the message you'll want is MediaWiki:Shoutwiki-loginform-tos.
I have no idea how this extension interacts with the ConfirmAccount extension, as it's not a scenario I've ever tested but as always, patches are welcome!
As for the user recruitment part...that's tricky. Allow me to explain a bit of history and whatnot first (who knows, maybe someone will find this useful one day). On ArmchairGM, where the social tools originated, in addition to the extensions which we now collectively refer to as "SocialProfile", two other extensions played a major role in making the recruitment process work: InviteContacts and LoginReg.
NewSignupPage is LoginReg reborn; it implements the "backend" parts necessary (including, but most definitely not limited to, the new database table). InviteContacts was, as the name suggests, an extension which allowed you to send out invites to people in your email address book. I've been wanting to fix it since day one, but in the end, it turned out to be impossible. So, for years, there's been no "proper" way to recruit users (although with SocialProfile + NewSignupPage installed, it has always been possible if you know how).
Not that many months ago I decided to resurrect an older project of mine, codenamed MiniInvite this is essentially InviteContacts without the contact importing functionality. Once tested, finished and released, it allows (registered) users to send out invitation emails to people via a special page. The actual magic is done by two URL parameters, from and referral. If you visit a URL such as http://wiki.example.com/w/index.php?title=Special:UserLogin/signup&from=1&referral=TheDev and use this URL to sign up on the wiki, points are awarded to the wiki user TheDev for recruiting you (and an event, "TheDev recruited Foo", will show up on the activity feed, Special:UserActivity). This requires both NewSignupPage and SocialProfile, and $wgRegisterTrack has to be set to true in your wiki's LocalSettings.php for the recruitment process to work. I admit that I haven't exactly tested this, so do let me know how it works (or doesn't work) out for you.
@Nemo bis: Yes and no. Yes, it at least has its roots in a bug, but no, it's not a bug I "created" or can fix. The relevant root bug is bug #10317. Special:UserLogin, especially with the way how it currently (ab)uses QuickTemplate, is not very flexible or extendable. It was tough enough to have the special page changed so that links are parsed in the message (see also Special:Code/MediaWiki/45820 & gerrit:117806). I'm more than well aware of what we generally think of raw HTML messages, but at the time I wrote the patch in question, raw HTML was unfortunately the only solution that really "worked".
Should the URL(s) of the Terms of Use or Privacy Policy ever change, one would need to edit all i18n .json files, which definitely sucks, when you could just do some {{curly brace magic}} inside the message.
As always, patches are more than welcome, although I don't think you can get away without changing core. Do note that the content in includes/templates/ directory is rather scary, though. Jack Phoenix (Contact) 18:12, 3 October 2014 (UTC)
Very informative. I will investigate further in the future. For now I am trying to get the Confirm Account extension to work but for the life of me it is not going well. Donkey Kong Genius (talk) 22:18, 5 October 2014 (UTC)

New Bug? HTML/Wikitext treated as text

The Special:UserLogin/signup page is treating all the text in the MediaWiki:Shoutwiki-loginform-tos interface-page as simple text. IOW, no active links & therefore no tos document. I'm running MW 1.25.1

The Extension is no longer usable. WmBliss (talk) 22:42, 8 September 2015 (UTC)

Every N months/years someone changes the core MediaWiki file includes/templates/Usercreate.php intentionally so that it breaks NewSignupPage. See r45820 for the original change that I committed years ago which is needed for NewSignupPage to function correctly, and gerrit:187479 for the most recent reversion of my changeset. At this point I've given up on getting the core stuff fixed — it's (unfortunately) easier to reapply the one-line patch than to constantly argue about that and why it's needed. Jack Phoenix (Contact) 13:45, 22 November 2015 (UTC)

Adding checkbox for anonymous editors as well

New GDPR rules make this plug in very useful. However, it would be useful to also get opt in from anonymous users. I've created a branch to do it here. Are you interested in merging these changes or shall I fork the project?

I'm also thinking of adding new accounts to a group automatically within the extension. Also, having a special page to allow existing users to opt in/opt out of terms of service/privacy would be good. This is probably beyond the scope of this plugin? TimSC (talk) 20:38, 12 July 2018 (UTC)

the entire point is to require them to accept before creating their account, if they decline then they should not be allowed to register. 68.43.208.54 (talk) 02:39, 26 January 2019 (UTC)