<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>wpeventregister.com</title>
	<atom:link href="http://wpeventregister.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpeventregister.com</link>
	<description></description>
	<lastBuildDate>Sun, 16 Jun 2013 19:54:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>Tips &#8211; Closing Registration prior to Event</title>
		<link>http://wpeventregister.com/tips-closing-registration/</link>
		<comments>http://wpeventregister.com/tips-closing-registration/#comments</comments>
		<pubDate>Fri, 26 Oct 2012 15:36:44 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=391</guid>
		<description><![CDATA[I get alot of questions, comments and suggestions on how to handle closing the registration for an event.  This varies by every individual and every event, so I thought I would take a moment and describe how we designed the plugin to support this to best accomodate as many options as possible. As a developer [...]]]></description>
			<content:encoded><![CDATA[<p>I get alot of questions, comments and suggestions on how to handle closing the registration for an event.  This varies by every individual and every event, so I thought I would take a moment and describe how we designed the plugin to support this to best accomodate as many options as possible.</p>
<p>As a developer you are often challenged with designing software the meets the need of the masses, yet is taylored to meet each persons specific needs.  This is a broad yet specifi requirement.  In regards to how to close registration we have designed two primary methods.</p>
<p>1. Close registration based on the Start date/time of the event or on the End date/time of the event.  This is an option you check when you create your event.</p>
<p>2. Prevent registration based on fee availability.  By allowing fees to be available on days/times seperate from the event specific date, we can support things like Early Bird fees and Late Fees and normal fees.  With the date control you can have it set where only one fee is visible at a time.  If there are no fees available during a specific date or time, registration is closed at that time.</p>
<p><a href="http://wpeventregister.com/wp-content/uploads/2012/10/feedates.png"><img class="alignleft size-full wp-image-394" title="feedates" src="http://wpeventregister.com/wp-content/uploads/2012/10/feedates.png" alt="" width="283" height="128" /></a></p>
<p><a href="http://wpeventregister.com/wp-content/uploads/2012/10/nofees1.png"><img class="alignleft size-full wp-image-393" title="nofees" src="http://wpeventregister.com/wp-content/uploads/2012/10/nofees1.png" alt="" width="361" height="116" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Another great feature of the date control on the fees is that you can create events but not have them available for registration until the day a certain fee is active.</p>
<p>Hope that helps.</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/tips-closing-registration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Coordinator Module Changes and Guide</title>
		<link>http://wpeventregister.com/coordinator-module-changes-and-guide/</link>
		<comments>http://wpeventregister.com/coordinator-module-changes-and-guide/#comments</comments>
		<pubDate>Wed, 17 Oct 2012 04:31:07 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=380</guid>
		<description><![CDATA[For those of you who are using version 6.00.24 or later the coordinator module now supports the ability to include the custom questions and responses in the coordinator email.  The tag for this information is [custom].  Download the revised user guide here for the coordinator module  CoordinatorGuide]]></description>
			<content:encoded><![CDATA[<p>For those of you who are using version 6.00.24 or later the coordinator module now supports the ability to include the custom questions and responses in the coordinator email.  The tag for this information is <span style="color: #ff0000;">[custom].</span><span style="color: #ff0000;"> </span></p>
<p><span style="color: #ff0000;"><span style="color: #000000;">Download the revised user guide here for the coordinator module</span>  <a href="http://wpeventregister.com/wp-content/uploads/2012/10/CoordinatorGuide.pdf">CoordinatorGuide</a></span></p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/coordinator-module-changes-and-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release 6.00.24</title>
		<link>http://wpeventregister.com/new-release-6-00-24/</link>
		<comments>http://wpeventregister.com/new-release-6-00-24/#comments</comments>
		<pubDate>Wed, 17 Oct 2012 04:26:27 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=378</guid>
		<description><![CDATA[Today we released version 6.00.24.  This version has a few bug fixes that have been creating problems on the registration form with certain themes and plugins.  Additionally there were a few coding errors as well. One fix that occured in version 6.00.20 that created an issue was in the confirmation mails not showing all the [...]]]></description>
			<content:encoded><![CDATA[<p>Today we released version 6.00.24.  This version has a few bug fixes that have been creating problems on the registration form with certain themes and plugins.  Additionally there were a few coding errors as well.</p>
<p>One fix that occured in version 6.00.20 that created an issue was in the confirmation mails not showing all the tags as noted.  This has been addressed.</p>
<p>It is strongly recommended to deactivate and reactivate the plugin at least once after it is upgraded and activated for the first time.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/new-release-6-00-24/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Release 6.00.22</title>
		<link>http://wpeventregister.com/release-6-00-22/</link>
		<comments>http://wpeventregister.com/release-6-00-22/#comments</comments>
		<pubDate>Sun, 07 Oct 2012 23:56:24 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=364</guid>
		<description><![CDATA[Wow.  Nothing like a new release to keep you on your toes!.  My apologies for the bugs in 6.00.20 and 6.00.21.  This should solve both issues and additionally provide a new popup window format for the calendar that should be more cross theme compatible. Another note: Many of you have asked how to have the [...]]]></description>
			<content:encoded><![CDATA[<p>Wow.  Nothing like a new release to keep you on your toes!.  My apologies for the bugs in 6.00.20 and 6.00.21.  This should solve both issues and additionally provide a new popup window format for the calendar that should be more cross theme compatible.</p>
<p>Another note: Many of you have asked how to have the event details show/hide feature either default open or closed depending on the event.  I have modified the code, so that it is closed by default.  If you wish it to show open then on the event setup page, select Yes for show description on form and it will be default open.</p>
<p>Enjoy and thanks for the support.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/release-6-00-22/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Release 6.00.20 Now Available</title>
		<link>http://wpeventregister.com/release-6-00-20-now-available/</link>
		<comments>http://wpeventregister.com/release-6-00-20-now-available/#comments</comments>
		<pubDate>Sun, 07 Oct 2012 06:07:05 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=357</guid>
		<description><![CDATA[Today we released version 6.00.20. This release provides a few bug fixes as well as a few enhancements. This release should resolve issues where some of you have had double postings for your registrations. This release resolves PayPal sandbox issues. This release adds validation to ensure attendee names are entered on the confirmation page. Additionally [...]]]></description>
			<content:encoded><![CDATA[<p>Today we released version 6.00.20.</p>
<p>This release provides a few bug fixes as well as a few enhancements.<br />
This release should resolve issues where some of you have had double postings for your registrations.<br />
This release resolves PayPal sandbox issues.<br />
This release adds validation to ensure attendee names are entered on the confirmation page.</p>
<p>Additionally we have added a new shortcode feature for those of you who wish to provide a more robust public attendee list.</p>
<p><code>[EVR_CUSTOM_ATTENDEE event_id="" custom="" template=""]</code></p>
<p>To use:<br />
Create a page and place the shortcode on a page.<br />
A. Place the event ID of the event you wish to display attendee list of (must be between &#8220;).<br />
B. Place the question ID of the question you wish to display the response of. You can display multiple questions, using comma separation, i.e. &#8220;1,2,3&#8243; (must be between &#8220;).<br />
C. The next variable does not need definition for a default layout, however if you wish to custom layout your listing, you will need to create your custom template.<br />
D. When using a custom template, place &lt;table&gt;  before the shortcode and &lt;/table&gt; after the shortcode.<br />
IF you want to use a custom template in the template field, an example would be &lt;tr&gt;&lt;td&gt;{ATTENDEES}&lt;/td&gt;&lt;td&gt;{QA}&lt;/td&gt;&lt;/tr&gt;  which would display the list of attendees per registrant and any custom questions/responses.</p>
<p>Tags you can use are:<br />
{FIRST}, {LAST},{NAME},{ADDRESS},{CITY}, {STATE},{ZIP}, {EMAIL}, {PHONE}, {COUNT}, {TYPE}, {DATE}, {ATTENDEES}, {QA}</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/release-6-00-20-now-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release 6.00.19</title>
		<link>http://wpeventregister.com/new-release-6-00-19/</link>
		<comments>http://wpeventregister.com/new-release-6-00-19/#comments</comments>
		<pubDate>Thu, 13 Sep 2012 17:59:08 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=320</guid>
		<description><![CDATA[Well, it&#8217;s finally here. The next release of Event Registration for WordPress. The majority of changes are bug fixes: * Fixed slashes issue on Company default mail * Fixed php tag error in evr_three_cal file. * Fixed issue on export payment list to excel not showing payments * Fixed issue with questions * Fixed listing [...]]]></description>
			<content:encoded><![CDATA[<p>Well, it&#8217;s finally here. The next release of Event Registration for WordPress. The majority of changes are bug fixes:</p>
<p>* Fixed slashes issue on Company default mail<br />
* Fixed php tag error in evr_three_cal file.<br />
* Fixed issue on export payment list to excel not showing payments<br />
* Fixed issue with questions<br />
* Fixed listing style options for categories</p>
<p>In addition to the patch fixes, we have also resolve the issue with waitlist registration. You can once again accept waitlist registrations when your event reaches capcity.</p>
<p>We made a couple of changes to the Calendar:<br />
* Modified event names on calendar to truncate long names to prevent overrun of calendar<br />
* Fixed calendar event category color coding issue</p>
<p>Finally and most noteworthy is a revised sidebar widget, thanks to Crystal McNair for this contribution. This will impact all widget users, as your old widget will disapper. You will need to add the new widget back to your sidebar from the widget area.<br />
<img class="aligncenter size-large wp-image-321" title="newwidget" src="http://wpeventregister.com/wp-content/uploads/2012/09/newwidget-1024x276.png" alt="" width="540" height="145" /></p>
<p>Once you drag the widget to the sidebar, you will need to make a few settings and save it to make it active.  One of the nice features is that you can now make the widget category specific.</p>
<p><a href="http://wpeventregister.com/wp-content/uploads/2012/09/activewidget.png"><img class="alignleft size-full wp-image-322" title="activewidget" src="http://wpeventregister.com/wp-content/uploads/2012/09/activewidget.png" alt="" width="251" height="578" /></a></p>
<p> <br />
  Step 1:  Title your widget.</p>
<p>  Step 2: Enter the number of events you want the widget to display.</p>
<p>  Step 3: Select a category for your events.  This list is generated by the categories you have previously created in the category section of the plugin.</p>
<p>  Optional Step:  You can customize how the widget displays and what information is displayed.  See the directions and tags area of the widget for help.  It is recommended to not use any customization until you have verified the widget is working.</p>
<p>  Step 4/5:  Save your changes.</p>
<p>  Step 6: View the widget on your site.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/new-release-6-00-19/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Guide Changes</title>
		<link>http://wpeventregister.com/user-guide-changes/</link>
		<comments>http://wpeventregister.com/user-guide-changes/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:55:30 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=196</guid>
		<description><![CDATA[Wow, so many little changes! In an effort to provide the best support, we are working on updating our Online User Guide before we revise the PDF version of the User Guide. Please note that some of the links do not work yet, but check back, as we are making changes daily. The forum is [...]]]></description>
			<content:encoded><![CDATA[<p>Wow, so many little changes!  In an effort to provide the best support, we are working on updating our <a href="http://wpeventregister.com/instructions/">Online User Guide</a> before we revise the <a href="http://wpeventregister.com/wp-content/uploads/2012/05/EventRegistrationGuide_60008a.pdf">PDF version of the User Guide</a>.  Please note that some of the links do not work yet, but check back, as we are making changes daily.  The <a href="http://www.wpeventregister.com/forum">forum </a> is a great place to find answers and ask questions if you cant find what you need in either guide.</p>
<p>Between the guides and the <a href="http://www.wpeventregister.com/forum">forum </a>,  they should answer most of the basics and get you going.  You can email us directly at support@wpeventregister.com for any questions you cant find answers on the <a href="http://www.wpeventregister.com/forum">forum </a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/user-guide-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>We&#8217;re Back!</title>
		<link>http://wpeventregister.com/were-back/</link>
		<comments>http://wpeventregister.com/were-back/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:47:56 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=193</guid>
		<description><![CDATA[Well we are finally back and downloads are happening! Thanks for all your support and patience. We are now working on rev 6.00.19 with Version 6.00.18 available for download. Please note we have changed our support address to support@wpeventregister.com. Thanks for all your feedback, patience and support!]]></description>
			<content:encoded><![CDATA[<p>Well we are finally back and downloads are happening!  Thanks for all your support and patience.  We are now working on rev 6.00.19 with <a href="http://wordpress.org/extend/plugins/event-registration">Version 6.00.18</a> available for download.  Please note we have changed our support address to support@wpeventregister.com.</p>
<p>Thanks for all your feedback, patience and support!</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/were-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Changes, Changes, Changes!</title>
		<link>http://wpeventregister.com/hello-world/</link>
		<comments>http://wpeventregister.com/hello-world/#comments</comments>
		<pubDate>Sat, 28 Apr 2012 11:57:58 +0000</pubDate>
		<dc:creator>buck</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wpeventregister.com/?p=1</guid>
		<description><![CDATA[Welcome to our new URL.   As our product has grown in popularity we have had to slow down and fine tune things.  Sometimes things  get a bit messy with rapid growth, so we are taking a little time to do some cleanup, code revisions and address a few compliance issues.  These things do not represent [...]]]></description>
			<content:encoded><![CDATA[<p>Welcome to our new URL.   As our product has grown in popularity we have had to slow down and fine tune things.  Sometimes things  get a bit messy with rapid growth, so we are taking a little time to do some cleanup, code revisions and address a few compliance issues.  These things do not represent any security or product problems for you, our customer, but does affect how we are published in the WordPress.org site.  So we are gladly making the changes and look for increased popularity (and support!) for our product.</p>
<p>Our product has had tremendous growth over the last year, more than it first three years combined.  Your generous donations and support have allowed us to invest in development.   Also I would like to say thanks to all of you wonderful users who have given us ideas, suggestions and pointed out bugs.  We believe our product has grown by leaps and bounds in a positive way.  Your contributions in our <a href="http://wpeventregister.com/forum">forum</a> have been invaluable, as well  we hope the forum has been a help to you in finding solutions.</p>
<p>Over the next couple of months we will be striving to provide some product improvements, site and forum improvements and increased support.  So stay tuned and check back frequently.</p>
]]></content:encoded>
			<wfw:commentRss>http://wpeventregister.com/hello-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
