Add-On Releases - vBulletin Raffles

THIS ADD-ON IS NO LONGER AVAILABLE AND IS NOT SUPPORTED

NOTE: This add-on is designed for use with vBulletin 4.1.1 or higher. It may not work with earlier versions of vBulletin.

Raffles, giveaways, and contests, whatever you wish to call them, are a great way to increase traffic on any forum.

Features:

• Define a different prize image for each raffle.
• Set raffle rules on a per raffle basis.
• Set raffles to start in the future or on the day you create the raffle.
• Allow One or more entries per user.
• Allow multiple entries at one time if desired.
• Admin settable time delay between user entries.
• One or more prizes per raffle.
• One or more winners per raffle (multiple winners require multiple prizes).
• Allow members to win multiple times in one raffle if desired.
• Display winning 'ticket' numbers if desired.
• Selectable usergroups
• Post count limit if desired.
• Require Human Verification if desired.
• Will show in Community Menu if desired.
• Show active raffles in forum sidebar and/or in what's going on.
• Automatic raffle draw via vBulletin scheduled tasks.
• Manual raffle draw to override end date and/or scheduled draws.
• Turn raffles on or off via admincp. (Only raffle admins can view raffles when they are turned off)
• Support for just about any credit system such as vBCredits II, ICash, kBank and vbBux.
• Support for AW Coding's Credit Purchase System so member can purchase "raffle tickets".
• XHTML 1.0 Transitional validated (provided your current template passes the tests)

* DISCLAIMER *
----------------
Laws about how raffles should be handled vary from location to location. Be sure to check with local authorities and to comply with any laws that may apply to you. The author of this add-on can not be held responsible if the use of this add-on results in any violation of local laws.
By downloading this add-on, you agree to abide by local laws and to hold the author of this add-on harmless for any damages that may occurr from the use of this add-on.



* INSTALLATION *
-----------------------
1) Upload the contents of the 'upload' folder to your forum's root.
(If your forum's location is http://www.example.com/forums/, the root is /forums/)

2) Import the product XML file (product-raffles.xml) into the Product Manager in AdminCP.

3) If you want to view raffles on your site while the raffle system is turned off, go to AdminCP -> Usergroups -> Administrator Permissions select yourself and set "Can Admin Raffles" to 'Yes'.

4) Anyone you want to be able to administer raffles on your site must also have Administrator Permissions and have "Can Admin Raffles" set to 'Yes' or they will not be able to administer raffles.

5) Take some time to set the options in Raffle Settings.

6) Set up a raffle.

7) Make sure this add-on is marked as 'Installed' on vBulletin.org!
(If you want to get notices from me about updates for this add-on.)

* UPGRADE INSTRUCTIONS *
------------------------------------
1) Upload the contents of the 'upload' folder to your forum's root.
(If your forum's location is http://www.example.com/forums/, the root is /forums/)

2) Import the product XML file (product-raffles.xml) into the Product Manager in AdminCP and be sure 'Allow Overwrite' is set to 'Yes'.

3) If you are already using vBCredits you will need to go into Raffle Settings and set 'Use vBCredits' to 'Yes' and set 'vBCredits Currency' to the currency you are using. If you are using any other credit system, you will need to provide the information on what table, field and userid field are used by that credit system.

* USING RAFFLES *
------------------------
The whole system is pretty self explanatory, but there are a few things to keep in mind...

1) A default raffle image is supplied with the add-on. You must always supply an image for your raffles. You may change the default image if you like.

2) The entry period for raffles always end at 12:00am (midnight) on the day the raffle is to be drawn. (ie: Draw date is set 12/21/2011.. members can enter through 12/20/2011, the moment the date changes to 12/21/2011 no more entries are possible)

3) The scheduled task to draw the raffles is set to take place at 10:00am the day the raffle is to be drawn. You may change this by going to AdminCP->Scheduled Tasks->Scheduled Task Manager, find "Draw raffles", click on Edit and change the time of the draw to what you want it to be.

