Event Registration

[orangefrog]

Okay, I know this has probably been beatin to death, but I'm working on a site that really needs an event registration system. I've gone through the forum, like a hundred times, and have found several posts on this, but nothing works...except if I want to use eventbrite. Lol. Anyway, the best solution i found was this http://forum.cmsmadesimple.org/index.php/topic,16812.0/prev_next,prev.html#new

However, after following that idea step by step, word for word, it still doesn't work 100%. What happens is it pulls the events properly to the form builder, but it doesn't pull the events selected allt he way to the e-mail. So the person receiving the e-mails doesn't know what event has been selected.

Does anyone have an idea on how to fix this? Or, better yet, does anyone have a different idea that might work? I need calendar functionality with the option to register for events displayed in the calendar. I would like to go as far as having a payment method, but right now the registration is the most important part.

I don't mind if FEU are the only ones allowed to register either.

I would be willing to pay someone for this as a last resort as I really need this functioniality. Please, I'm begging here.

Here's what I'm using
CGCalendar 1.5.6
FrontEndUsers 1.12.3
CMS MS 1.8.2

[Dr.CSS]

I think this hooks in like you may need, you will have to look in forum for post on how to...

http://dev.cmsmadesimple.org/projects/availability

[Rolf]

Hi orangefrog,

I created a simple eventregistration system by using FormBuilder, FormBrowser and a little UDT. Only have it posted in the Dutch board at the moment:
http://forum.cmsmadesimple.org/index.ph ... 954.0.html

Perhaps you can translate it, using Google Translate.
Otherwise I will translate it soon, and also put it in the English T&T board (I was already planning this anyway)

Hope this helps,

Rolf 

[orangefrog]

Rolf,

Does this pull information (ie event title) from the calendar module? If it does, awsome. Nice bit of code I might add. And thanks fort he response, much appreciated.

Dr.CSS,

I've looked at the availability option before and couldn't get it to work the way I needed it. Thaks for the idea though. Much appreciated.

I think in the end, all i need is a 'register here' button in the calendar list/detail pages. Once clicked it needs to go to a form in form builder and display that pulled event title into the form. Then, it needs to send that event title in the e-mail to the site admin.

The option I tried above is exactly what i was looking for and need, but I can't get it to carry the event titles selected all the way through to the e-mail. I guess it was coded for an older version of CMSMS.

[lainyrache]

I am looking for pretty much the same thing.
I am now thinking  of trying paypal button maker with formbuilder. If anyone has any tips before i go all round the houses again it would be much appreciated.

[Rolf]

Does this pull information (ie event title) from the calendar module? If it does, awsome. Nice bit of code I might add. And thanks fort he response, much appreciated.

It is not created to use in combination with CGCalendar. But you can probably pull CGC info and use it in the page template.

For each event you have to create a Form and Browser.
Like I said it is a simple registration system. If you want it to use for dozens of events it isn't the best solution. But try it and see for yourself if it is effective for your purpose.

Regards, Rolf 

[orangefrog]

Thanks Rolf, but I don't think this will work even though it is a nice bit of code. The end user of this website is, well, to say it nicely a bit lacking in the internet knowledge. They wouldn't be able to do much of anything on the backend except for edit content. Which is why the solution that calguy cam up with was perfect.

CalGuy...if your out there, can you help me get your bit of code working with 1.8.2? I don't mind paying for your services. Please, I'm begging you here.

[calguy1000]

what bit of code?  I haven't written anything for event registration that I can recall.
though I have killed a fair amount of memory cells lately.

If I was to do event registration I would do a separate module that tied in to the ecommerce suite.. but that'd be an involved process, because to do it properly there are alot of considerations.

i.e:  - recurring events
        - capacity for the event
        - early booking discounts
        - cancellations
        - seat selections or different 'classes' of tickets
        - promotions / discounts
        - ticket / roster generation
       
this would not be a trivial module to write.

[orangefrog]

CalGuy! Ya!!! Form reading the post, this is what you cam up with a while ago

http://forum.cmsmadesimple.org/index.php/topic,16812.0/prev_next,prev.html#new

The issue is now is that it doesn't carry the event selected over to the e-mail part of Form builder. i got everything else to work but that. Is there a way to fix that?

And for argument sake, to build that registration event module, what would you charge me to do and what time frame would it take to get it done. You can let me know directly at production@orangefrogcreative.ca.

[kms]

