RS EVENT multiday vs Tickera – Sell Tickets & Manage Events

“RS EVENT multiday” is an easy to use and highly flexible tool to manage and print posts as events by adding the sidebar-widget “RS EVENT multiday” and/or the functions rs_event_list(), rs_event_post() and rs_event_id(), which can be used in templates. It is based on the original “RS EVENT” by Robert Sargant. The plugin offers the possibility to add a “RS EVENT multiday” widget to the sidebar of your blog. It allows you to show a list of upcoming and/or past events. “RS EVENT multiday” includes three different functions, which can be used in templates. rs_event_list(), rs_event_post(), rs_event_id() FUNCTIONS First of all, the “RS EVENT multiday” widget adds the function rs_event_list() to your sidebar and you can costumize all the settings via the widget control panel at the backend of your blog. If you want to create designated pages to show an event list, you should create a special template file for the theme you use and add the function rs_event_list() manually to the code of your template. rs_event_list() This is the function used for the widget. Of course, it can be used in templates as well. It prints an unordered list of events according to the parameters given to it (see below). Both, the and the include class=”rsevent”, so you can costumize the output with stylesheets. Furthermore, the output can be customized with the parameters “html_list_v1”, “html_list_v2”, “html_list_v3” and “html_list_v4”. For details see the parameters-section below. Note: If you just want to get the return values from rs_event_list(), so they do not get printed, you should use the function rs_event_list_return(). rs_event_post() This function should be used in the single-post-template (usually the file single.php of your theme). It prints the date of the event. The output can be customized with the parameters “html_post_v1”, “html_post_v2”, “html_post_v3” and “html_post_v4”. For details see the parameters-section below. Note: If you just want to get the return values from rs_event_post(), so they do not get printed, you should use the function rs_event_post_return(). (This might be useful for e.g. Thematic themes.) rs_event_id() This function returns an array with IDs of posts, which include event-data. This array of IDs can then be used in other functions or loops. Each function can be customized by parameters. PARAMETERS The parameters are used to customize the functions (see above), if you use them within templates. If you use the sidebar-widget of “RS EVENT multiday”, you can make all the settings via the widget control panel at the backend of your blog. Please, have a look at the example below (“How to pass on parameters to one of the functions”) in order to see how it works. title (string) The widget-title in your sidebar. Not used, when the function is added to a template. default value: ‘Upcoming Events’ timespan (integer) The maximum distance into the future events will be retrieved for, in days. default value: 365 history (integer) The maximum distance into the past that events will be retrieved for, in days. This can also be set to a negative negative number, e.g. -2 to prevent events that are occuring in the next two days from appearing. default value: 0 date_format_1 (string) The style in which the date is formatted. date_format_1 is used for single-day events, for the end date of multi-day events, and for the start date of multi-day events if the two dates are NOT within the same year. default value: ‘d.m.Y’ date_format_2 (string) The style in which the date is formatted. date_format_2 is used for the start date of multi-day events if the two dates are within the same year. default value: ‘d.m.’ groupdateformat_y (string) The style in which the yearly headline date is formatted, if events are grouped by year. See also parameter group_by_year. default value: ‘Y’ groupdateformat_m (string) The style in which the monthly headline date is formatted, if events are grouped by month. See also parameter group_by_month. default value: ‘F’ groupdateformat_d (string) The style in which the daily headline date is formatted, if events are grouped by day. See also parameter group_by_day. default value: ‘d, l’ time_format (string) The style in which the time is formatted. Note: ‘second’ cannot be entered for event time and must not be used because of variable $fake_second (used to mark empty time value.) default value: ‘H:i’ time_connector (string) The sign(s) that are printed between the start-time and the end-time, if an end-time is entered. default value: ‘ – ‘ html_list_v1 (string) Used for rs_event_list(). Formats the output, if first date and time of an event is entered with “multi-day”-option off. default value: ‘ %DATE% @ %TIME% | %LOCATION% %TITLE% » read more « ‘ html_list_v2 (string) Used for rs_event_list(). Formats the output, if first date but no time is entered with “multi-day”-option off; if %TIME% is used here anyway (which usually does not make any sense), output of %TIME% equals “–:–“. default value: ‘ %DATE% | %LOCATION% %TITLE% » read more « ‘ html_list_v3 (string) Used for rs_event_list(). Formats the output, if “multi-day”-option is on and first date and end date is entered. default value: ‘ %DATE% - %ENDDATE% | %LOCATION% %TITLE% » read more « ‘ html_list_v4 (string) Used for rs_event_list(). Formats the output, if “multi-day”-option is on but no end date is entered. default value: ‘ %DATE% (multi-day) | %LOCATION% %TITLE% » read more « ‘ html_post_v1 (string) Used for rs_event_post(). Formats the output, if first date and time of an event is entered with “multi-day”-option off. default value: ‘ %DATE% @ %TIME% ‘ html_post_v2 (string) Used for rs_event_post(). Formats the output, if first date but no time is entered with “multi-day”-option off; if %TIME% is used here anyway (which usually does not make any sense), output of %TIME% equals “–:–“. default value: ‘ %DATE% ‘ html_post_v3 (string) Used for rs_event_post(). Formats the output, if “multi-day”-option is on and first date and end date is entered. default value: ‘ %DATE% - %ENDDATE% ‘ html_post_v4 (string) Used for rs_event_post(). Formats the output, if “multi-day”-option is on but no end date is entered. default value: ‘ %DATE% (multi-day event) ‘ max_events (integer) The maximum number of events to show. If this is set to 0, then all events will be shown. default value: 0 (i.e. show all) group_by_year (integer) value 0 = off, value 1 = on. If group_by_year is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same year. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_y default value: 0 (i.e. “off”) group_by_month (integer) value 0 = off, value 1 = on. If group_by_month is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same month. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_m default value: 0 (i.e. “off”) group_by_day (integer) value 0 = off, value 1 = on. If group_by_day is set, the function rs_event_list() outputs a date as a headline for all events, that take place within the same day. For multiday events, the first day of the event is used for grouping and every event shows up only once. The format of the date can be set with the parameter groupdateformat_y default value: 0 (i.e. “off”) no_events_msg (string) The output when the are no events within the set timespan. default value: ‘no upcoming events’ sort_order (string) Whether to list the events in ascending (value: ‘ASC’) or descending (value: ‘DESC’) date order. default value: ‘ASC’ category (integer) Show only events listed against posts in the category with this ID number. If this is set to 0, then all events will be shown. default value: 0 (i.e. show all) fulltext_active (integer) If this is set to 0, the wildcard %FULLTEXT% cannot be used for the HTML-Output of the Event-List and an excerpt for the wildcard %EXCERPT% is not created automatically, consequently, it has to be entered via the excerpt-box at the edit-post-page. You should disable %FULLTEXT% and set this to 0, if you do not need or use %FULLTEXT% and if you manually creat excerpts in order to improve the perfomance of the plugin RS EVENT multiday. default value: 1 (i.e. enabled and %FULLTEXT% can be used and excerpts are created automatically) loggedin (integer) Allows to hide the widget or the output of the function rs_event_list(). If this is set to 0, the list or the widget will only be visible to logged in users. default value: 0 (i.e. widget and function are visible to all) Customizing the html-output with wildcards The values “html_list_vX” and “html_post_vX” can be styled both for the widget (-> via the widget control panel) and within templates (please have a look at the example “How to pass on parameters to one of the functions” below). Simply use html-code and the following parameters: %URL% Outputs the URL of the event-post. %DATE% Outputs the start-date of the event, formatted as date_format_1 in _v1, _v2 and _v4 and as date_format_2 in _v3. %ENDDATE% Outputs the end-date of the event, formatted as date_format_2. %TIME% If a starttime and endtime is entered, the output is similar to %STARTTIME% time-connector %ENDTIME%. If just a starttime and no endtime is entered, %TIME% is similar to %STARTTIME%. %STARTTIME% Outputs the time when the event starts, if one is entered, formatted as time_format. %ENDTIME% Outputs the time when the event ends, if one is entered (can only be entered if a starttime exists), formatted as time_format. %LOCATION% Outputs an ordinary text value (if one is entered) which might be used to enter e.g. the location of the event. %TITLE% Outputs the title of the post. %FULLTEXT% Outputs the entire text of the post. (You can disable this wildcard to improve the perfomance of the plugin.) %EXCERPT% Outputs the excerpt of the post. If the %FULLTEXT% wildcard is disabled, an excerpt is not created automatically. Consequently, the excerpt-box at the edit-post-page has to be filled with text in order to output an excerpt when %FULLTEXT% is disabled. Please, also see the information for “fulltext_active” at the parameter section above. %ID% Outputs the ID of the post. How to pass on parameters to one of the functions Here is an example how to pass on some parameters to the function rs_event_list() [or rs_event_list_return()], when used within a template. It works similar with rs_event_post() [and rs_event_post_return()], just use the html_post_vX parameters instead of the html_list_vX parameters. Note: Parameters for the widget can be simply passed via the Widget-Panel of your blog-backend. 60, 'date_format_1' => 'm|d|Y', 'date_format_2' => 'm|d', 'html_list_v1' => ' %DATE%, %TIME% %TITLE% ', 'html_list_v2' => ' %DATE% %TITLE% ', 'html_list_v3' => ' %DATE% to %ENDDATE% %TITLE% ', 'html_list_v4' => ' %DATE% (multiday!!!) %TITLE% ', 'max_events' => 4, ); rs_event_list($argsevent); ?>