4) There are replacement variables used in several phrases. These are what the variables are:

raffle_agree: {1} = Forum name
raffle_eligible: {1} = Forum name {2} = Raffle name
raffle_message_body: {1} = Raffle name {2} = Draw date
raffle_message_close: {1} = Raffle admin name {2} = Phrase (raffle_admin_title)
raffle_message_salute: {1} = Winner name
raffle_recent: {1} = Time remaining before a user can enter again
raffle_winner_multi: {1} = Winner names for multiple raffle winners {2} = Raffle name
raffle_winner_one: {1} = Winner name for single raffle winner {2} = Raffle name

5) When adding a custom user profile field for this add-on, be sure to 'Private Field' is set to 'Yes' and 'Field Searchable on Member List' is set to 'No'.

6) If you don't want to have Raffles in the community menu, you can use a forum link to raffles.php.


* History (Changelog) *
-----------------------------
1.4.6 (November 18, 2015)
- Fix - Missing code for sidebar block

1.4.5 (August 6, 2015)
- Fix - Error entering raffles with entry limit.

1.4.4 (August 29, 2013)
- Fix - XHTML 1.0 transitional validation errors in raffle sidebar box.

1.4.3 (March 15, 2013) (Never released on vB.org)
- Change - Moved hard coded day, hour, minute, second words to vB phrases.