Actually, I need an event registration system for CMSMS too, with all the demand and interest I'm surprised there is not a module already, it would be a great asset to the CMS. So the best thing I could come up with so far is just using Calguy's e-commerce modules and setting up the events as products, obviously I am not tying into a calendar module, but you can add an extra field to the product for the date, and then maybe do some sort of custom product listing to make a pseudo-calendar list of events? Just a thought. That's where I'm at and it might work, but I also need to have fields where the user enters the attendee info, that's where a real event registration system would help.

[Dr.CSS]

I'm sure he is more than willing to make one if you want to sponsor it...

[orangefrog]

I hope someone is. I don't know how many times I said i would pay for it. I really need it. If anyone wants to tackle this, please let me know. Again, I'm willing to pay for your time. Even if it's changing CalGuys original script to work properly with 1.8.2. I don't care right now, i just need something. Please help!

[calguy1000]

This topic has come up numerous times over the years  Numerous people have said 'I need an event or course registration module with these 5 dozen capabilties'... the problems historically have been that people have difficulty either scoping out the problem, or with investing the money that would take for this to be developed.  Or, thirdly priorities change and then nothing happens.

I've spent many hours scoping modules like this out a few times, a few different ways for different groups each with a similar set of core requirements, but with some custom requirements each time.  None of the proposals I've written have come to fruition.

So, I'm not gonna go any further with this until people realize that this project is a) complex, b) will take time to develop, c) is gonna be a large module in the scale of CGCalendar + Availability, and that d) the budget for this project would probably be between the $6k and $10k mark.

i.e:  The people that ask can you write a complete course registration solution for me in 5 days for around $350 have to look elsewhere.

Somebody will undoubtedly say that 'maybe we could get together to sponsor this'... well, that idea is a grand goal, but unfortunately that's been tried before too and didn't work out....

I hate to sound so negative, but I need people to realize that this issue has been examined numerous times, and has never worked out.  This is not a fault of any single person, or a flaw in any way with CMSMS or the way it's managed.  It's just a side-effect of the way the cooperative internet, and open source software works.

[orangefrog]

I know far too well the scope of projects like this. I regularly work on large projects. I also know the costs associated to these. Which is why I keep asking as well if some one could make the code you wrote a while a go work with 1.8.2. This I think is a much smaller job. Just having the event info in the cgcalendar module carry through to formbuilder and then to the e-mail (just like the previous code did), is really what i need right now.

Have you looked at the previous code? http://forum.cmsmadesimple.org/index.php/topic,16812.0/prev_next,prev.html#new
I know you wrote it as it says in a previous thread. And again, I've used it in the past and it worked like a hot damn as I was able to pretty much create the form as I needed it. Really, this is the best fix for me at this moment.

That all being said, I will talk with my client on the numbers you are thinking about here and if i can get the go ahead on it, would you be willing to have the module, after it is done a paid for, open to the community like all the other modules? I ask as i know some programmers are a bit protective of their code. And I can't promise they will go ahead with it, but they have gone for less of a project and paid more in the past.

Let me know your thoughts. Thanks for not running away on this already beatin to death topic.

[orangefrog]

Okay, I think I'm getting closer on the code that CalGuy put up a while ago. I selected the udt inthe submission part of the form builder form and it now carries the event all the way through, but now it won't e-mail the results and it comes up with this error...

Code: Select all

Warning: Illegal offset type in /home/ridgemea/public_html/modules/FormBuilder/classes/Form.class.php on line 571