Tickera lets you sell tickets on WordPress, manage event registration, and run ticket sales end-to-end on your own domain. Create an event, add tickets, design beautiful PDF tickets with the built-in drag & drop Ticket Designer, deliver them with QR/Barcodes, and check in attendees at the door. You keep the revenue — no middleman fees taken by Tickera. For ticket scanning, use integrated Barcode readers. If you want mobile check-in on phones, our premium Checkinera apps for iOS/Android enable blazing-fast scanning – even offline after sync. There’s also a Checkinera web app that turns any modern browser into a fully-fledged check-in desk. ✅ Key features 🎟️ Sell event tickets on your site – you keep the revenue 🗂️ Manage events in WordPress — create, edit, duplicate, set dates/capacity, and control ticket types 🎨 Built-in drag & drop Ticket Designer with a live PDF preview, unlimited designs, and ready-made templates 🧾 PDF tickets with embedded QR/Barcode for fast entry 🧍 Event registration with buyer and attendee fields 💸 Ticket sales tools: multiple ticket types, limits, discount codes, fees, taxes 🚀 Fast check-in with barcode readers, Checkinera mobile apps (premium), or the web app 🧩 Works with most WordPress themes 🧪 Developer-friendly (actions and filters for customization) 🏷️ White-label ready 🕸️ Multisite support ━━━━━━━━━━━━━━━━ “These guys offer a whole different level of service… give them a go!” — James Farmer, WPMU DEV ━━━━━━━━━━━━━━━━ 🎨 Design beautiful tickets (new in 3.6) Make tickets people actually want to keep. The built-in Ticket Designer is a drag & drop editor with a live, pixel-perfect PDF preview — what you see on screen is exactly what your attendees receive. Start from a library of ready-made templates (Wedding, Concert, Conference, Gala Dinner, Festival, Theatre and more), or build your own unlimited designs and assign them per event or per ticket type. You can also restyle your storefront with selectable front-end themes (Minimal, Bold, or Dark) for a clean, modern look on your event, cart and checkout pages — or keep your own theme’s styling. Set it under Tickera > Settings > Appearance. Manage events & event registration Create and update events in WordPress, then capture event registration details for each attendee. 🧠 How it works Choose your payment gateway. Create an event and add one or more ticket types (e.g., Standard, VIP). Share your ticket sales page and take orders. Buyers receive PDF tickets with QR/Barcodes. At the venue, check in attendees with scanners, the Checkinera apps (premium), or the web app. 🎬 Video 💳 Payments Tickera plugin comes with 2Checkout, Custom Offline Payments, and Free Orders as built-in payment gateways. Need more options? Get Tickera Premium for gateways like: – Mollie (iDeal, Credit Card, Bancontact/Mister Cash, SOFORT, Overbooking, Bitcoin, PayPal, paysafecard, AcceptEmail) – PayPal Standard • PayPal PRO • 2Checkout • Stripe • Paymill • Authorize.net • PIN Payments • Vogue Pay • iPay88 • PayGate • OptimalPayments/Netbanx • Braintree • PayUMoney • PayTabs • White Payments • PayU Latam • Komoju • plus Custom Offline Payments & Free Orders. 🛒 WooCommerce compatible Already on WooCommerce? Sell tickets as WooCommerce products while Tickera handles e-ticket delivery and check-in. Learn more about Bridge for WooCommerce (premium add-on). 🪑 Seating & 🧾 forms (premium add-ons) 🪑 Assigned seating with Seating Charts – build seat maps; let buyers pick seats at checkout. 🧾 Custom attendee fields and exports with Custom Forms. 💼 Take a cut on multisite/marketplaces with Stripe Connect. For more, see the complete catalog: All Tickera add-ons. ━━━━━━━━━━━━━━━━ “In my opinion Tickera is the best ticket management solution available today on WordPress” – Anton Kozlov ━━━━━━━━━━━━━━━━ 📚 Documentation Getting started & setup: https://tickera.com/documentation-category/tickera/ Checkinera apps (iOS/Android): https://tickera.com/checkinera-app/ Checkinera web app: https://tickera.com/checkinera-web/ Bridge for WooCommerce: https://tickera.com/addons/bridge-for-woocommerce/ Seating Charts: https://tickera.com/addons/seating-charts/ Custom Forms: http://tickera.com/addons/custom-forms/ Need help? Browse full docs: https://tickera.com/documentation-category/tickera/ 🚀 Premium demo Want to try everything (including premium add-ons)? 👉 Request a demo access 🧰 Use cases Ticket sales for concerts, conferences, festivals, theatres, meetups, comedy shows Sports events (football matches, basketball, volleyball, tournaments, races) Event registration for workshops, classes, seminars, trainings, hackathons Attractions & venues (zoos, museums, galleries, exhibitions, theme/adventure parks) Tours & experiences (city tours, boat/ferry tours, winery/brewery tours, campus open days) Community & non-profit (church events, charity fundraisers, school/university events) Nightlife & hospitality (clubs, DJ nights, VIP lists, table/service packages) Seasonal & holiday events (markets, fairs, fireworks nights, Halloween/NYE) Corporate & product (launches, networking, town halls, partner events) Education & webinars (online events with attendee data collection) Theatre & cinema (screenings, premieres; seat selection via Seating Charts add-on) On-site logistics (entry lanes, staff/crew passes, vendor passes) Parking passes for events (sell/scan parking tickets to manage capacity) Multi-activity days (festival day passes, stage/area access levels) Timed entry windows (staggered arrivals, capacity control at the door) Sell tickets online and scan tickets on-site via QR/Barcode (readers, Checkinera apps, or web app) Event registration with per-attendee data (forms, exports) ━━━━━━━━━━━━━━━━ “Cannot recommend Tickera highly enough” – DJ Andy Ward ━━━━━━━━━━━━━━━━ External services Freemius manages upgrades to the premium license and handles premium licensing. Privacy policy: https://freemius.com/privacy/ TCPDF handles the rendering process of tickets, QR codes, and barcodes. Privacy policy: https://tcpdf.org/about/ Google Map API (maps.googleapis.com) renders the ticket template’s map element. Privacy policy: https://policies.google.com/privacy?hl=en-US Freegeoip.net collects customer geolocation information (e.g., City, ZIP) to pre-fill checkout payment forms. Privacy policy: https://freegeoip.live/privay-policy.html 2Checkout makes it possible to accept payments via the 2Checkout payment gateway. Privacy policy: https://www.2checkout.com/legal/privacy/ Tickera is used for pulling the list of add-ons offered in the Add-ons area of the plugin. Privacy policy: https://tickera.com/privacy/