1.4.2 (September 1, 2012) (Released February 18, 2013 on vb.org)
(NO NEED TO UPDATE IF YOU DON'T USE THE COMMUNITY MENU FOR RAFFLES)
- Fix - Community menu navigation information missing from install xml.

1.4.1 (August 15, 2012) (NO NEED TO UPLOAD FILES IF YOU ARE RUNNING 1.4.0 JUST IMPORT XML FILE)
- Fix - Raffle sideblock missing from install file (overlooked in version 1.4.0).

1.4.0 (August 13, 2012)
- Fix - Some servers not providing proper responses with direct MySQL calls. (usually nginx)

1.3.9 (June 28, 2012)
- Fix - Wrong phrase used for file upload error.
No need to import XML file if you are running version 1.3.8. Just upload files to server.

1.3.8 (June 27, 2012)
- Add - Ability to upload prize image from ACP.
NOTE: Depending on your server configuration, you may need to make your images/raffles folder writeable (776 or 777)
- Add - Option to prevent additional usergroups from entering a raffle.

1.3.7 (May 21, 2012)
- Add - Option to show old raffles on a different page than currrent raffles.
- Change - Removed raffle_bits template.
- Change - Made compatible with vB 4.2.0.

1.3.6 (March 12, 2012)
- Fix - Active raffle sideblock will no longer show if there are no active raffles.

1.3.5 (February 25, 2012) (Never released on vB.org)
- Code enhancement for expansion.

1.3.4 (December 28, 2011)
- Add - Mass delete raffle entries (you must select a raffle in ACP->Raffles->Manage User Entries. The selection 'All Raffles' will not display a delete all option).

1.3.3 (October 5, 2011) (No need to install xml file if upgrading from 1.32 to 1.33. Just upload files to server)
- Fix raffle ticket purchase link for AWCoding Credit Purchase System Pro.

1.3.2A (September 29, 2011)
- Re-uploaded 1.3.2 with correct cpnav_raffles.xml file.

1.3.2 (September 29, 2011)
- Fix detection of AWCoding Credit Purchase System Lite (problem caused when fixing Pro detection).

1.3.1 (September 28, 2011)
- Improved user entry list in AdminCP.
- Fix detection of AWCoding Credit Purchase System Pro.

1.3.0 (August 29, 2011) (Uploaded a second time with proper sideblock code)
- Code enhancement for future expansion.
- Enabled CSRF protection.

1.2.9 (August 24, 2011) (never uploaded here)
- Code enhancement for future expansion.
- Unregistered users can now see raffles in WGO and forum sidebar if they are allowed.
- Fix members no longer able to view and enter raffles scheduled in the future.

1.2.8 (August 1, 2011) (never uploaded here)
- Code enhancement for future expansion.

1.2.7 (August 1, 2011)
- Restored AWCPS patch to install script.
- Restored forum sidebar block to install script.
- Restored missing option to show image in sidebar block.

1.2.6 (July 20, 2011)
- Moved 'Allow Multiple Wins' from main settings to individual raffle settings. (user requested)

1.2.5 (July 16, 2011)
- Added Debug Logging option to raffle system. (v1.2.4 was never uploaded)

1.2.3 (July 15, 2011)
- MAJOR FIX - Fix raffle draw so no duplicates happen when allow multiple wins is set to no (finally found bug in 3.8.x version).

1.2.2 (July 11, 2011)
- Fix members can no longer enter multiple times by using the back button on their browser. (reported in vB 3.8.7 version)

1.2.1 (July 6, 2011)
- Fix Allow multiple wins to one member now works.
- Fix database error when no members enter raffle.
- Removed un-needed left joins in some DB queries that were needed in original release.

1.2.0 (July 4, 2011)
- Fix raffle draw time now displays in members's usercp chosen time zone format.

1.1.9 (July 3, 2011)
- Fix error in scheduled task when multiple prizes are awarded.
- Changed copyright so it only displays on raffle pages.

1.1.8 (June 17, 2011)
- Fix SQL error when 'Show Raffles Already Drawn' is set to 'No'.

1.1.7 (June 8, 2011)
- Added maximum picture width option for raffle detail page.

1.1.6 (June 6, 2011)
- Fix PMs not being sent with automated draw.
(NO NEED TO IMPORT XML IF YOU ARE ALREADY RUNNING VERSION 1.1.5 - JUST UPLOAD FILES)

1.1.5 (June 2, 2011)
- Fix vBCredits error created in version 1.1.1.
- Minor code change to make system compatible with PHP 5.3.x

1.1.4 (June 1, 2011)
- Database table creation change to make it compatible with MySQL 5.5.8
(NO NEED TO UPDATE IF YOU ARE ALREADY RUNNING VERSION 1.1.3)

1.1.3 (May 30, 2011)
- Added option to show raffle image in forum sidebar block.
- Added sidebar block image width setting.
- Added vBulletin minimum version 4.0.4 check.
- Changed database creation method.

1.1.2 (May 26, 2011)
- Fix system checking for credits when it shouldn't.

1.1.1 (May 26, 2011)
- Fix 'Other Credit System' saying not enough credits when member has enough.

1.1.0 (May 24, 2011)
- Added option to show the scheduled draw time on raffle pages.(user requested)

1.0.9 (May 21, 2011)
- Fix unregistered members unable to see raffles when they are allowed.

1.0.8 (May 16, 2011)
- Fix blank screen after entry.
- Fix redirect error.
- Fix default maximum entries.

1.0.7 (May 12, 2011)
- Added option to show who has entered raffles.(user requested)
- Reduced database queries by 1.
- Moved vBCredits log phrase to vBulletin phrases.
- Fixed bug where raffle sidebar was being displayed when raffles were turned off.

1.0.6 (May 10, 2011)
- Added the ability to allow multiple entries to be submitted at one time.(user requested)
- Added display of the number of entries a member has submitted to raffle detail page.(user requested)
- Added support for AW Coding's Credit Purchase System. (allows use of different payment systems to purchase 'tickets')
- Added transaction logging for vBCredits (thanks to Darkwaltz4 for info)
- Added minimum/maximum value checks.
- Added option to display winning "ticket" number(s) with winner name(s).(user requested)
- Added option to allow members to only win once per raffle.(user requested)
- Added PM to raffle admin if raffle couldn't be drawn when scheduled.
- Added ability to set a start date other than the day raffle was created.(user requested)
- Stray hardcoded phrase moved to vB phrases.
- Fixed bug where sent PMs were being saved in admin sent box when raffle was drawn manually even if option is set to no in settings.
- Fixed bug where only one winner was being displayed in admin area for a multi-prize raffle when raffle was drawn manually.

1.0.5 (May 4, 2011)
- Sidebar and Current Raffle templates now cached
- Fixed bug where entry limits over 999 only allowed 1 entry.
- Fixed missing phrases on new installs.
- Added support for vBCredits, ICash, kBank and vbBux. (user requested)

1.0.4 (May 3, 2011)
- Sidebar block now installs automatically when the add-on is installed.

1.0.3 (May 3, 2011)
- Added option to display current raffles in What's Going On (Displays what raffles are available for the member's usergroup). (user requested)
- Added Sidebar Block template and instructions in ReadMe on how to add a Current Raffle Block. (user requested)
- Added Banned Usergroup setting for usergroups forbidden to use or see the raffle system. (user requested via PM)
- Modified Raffle Admin so banned usergroups do not show up when creating or editing a raffle.