Going through the file Form.class, it looks like it is a form id alias issue. Here's the form I have...

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<form id="10"
	alias="test">
		<form_name><![CDATA[test]]></form_name>
		<attribute key="next_button_text"><![CDATA[Continue...]]></attribute>
		<attribute key="prev_button_text"><![CDATA[Back...]]></attribute>
		<attribute key="css_class"><![CDATA[formbuilderform]]></attribute>
		<attribute key="unspecified"><![CDATA[[unspecified]]]></attribute>
		<attribute key="submit_action"><![CDATA[text]]></attribute>
		<attribute key="list_delimiter"><![CDATA[,]]></attribute>
		<attribute key="submit_response"><![CDATA[]]></attribute>
		<attribute key="inline"><![CDATA[0]]></attribute>
		<attribute key="required_field_symbol"><![CDATA[*]]></attribute>
		<attribute key="form_template"><![CDATA[{* DEFAULT FORM LAYOUT / pure CSS *}
{$fb_form_header}
{if $fb_form_done == 1}
	{* This first section is for displaying submission errors *}
	{if isset($fb_submission_error) && $fb_submission_error}
		<div class="error_message">{$fb_submission_error}</div>
		{if isset($fb_show_submission_errors) && $fb_show_submission_errors}
			<div class="error">
			<ul>
			{foreach from=$fb_submission_error_list item=thisErr}
				<li>{$thisErr}</li>
			{/foreach}
			</ul>
		</div>
		{/if}
	{/if}
{else}
	{* this section is for displaying the form *}
	{* we start with validation errors *}
	{if isset($fb_form_has_validation_errors) && $fb_form_has_validation_errors}
		<div class="error_message">
		<ul>
		{foreach from=$fb_form_validation_errors item=thisErr}
			<li>{$thisErr}</li>
		{/foreach}
		</ul>
		</div>
	{/if}
	{if isset($captcha_error) && $captcha_error}
		<div class="error_message">{$captcha_error}</div>
	{/if}

	{* and now the form itself *}
	{$fb_form_start}
	<div>{$fb_hidden}</div>
	<div{if $css_class != ''} class="{$css_class}"{/if}>
	{if $total_pages gt 1}<span>{$title_page_x_of_y}</span>{/if}
	{foreach from=$fields item=entry}
		{if $entry->display == 1}
        	{strip}
         	{if $entry->needs_div == 1}
            	<div
            	{if $entry->required == 1 || $entry->css_class != '' || $entry->valid == 0} class="
              		{if $entry->required == 1}required{/if}
              		{if $entry->css_class != ''} {$entry->css_class}{/if}
                    {if $entry->valid == 0} fb_invalid{/if}
              		"
            	{/if}
            	>
         	{/if}
         	{if $entry->hide_name == 0}
            	<label{if $entry->multiple_parts != 1} for="{$entry->input_id}"{/if}>{$entry->name}
            	{if $entry->required_symbol != ''}
               		{$entry->required_symbol}
            	{/if}
            	</label>
         	{/if}
         	{if $entry->multiple_parts == 1}
            	{section name=numloop loop=$entry->input}
               		{if $entry->label_parts == 1}
               			<div>{$entry->input[numloop]->input} {$entry->input[numloop]->name}</div>
               		{else}
               			{$entry->input[numloop]->input}
               		{/if}
               		{if isset($entry->input[numloop]->op) && $entry->input[numloop]->op}{$entry->input[numloop]->op}{/if}
            	{/section}
         	{else}
            	{if $entry->smarty_eval == '1'}{eval var=$entry->input}{else}{$entry->input}{/if}
         	{/if}
         	{if $entry->valid == 0} <--- {$entry->error}{/if}
         	{if $entry->needs_div == 1}
            	</div>
         	{/if}
         	{/strip}
     	{/if}
	{/foreach}
	{if $has_captcha == 1}
		<div class="captcha">{$graphic_captcha}{$title_captcha}<br />{$input_captcha}</div>
	{/if}
	<div class="submit">{$prev}{$submit}</div>
	</div>
	{$fb_form_end}
{/if}
{$fb_form_footer}]]></attribute>
		<attribute key="input_button_safety"><![CDATA[0]]></attribute>
		<attribute key="submit_javascript"><![CDATA[]]></attribute>
		<attribute key="redirect_page"><![CDATA[-1]]></attribute>
		<attribute key="submit_button_text"><![CDATA[Submit Form]]></attribute>
		<attribute key="predisplay_udt"><![CDATA[fb_form_test]]></attribute>
		<attribute key="display_udt"><![CDATA[fb_form_test]]></attribute>
	<field id="107"
		type="DispositionUserTag"
		validation_type=""
		order_by="1"
		required="0"
		hide_label="0"
		alias="">
			<field_name><![CDATA[Call UDT]]></field_name>
			<options>
			<option name="udtname"><![CDATA[fb_form_test]]></option>
			<option name="field_alias"><![CDATA[]]></option>
			<value></value>
			</options>
</field>
	<field id="71"
		type="TextField"
		validation_type="none"
		order_by="2"
		required="1"
		hide_label="0"
		alias="">
			<field_name><![CDATA[Your Name]]></field_name>
			<options>
			<option name="length"><![CDATA[80]]></option>
			<option name="field_alias"><![CDATA[]]></option>
			<option name="css_class"><![CDATA[]]></option>
			<option name="javascript"><![CDATA[]]></option>
			<option name="regex"><![CDATA[]]></option>
			<option name="default"><![CDATA[]]></option>
			<option name="clear_default"><![CDATA[0]]></option>
			<value></value>
			</options>
