Event attendance

Request by: DaveLogic

With this hack when you create an event you can give the users an option to "register" to the event. Then you can view which people have registered to that event.

This could be used so you create an event and then other people notify that they will be attending to the event. You can then keep track of all the people that would be attending each event.

Info for hackers:
You may modify, improve, upgrade, redistribute this hack, include it
in another hack or yours or translate it provided you do it free of
charge and you distribute it in www.vbulletin.org at least, there is no
need to pm me asking for permission
Some portions of the code are (c) Jelsoft Enterprises Ltd.

[SamirDarji]

That's the hard part--the pseudocode. It's the logic behind the code. That's where ideas on how to do something get tested, shot down, optimized and the like. The coding is the easy part once you have the logic. Then it's just a matter of making the chosen language do what the pseudocode dictates.

[Benj]

dont have a clue how to do pseudocode sorry

[Benj]

so................................

[buro9]

Originally Posted by SamirDarji

If someone writes out the pseudocode, I'd be willing to hack at it in my spare time.

Here's the psuedo SQL:

PHP Code:

$query = "SELECT `eventid` , `userid` , `event` , `title` , `allowsmilies` , `recurring` , `recuroption` , `calendarid` , `customfields` , `visible` , `dateline` , `utc` , `dateline_from` , `dateline_to` , `useroll` , `roll`
FROM `" . TABLE_PREFIX . "event`
WHERE `roll` LIKE '%i:" . $bbuserinfo['userid'] . ";s:" . strlen($bbuserinfo['userid']) . ":\"" . $bbuserinfo['username'] . "\"%' LIMIT 0, 30"; 


That would return all events that a user was attending.

Note that the SQL matches the entire user information, as performing wildcard LIKE's are never good because if we just did the userid we might match events that had the same number of attendees as the user id... or worse, if we compared on username, there may be a user named Rob and one named RobSmith and we'd match that.

So that's the SQL... and it works... so it shouldn't be too hard to write the rest

Please, when writing the rest, bear in mind whether the event is publicly viewable, i.e. that the calendar that it appears on is viewable.

[Benj]

legend

[MWetherspoon]

Question - does anyone know of any easy way to update the mod so that when a user signs up for an event, as opposed to just listing their post name, it actually uses their name as a link to their public profile?

For me that would be a handy feature as even organizers could easily pull the user info from the custom fields in the user profile that I have enabled on the site.

I'm going to play with it and see what I can come up with.

Thanks in advance!

- Mark

[SamirDarji]

Originally Posted by buro9

Several people have asked, and I had already sent them to one person, so I'll put them here, and if the hack author objects I'll remove them.

This is what I sent to the first person that asked:

In calendar.php the block of code you would have adjusted following:

PHP Code:

if (($show['candeleteevent'] OR $show['canmoveevent'] OR $show['caneditevent']) AND !$show['holiday']) 


I have this:

PHP Code:

    // HACK : START : ATTEND
    //if (($show['candeleteevent'] OR $show['canmoveevent'] OR $show['caneditevent']) AND !$show['holiday'])
    //{
    //  $show['eventoptions'] = true;
    //}
    //
    //eval ('$caldaybits .= "' . fetch_template('calendar_showeventsbit') . '";');

    if (($show['candeleteevent'] OR $show['canmoveevent'] OR $show['caneditevent']) AND !$show['holiday']) {
      $show['eventoptions'] = true;
    }

    if ($eventinfo['useroll']) {
      // Roll for this event
      $show['userattending'] = false;
      if (($roll = @unserialize($eventinfo['roll'])) && is_array($roll)) {
        uasort($roll, "strnatcasecmp");
        if (array_key_exists($bbuserinfo['userid'], $roll)) {
          $show['userattending'] = true;
        }
        while ($rollusername = current($roll)) {
           $rolluserid = key($roll);
           eval('$rollbits .= "' . fetch_template('calendar_rollbit') . '";');
           next($roll);
        }
      } else {
        $eventinfo['roll'] = "";
      }

      eval ('$eventinfo[roll] = "' . fetch_template('calendar_roll') . '";');
      // End Roll
    } else {
      $eventinfo['roll'] = "";
    }

    eval ('$caldaybits .= "' . fetch_template('calendar_showeventsbit') . '";');
    // HACK : END : ATTEND 


And then the calendar_rollbit becomes:

<li><a href="member.php?u=$rolluserid">$rollusername</a></li>

And the calendar_roll becomes:

<p><strong>People attending this event</strong>:</p>
<if condition="$rollbits">
<ul>
$rollbits
</ul>
<else />
<p><i>Nobody yet!</i></p>
</if>

<if condition="$bbuserinfo[userid] > 0">
<if condition="$show[userattending]">
	[<a href="calendar.php?$session[sessionurl]do=unattend&e=$eventinfo[eventid]">I will no longer be attending this event</a>]
<else />
	[<a href="calendar.php?$session[sessionurl]do=attend&e=$eventinfo[eventid]">I will be attending this event</a>]
</if>

</if>

Finally... find and correct the label title for the checkbox in the calendar_edit template... it should be:

<div><label for="cb_roll"><input type="checkbox" name="useroll" value="1" id="cb_roll" tabindex="3" $useroll />Allow users to specify that they will be attending this event.</label></div>

Some of that may not work in old versions of PHP, you'll have to try it and see

Here it is. This code doesn't include the duplicate member listing fix, so you'll have to implement that, but it's got everything else.

[MWetherspoon]

Thanks a ton SamirDarji - I had missed that note in the post by buro9 that he had added the link to the profile in the Roll Call hack!

Installed and working great!

Now to go back and fix the duplicate member fix!

[SamirDarji]

Yeah, I missed the fix to the unregistered user problem and spent a few good hours making the same fix. I would've hated to see you do the same.

[buro9]

Originally Posted by SamirDarji

Yeah, I missed the fix to the unregistered user problem and spent a few good hours making the same fix. I would've hated to see you do the same.

vBulletin.org needs CVS so that all such fixes can be rolled in by anyone rather than this hunting around hack threads thing!