1.0.2 (May 2, 2011)
- Fixed "Enter Through" date display. (was not following vBulletin date display settings)
- Slight change to database routines so they all go directly through vBulletin.

1.0.1 (April 30, 2011)
- Added check to be sure files are uploaded to server (NO NEED TO DOWNLOAD IF YOU ALREADY HAVE 1.0.0 INSTALLED)

1.0.0 (April 30, 2011)
- Initial Release

* Known Working on vB Versions *
-------------------------------------------
4.0.4
4.0.6
4.0.7
4.0.8
4.1.1 through 4.2.1

[nhawk]

Originally Posted by inphoenix

Is there a way that no PMs are sent out to winners? I would like to announce on forum when it has been drawn.

While PMs will still be sent, there is an add-on on my site that announces winners in a thread.

[duketxboy]

is great bends over backwards to help somebody in need.........

[OverhaulNetwork]

Here is another suggestion I would like to see implemented. When I enable Show Raffles Already Drawn raffles seem to show in order of when they were started. I think it would make more sense to have them sorted by when the draw date is. I am forced to disable this feature because I don't want active raffles to be buried by raffles that have already been drawn.

Also have you given more thought to changing the cutoff time to buy tickets from 12:00AM? Maybe an option per raffle in minutes to choose cutoff times? Right now I am forced to set my raffles to end on the day following that actual day I draw as I have many members get tickets right up until I manually draw the raffle. This causes some confusion as the draw date shows as the following day. I am also forced to change the date back to the actual draw date right before drawing otherwise the raffle will remain showing current on the raffle page and side block even though it has been drawn.

[nhawk]

Originally Posted by OverhaulNetwork

Here is another suggestion I would like to see implemented. When I enable Show Raffles Already Drawn raffles seem to show in order of when they were started. I think it would make more sense to have them sorted by when the draw date is. I am forced to disable this feature because I don't want active raffles to be buried by raffles that have already been drawn.

Also have you given more thought to changing the cutoff time to buy tickets from 12:00AM? Maybe an option per raffle in minutes to choose cutoff times? Right now I am forced to set my raffles to end on the day following that actual day I draw as I have many members get tickets right up until I manually draw the raffle. This causes some confusion as the draw date shows as the following day. I am also forced to change the date back to the actual draw date right before drawing otherwise the raffle will remain showing current on the raffle page and side block even though it has been drawn.

I won't make the change on the general released version, but I will tell you what needs to be changed. Just be aware that the raffle system has run on the site it was developed for, for nearly 4 years. The midnight entry deadline was created because of problems with people entering at the very last moment and the result becoming skewed because of that.