</field>
	<field id="72"
		type="PulldownField"
		validation_type=""
		order_by="3"
		required="1"
		hide_label="0"
		alias="">
			<field_name><![CDATA[Gender]]></field_name>
			<options>
			<option name="select_one"><![CDATA[Select One]]></option>
			<option name="sort"><![CDATA[0]]></option>
			<option name="option_name"><![CDATA[Male]]></option>
			<option name="option_name"><![CDATA[Female]]></option>
			<option name="option_value"><![CDATA[m]]></option>
			<option name="option_value"><![CDATA[f]]></option>
			<option name="field_alias"><![CDATA[]]></option>
			<option name="css_class"><![CDATA[]]></option>
			<option name="javascript"><![CDATA[]]></option>
			<value></value>
			</options>
</field>
	<field id="106"
		type="StaticTextField"
		validation_type=""
		order_by="4"
		required="0"
		hide_label="0"
		alias="static">
			<field_name><![CDATA[Static Text]]></field_name>
			<options>
			<option name="text"><![CDATA[{foreach from=$smarty.post.opts item='one'}
Selected Course: {$one}<br/>
{/foreach}]]></option>
			<option name="field_alias"><![CDATA[static]]></option>
			<option name="css_class"><![CDATA[]]></option>
			<option name="smarty_eval"><![CDATA[1]]></option>
			<value></value>
			</options>
</field>
	<field id="73"
		type="DispositionMultiselectFileDirector"
		validation_type=""
		order_by="5"
		required="1"
		hide_label="0"
		alias="saveit">
			<field_name><![CDATA[Selected Courses]]></field_name>
			<options>
			<option name="select_one"><![CDATA[Select One]]></option>
			<option name="destination_displayname"><![CDATA[Junk]]></option>
			<option name="destination_value"><![CDATA[Junk]]></option>
			<option name="destination_filename"><![CDATA[junk.txt]]></option>
			<option name="field_alias"><![CDATA[saveit]]></option>
			<option name="css_class"><![CDATA[hidden]]></option>
			<option name="javascript"><![CDATA[]]></option>
			<option name="file_path"><![CDATA[/home/ridegmea/public_html/uploads/images/rmc_event_files]]></option>
			<option name="file_template"><![CDATA[]]></option>
			<option name="file_header"><![CDATA[]]></option>
			<value></value>
			</options>
</field>
	<field id="74"
		type="DispositionEmail"
		validation_type=""
		order_by="6"
		required="0"
		hide_label="0"
		alias="">
			<field_name><![CDATA[Send It]]></field_name>
			<options>
			<option name="email_subject"><![CDATA[Test formbuilder submit]]></option>
			<option name="email_from_name"><![CDATA[Form Builder]]></option>
			<option name="email_from_address"><![CDATA[siteadmin@ridgemeadowschamber.com]]></option>
			<option name="destination_address"><![CDATA[siteadmin@ridgemeadowschamber.com]]></option>
			<option name="field_alias"><![CDATA[]]></option>
			<option name="html_email"><![CDATA[1]]></option>
			<option name="email_template"><![CDATA[<h1>FormBuilder Submission</h1>
<strong>Form Name</strong>: {$sub_form_name}<br />
<strong>Date of Submission</strong>: {$sub_date}<br />
<strong>Your server</strong>: {$sub_host}<br />
<strong>IP address of person using form</strong>: {$sub_source_ip}<br />
<strong>URL of page containing form</strong>: {$sub_url}<br />
<strong>FormBuilder version</strong>: {$fb_version}<br />
<strong>Tab Character</strong>: {$TAB}<br />

<hr />
<strong>Your Name</strong>: {$fld_71}<br />
<strong>Gender</strong>: {$fld_72}<br />
<strong>Selected Courses</strong>: {$saveit}<br />
]]></option>
			<option name="email_encoding"><![CDATA[utf-8]]></option>
			<value></value>
			</options>
</field>
</form>

If any one has any thoughts on this, that would be great as we can all use a simple event registration thingy. You can see what I'm trying to here to...

http://www.ridgemeadowschamber.com/index.php?page=community-event-calendar