Included a user referrer code to invite code, so when they sign up, it shows up who referred them.
Now users can delete their invites
Invitation Image Verification Added
The system can be turned on and off.
Usergroups Permissions Added; Allowed Usergroups to View and to Use This Hack
Invitation User Control Panel Link; Show Invitation Link in "User Control Panel" Left Menu
Invitation Automatic Link Creation; This will create a link on your forum navbar to the invitation page
Usergroups Permissions Added
fully phrased
added an admin option disable registration via normal methods
added an admin option which usergroups can to delete their invites
added an admin option enable disable invitation image verification
added an admin option Edit the Email Text Title
added an admin option Edit the Invite Description
added Invitation Sender Username to Email
integrated the totally vBulletin default Human Verification System into Invitation System
You decide it if you wich human verification system will be used in the invitation system go to Admincp > Human Verification Manager > and select one human verification if you want.
these are;
Image Verification
An image consisting of letters in varying fonts/shapes/sizes will be shown to the user. The appearance of this image is dicated by several options that you may control.
Question and Answer Verification
Questions provided by you that must be answered appropriately for verification.
reCAPTCHA Verification
An image containing two words will be shown to the user. This verification supports audio, allowing blind users to register.
Added Invitation User Options
a> Ability to limit number of invites by user. (user: Admin an have 10 invites, user: Testuser can have 20, etc, admin controlled)
b> Ability to reset invites to 0 on a per user basis (override), admin controlled
c> Ability to reset to max being unused, admin controlled
d> Abilitiy turn to on or off Invitation System per user basis, admin controlled
INSTRUCTIONS Install: ->Just Import product_invitation.xml via Product Manager
->Do template edits: In USERCP_SHELL Template Find this Code
For those complaning about this feature: If your server is properly set up (reverse DNS, proper SPF record), you'll find that using the webmaster email address is MUCH less likely to get the invitations flagged as spam, compared to using your users' email addresses.
Sorry, but I think that's rubbish - the user will be inviting a friend by entering an email address that they've probably already written to. How could their own email be marked as spam over one from an unknown, new source?...
Is it possible to ask the install to also offer the option in Automatic Link Creation in admincp, to include the option of the usercp link to be in the left usercp sidebar located under the Miscellaneous link group ?
Sorry, but I think that's rubbish - the user will be inviting a friend by entering an email address that they've probably already written to. How could their own email be marked as spam over one from an unknown, new source?...
Because most spam detectors these days look at e-mail message sources, which show originating IPs and machinenames; e-mail sent from the vBulletin system, whether from a user who knows another user's e-mail address, or from the system itself, will all contain the same originating trace markers.
If you know how to properly configure your server as fullfactor suggested (reverse DNS, SPF record modifications), you can avoid this problem.
Generally, there are two things you will want to do (broadly):
1. Use your own Domain Name Server and Configure It.
If you have a dedicated Domain Name Server (i.e., you're not using your host's DNS), you should be able to change Domain Name records for your domain (i.e., domain.com). Each DNS control suite is really different -- WHM, for example, has a dedicated automated system for parsing each entry that impacts the various exchanges of your domain. Learning the domain name system configuration syntax of your Domain Name Server is essential if you want to alter aliases or exchanges so that they maximize SEO and minimize Blacklisting. Check with your Registrar and your individual dedicated hosting company if you're not familiar with this process.
2. Configure your Sender Policy Framework.
Once you are able to alter records for your Domain Name Server, adopt one of the standards of compliance (such as OpenSPF or ReverseDNS) to properly identify your server's machine and prevent it from being blacklisted by major spam tools. You can Google these for some introductory documentation on setting up policies that direct robots and ensures it is properly being identified.