For your listing of raffles, edit raffles.php. Locate the FIRST instance of this code...

	$getraffle = $vbulletin->db->query_read("SELECT * FROM " . TABLE_PREFIX . "raffle
		WHERE startdate <= $timenow
		$oldentryopt
		ORDER BY id DESC
	");

And change it to this code..

	$getraffle = $vbulletin->db->query_read("SELECT * FROM " . TABLE_PREFIX . "raffle
		WHERE startdate <= $timenow
		$oldentryopt
		ORDER BY enddate DESC
	");

That will sort the raffles by end date in decending order.

Now, the entry deadline...

Locate ALL instances of this code..

$oneless = $raffle['enddate']-86400;

And change it to..

$oneless = $raffle['enddate'];

Locate this code..

if($check_raffle_date <= $current_date && $raffle['winner'] == "")
{
	$raffle['status'] = "<font color='". $vbulletin->options['raffle_wait_color'] . "'><b>" . $vbphrase['raffle_waiting'] . "</b></font>";
}elseif($raffle['winner'] != ""){
	$raffle['status'] = "<font color='". $vbulletin->options['raffle_drawn_color'] . "'><b>" . $vbphrase['raffle_drawn'] . "</b></font>";
}
else
{
	$raffle['status'] = "<font color='". $vbulletin->options['raffle_active_color'] . "'><b>" . $vbphrase['raffle_active'] . "</b></font>";
}

And change to..

if($raffle['winner'] != "")
{
	$raffle['status'] = "<font color='". $vbulletin->options['raffle_drawn_color'] . "'><b>" . $vbphrase['raffle_drawn'] . "</b></font>";
}
else
{
	$raffle['status'] = "<font color='". $vbulletin->options['raffle_active_color'] . "'><b>" . $vbphrase['raffle_active'] . "</b></font>";
}

Locate this code..

if(($check_raffle_date <= $current_date) && $detail['winner'] == "")
{
	$detail['status'] = "<font color='". $vbulletin->options['raffle_wait_color'] . "'><b>" . $vbphrase['raffle_waiting'] . "</b></font>";
}elseif($detail['winner'] != "")
{
	$detail['status'] = "<font color='". $vbulletin->options['raffle_drawn_color'] . "'><b>" . $vbphrase['raffle_drawn'] . "</b></font>";
}
else
{
	$detail['status'] = "<font color='". $vbulletin->options['raffle_active_color'] . "'><b>" . $vbphrase['raffle_active'] . "</b></font>";
	$detail['active'] = $vbphrase['raffle_active'];
}

And change to this...

if($detail['winner'] != "")
{
	$detail['status'] = "<font color='". $vbulletin->options['raffle_drawn_color'] . "'><b>" . $vbphrase['raffle_drawn'] . "</b></font>";
}
else
{
	$detail['status'] = "<font color='". $vbulletin->options['raffle_active_color'] . "'><b>" . $vbphrase['raffle_active'] . "</b></font>";
	$detail['active'] = $vbphrase['raffle_active'];
}

Locate this code..

if($check_raffle_date == $current_date && $detail['winner'] == "")
{
	$show['msg'] = TRUE;
	$msg = "<font color='". $vbulletin->options['raffle_drawn_color'] . "'>" . $vbphrase['raffle_closed'] . "</font>";
}

And delete it.

Near the end of raffles.php locate this code...

if($current_date >= $oneless) eval(standard_error(fetch_error('raffle_entry_ended')));

And delete it.

That should allow entries right up until you actually draw the raffle. I strongly recommend against this. And I also recommend you disable the scheduled draw task if you do this.

If you make these changes, I can't support any problems that may happen. I hope you understand.

[OverhaulNetwork]

Originally Posted by nhawk

The midnight entry deadline was created because of problems with people entering at the very last moment and the result becoming skewed because of that.

Can you please explain a bit more how this causes an issue.

Currently I run raffles that allow people to get a max of 5 tickets (1 per day) and the raffle consists of 1 prize. I am confused as to how the time tickets are bought will change the outcome, maybe you could explain the winner algorithm.

[nhawk]

Originally Posted by OverhaulNetwork

Can you please explain a bit more how this causes an issue.

Currently I run raffles that allow people to get a max of 5 tickets (1 per day) and the raffle consists of 1 prize. I am confused as to how the time tickets are bought will change the outcome, maybe you could explain the winner algorithm.

I won't go into detail, but it has to do with the timing of the last entry into the raffle and the random function of mysql.

The midnight cutoff was to insure that everyone knew exactly when the entry deadline was (no excuses when it's plastered on every page) and it's a HUGE buffer to prevent the timing problem.

The part "I" don't understand is why the midnight cutoff is an issue for you. If the proper date for the last day entries are accepted is displayed, your members shouldn't have an issue with that and just wait for the next raffle to start.

[OverhaulNetwork]

Originally Posted by nhawk

I won't go into detail, but it has to do with the timing of the last entry into the raffle and the random function of mysql.

The midnight cutoff was to insure that everyone knew exactly when the entry deadline was (no excuses when it's plastered on every page) and it's a HUGE buffer to prevent the timing problem.

The part "I" don't understand is why the midnight cutoff is an issue for you. If the proper date for the last day entries are accepted is displayed, your members shouldn't have an issue with that and just wait for the next raffle to start.

Is there a way I could make it closer to the drawing time without causing an issue?

Like 5 minutes or some magic number that would work?

[OverhaulNetwork]

To go into a bit more detail why midnight becomes an issue is because we draw the raffles on a live video stream. So we have allot of people watching to find out who wins as well as people who are just finding out about the raffles (the purpose of the raffles is to draw new members to our site) so if we are broadcasting for 4 hours we encourage everyone to register tot he site and get a ticket as we will be drawing a winner in X amount of minutes.

It would suck to have to say, "You missed out on this weeks raffle, you can register and wait another week." people want things now now now. Forcing them to wait a week can possibly cause them to skip registering.

I have just been setting the raffle to end the following day then manually drawing it to get around this. But then it shows as drawing on the following day it is actually being drawn confusing members.

[nhawk]

Originally Posted by OverhaulNetwork

Is there a way I could make it closer to the drawing time without causing an issue?

Like 5 minutes or some magic number that would work?

It could be done but as the end date is stored now there is no time option. It just stores the date with all zeros for time. And the checks just check the date, not the time.

IE: If today is less than the end date accept entries. If today is greater than or equal to the end date don't accept entries.

There would be some coding and changes needed for it to accept and check for an end time.

[nhawk]

Originally Posted by OverhaulNetwork

To go into a bit more detail why midnight becomes an issue is because we draw the raffles on a live video stream. So we have allot of people watching to find out who wins as well as people who are just finding out about the raffles (the purpose of the raffles is to draw new members to our site) so if we are broadcasting for 4 hours we encourage everyone to register tot he site and get a ticket as we will be drawing a winner in X amount of minutes.

It would suck to have to say, "You missed out on this weeks raffle, you can register and wait another week." people want things now now now. Forcing them to wait a week can possibly cause them to skip registering.

I have just been setting the raffle to end the following day then manually drawing it to get around this. But then it shows as drawing on the following day it is actually being drawn confusing members.

LOL, please don't take this the wrong way.. but you have got to be the only person on the planet doing a live video feed of a raffle draw.

The original reason for the manual draw was to end a raffle early if it was so popular that a second identical raffle could be run. And then it was used sparingly with notice to the site's members (some 50,000+ when the raffle system first started with them) in a post. It was never intended to be used the way you're using it.

In any case, that's irrelevant because that's how you're using it.

Normally I wouldn't budge from my stance on this. But I will look closely at adding an end time option with a minimum spread between the draw and the end of the entry period. There are no promises as to when it will be done as this means reversing many changes over the time the system has been in existence. Once it's done I may even require you to run it for a period of time before I release it to everyone.