Events Made Easy

Omschrijving

Evenementen Made Easy is een complete oplossing voor evenementen- en lidmaatschapsbeheer voor WordPress. Events Made Easy ondersteunt publieke, private, concept- en terugkerende evenementen, lidmaatschap en locatiebeheer, RSVP (+ optionele goedkeuring), verschillende betalingsgateways (Paypal, 2Checkout, FirstData, Mollie en anderen) en OpenStreetMap-integratie. Met Events Made Easy kunt u uw evenement plannen en publiceren, of mensen plaatsen laten reserveren voor uw wekelijkse vergaderingen. U kunt evenementenlijst, kalenders en beschrijving aan uw blog toevoegen met behulp van meerdere zijbalkwidgets of shortcodes; als u een webdesigner bent, kunt u eenvoudig de placeholders gebruiken die worden aangeboden door Events Made Easy.

Belangrijkste kenmerken:
* Openbare, privé-, concept- en terugkerende evenementen met aangepaste en dynamische velden in het RSVP-formulier
* Lidmaatschapsbeheer met aangepaste en dynamische velden
* Aanwezigheid rapportage voor evenementen en lidmaatschappen als de rsvp of qrcode van het lid wordt gescand door iemand met voldoende rechten
* Pagina- en berichtinhoud bescherming via lidmaatschappen of via shortcodes
* Druppel inhoud via lidmaatschappen
* Personen en groepen met aangepaste velden per persoon
* PDF-creatie voor lidmaatschap, boekingen en personen info
* Lidmaatschapskaart of boekingsticket kan automatisch als pdf via e-mail worden verzonden, met optionele QR-code om te scannen op aanwezigheids-/betalingsinformatie
* RSS- en ICAL-feeds
* Kalenderbeheer, met vakantie-integratie
* Verschillende widgets voor evenementen lijsten en kalender
* Locatiebeheer, met optionele OpenStreetMap integratie
* RSVP-boekingen met aangepaste velden en dynamische velden, betaling volgen, optionele goedkeuring, kortingen
* Templates voor e-mails, evenementen lijsten, afzonderlijke evenementen, feeds, RSVP-formulieren,… met specifieke tijdelijke aanduidingen voor elk
* Veel shortcodes en opties
* Betalingsgateways:Paypal, FirstGegevens, 2CheckOut, Mollie, Worldpay, Sagepay, Stripe, Braintree, Paymill, Instamojo, Mercado Pago
* Stuur e-mails naar geregistreerde mensen, stuur automatisch herinneringen voor betalingen
* Stuur automatisch herinneringen voor lidmaatschappen die bijna verlopen of zijn verlopen
* E-mail wachtrij en nieuwsbrief functionaliteit
* Mailings kunnen in de toekomst worden gepland, geannuleerd…
* Multi-site compatibel
* Heb verschillende AVG assistentiefuncties (persoonlijke informatie opvragen en bekijken via een link; oude records verwijderen voor mailings, deelnemers, boekingen)
* Volledig lokaliseerbaar en reeds volledig gelokaliseerd in het Duits, Zweeds, Frans en Nederlands. Ook volledig compatibel met (m) qtranslate (-xt):de meeste instellingen staan ​​taal tags toe, zodat je je evenementen in verschillende talen aan verschillende mensen kan laten zien. De boeking e-mails houden ook rekening met de gekozen taal.

Ga voor meer informatie, documentatie en het ondersteuningsforum naar de Officiële site.

Schermafdrukken

Installatie

Maak altijd een back-up van uw DB voordat u de upgrade uitvoert, voor het geval dat …
1. Upload de map events-made-easy naar de map /wp-content/plugins/
2. Activeer de plug-in via het menu ‘Plug-ins’ in WordPress
3. Voeg een evenementenlijst of kalenders toe volgens de instructies in de sectie Gebruik.

Gebruik

Na de installatie voegt Events Made Easy een menu “Evenementen” op het hoogste niveau toe aan uw WordPress-beheer.

  • Op de pagina Evenementen kunt u uw evenementen beheren. Op de pagina Nieuwe toevoegen kunt u een nieuwe gebeurtenis invoegen.
    Algemene EME-instellingen met betrekking tot RSVP-mails en sjablonen kunnen per gebeurtenis worden aangepast.
  • Op de pagina Locaties kunt u locaties rechtstreeks toevoegen, verwijderen en bewerken. Locaties worden automatisch toegevoegd met gebeurtenissen indien niet aanwezig, maar met deze interface kunt u uw locatiegegevens aanpassen en een afbeelding toevoegen.
  • Op de pagina Categorieën kunt u categorieën toevoegen, verwijderen en bewerken (als Categorieën zijn geactiveerd op de pagina Instellingen).
  • De pagina Vakanties wordt gebruikt om vakantielijsten in een kalender te definiëren en te beheren
  • Op de pagina Aangepaste velden kunt u aangepaste velden beheren die kunnen worden gebruikt voor evenementen, locaties, mensen, leden, lidmaatschappen en RSVP-definities
  • Op de pagina Templates kunt u aangepaste templates beheren voor evenementen, lidmaatschappen, e-mails, pdf-creatie, …
  • Op de pagina Kortingen kunt u kortingen en kortingsgroepen beheren die worden gebruikt in RSVP- of lidmaatschapsdefinities
  • De pagina Personen dient als een verzamelpunt voor de informatie over de mensen die een ruimte hebben gereserveerd voor een van uw evenementen of voor persoonlijke informatie van leden.
    Het kan ook worden gebruikt om aangepaste informatie toe te voegen voor een persoon op basis van de groep waarin hij zit, om de structuur van een organisatie weer te geven of om gewoon extra informatie op te slaan
  • De pagine Groepen
  • De pagina Goed te keuren boekingen wordt gebruikt om boekingen te beheren voor evenementen die goedkeuring vereisen.
  • De pagina Boekingen wijzigen wordt gebruikt om boekingen voor evenementen te wijzigen.
  • De pagina Leden wordt gebruikt om al uw leden te beheren (bijvoorbeeld lidmaatschapsstatus, aangepaste ledeninfo).
  • De pagina Lidmaatschappen wordt gebruikt om uw lidmaatschappen te definiëren en te beheren.
  • De pagina Landen/staten kan worden gebruikt om landen en staten (in verschillende talen) te definiëren voor persoonlijke informatie in lidmaatschaps- en RSVP-formulieren
  • Op de pagina E-mails verzenden kunnen mailings voor evenementen of algemene informatie worden gepland, gemaakt en beheerd (veel opties mogelijk)
  • De pagina Geplande acties wordt gebruikt om geautomatiseerde EME-taken te plannen (zoals herinneringen verzenden, onbetaalde boekingen annuleren, nieuwsbrief).
  • De pagina Opruimacties
  • De pagina Instellingen wordt gebruikt om generieke EME-standaardwaarden in te stellen voor evenementen, betalingsgateways, mailserver info, mail templates, …
  • Fijnmazig configureerbare toegangscontrole (ACL) voor het beheren van evenementen, locaties, boekingen, leden, …

Lijst met evenementen en kalenders kunnen aan uw blogs worden toegevoegd via widgets, shortcodes en sjabloontags. Raadpleeg de volledige documentatie op de ondersteuningspagina voor evenementen Made Easy Easy.

FAQ

Zie het FAQ gedeelte op de documentatie site.

Beoordelingen

23 september 2020
This is a trully great and genuinly free plugin for Events. No "pro" version, everything is included for free. The support also is good and friendly. Needs a bit of learning, still i haven't found anything as good and free as EME.
1 september 2020
I'm giving this 4 stars because in my search for an events plugin this seemed the best for my needs, and so far in my testing I think it will be. One important thing to note (and at least one person with a 1-star rating mentioned this), is that the bool datatype isn't supported in older mysql versions (I'm not sure why mine isn't the latest because I installed Xampp from Bitnami just a couple months ago), and 0000-00-00/0000-00-00 00:00:00 don't work as defaults for date/datetime fields. I tried modifying the file where the tables are created (then copied back to the Zip file I installed from) but I guess somewhere the version of mysql is being looked for, and in older versions the tables don't get created. There is no indication of this when installing the plugin; you'll only discover it when trying to add a location or event. Since my modifications to the PHP file didn't work, I just created the full SQL to create the tables by copying it out of the PHP file and making the necessary revisions: Bool fields: [field_name] bool DEFAULT 0 (or 1 if true) should be changed to [field_name] boolean DEFAULT false (or true) Date fields: [field_name] date DEFAULT '0000-00-00' should be changed to [field_name] date DEFAULT '1000-01-01' Datetime fields: [field_name] datetime DEFAULT '0000-00-00 00:00:00' should be changed to [field_name] datetime DEFAULT '1000-01-01 00:00:00' Here's the full SQL (note the error message you get when you try to add an event or location and table name is and make sure you follow that naming convention): CREATE TABLE wp_eme_events ( event_id mediumint(9) NOT NULL AUTO_INCREMENT, event_status mediumint(9) DEFAULT 1, event_author mediumint(9) DEFAULT 0, event_name text NOT NULL, event_slug text, event_url text, event_start_time time NOT NULL, event_end_time time NOT NULL, event_start_date date NOT NULL, event_end_date date DEFAULT NULL, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, event_notes longtext DEFAULT NULL, event_rsvp boolean DEFAULT false, use_paypal boolean DEFAULT false, use_2co boolean DEFAULT false, use_webmoney boolean DEFAULT false, use_fdgg boolean DEFAULT false, use_mollie boolean DEFAULT false, use_sagepay boolean DEFAULT false, price text, currency text, rsvp_number_days tinyint unsigned DEFAULT 0, rsvp_number_hours tinyint unsigned DEFAULT 0, event_seats text, event_contactperson_id mediumint(9) DEFAULT 0, location_id mediumint(9) DEFAULT 0, recurrence_id mediumint(9) DEFAULT 0, event_category_ids text, event_attributes text, event_properties text, event_page_title_format text, event_single_event_format text, event_contactperson_email_body text, event_respondent_email_body text, event_registration_recorded_ok_html text, event_registration_pending_email_body text, event_registration_updated_email_body text, event_registration_cancelled_email_body text, event_registration_paid_email_body text, event_registration_trashed_email_body text, event_registration_form_format text, event_cancel_form_format text, registration_requires_approval boolean DEFAULT false, registration_wp_users_only boolean DEFAULT false, event_image_url text, event_image_id mediumint(9) DEFAULT 0, event_external_ref text, UNIQUE KEY (event_id) ); CREATE TABLE wp_eme_recurrence ( recurrence_id mediumint(9) NOT NULL AUTO_INCREMENT, recurrence_start_date date NOT NULL, recurrence_end_date date NOT NULL, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, recurrence_interval tinyint NOT NULL, recurrence_freq tinytext NOT NULL, recurrence_byday tinytext NOT NULL, recurrence_byweekno tinyint NOT NULL, event_duration mediumint(9) DEFAULT 0, recurrence_specific_days text, holidays_id mediumint(9) DEFAULT 0, UNIQUE KEY (recurrence_id) ); CREATE TABLE wp_eme_locations ( location_id mediumint(9) NOT NULL AUTO_INCREMENT, location_name text NOT NULL, location_slug text, location_url text, location_address1 tinytext, location_address2 tinytext, location_city tinytext, location_state tinytext, location_zip tinytext, location_country tinytext, location_latitude tinytext, location_longitude tinytext, location_description text, location_author mediumint(9) DEFAULT 0, location_category_ids text, location_creation_date datetime DEFAULT CURRENT_TIMESTAMP, location_modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, location_image_url text, location_image_id mediumint(9) DEFAULT 0, location_attributes text, location_properties text, location_external_ref text, UNIQUE KEY (location_id) ); CREATE TABLE wp_eme_bookings ( booking_id mediumint(9) NOT NULL AUTO_INCREMENT, event_id mediumint(9) NOT NULL, person_id mediumint(9) NOT NULL, payment_id mediumint(9) DEFAULT NULL, status tinyint DEFAULT 1, booking_seats mediumint(9) NOT NULL, booking_seats_mp varchar(250), booking_approved boolean DEFAULT false, waitinglist boolean DEFAULT false, booking_comment text, event_price text, extra_charge tinytext, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, payment_date datetime DEFAULT '1000-01-01 00:00:00', booking_paid boolean DEFAULT false, received tinytext, remaining tinytext, pg tinytext, pg_pid tinytext, reminder INT(11) DEFAULT 0, transfer_nbr_be97 varchar(20), wp_id bigint(20) unsigned DEFAULT NULL, lang varchar(10) DEFAULT '', discount tinytext, discountids tinytext, dcodes_entered tinytext, dcodes_used tinytext, dgroupid INT(11) DEFAULT 0, attend_count INT(11) DEFAULT 0, UNIQUE KEY (booking_id), KEY (status) ); CREATE TABLE wp_eme_groups ( person_id mediumint(9) NOT NULL AUTO_INCREMENT, lastname tinytext, firstname tinytext, email tinytext NOT NULL, status tinyint DEFAULT 1, phone tinytext, wp_id bigint(20) unsigned DEFAULT NULL, address1 tinytext, address2 tinytext, city tinytext, zip tinytext, state tinytext, country tinytext, state_code tinytext, country_code tinytext, lang varchar(10) DEFAULT '', massmail boolean DEFAULT true, gdpr boolean DEFAULT false, properties text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, gdpr_date date, UNIQUE KEY (person_id), KEY (status) ); CREATE TABLE wp_eme_people ( person_id mediumint(9) NOT NULL AUTO_INCREMENT, lastname tinytext, firstname tinytext, email tinytext NOT NULL, status tinyint DEFAULT 1, phone tinytext, wp_id bigint(20) unsigned DEFAULT NULL, address1 tinytext, address2 tinytext, city tinytext, zip tinytext, state tinytext, country tinytext, state_code tinytext, country_code tinytext, lang varchar(10) DEFAULT '', massmail boolean DEFAULT true, gdpr boolean DEFAULT false, properties text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, gdpr_date date, UNIQUE KEY (person_id), KEY (status) ); CREATE TABLE wp_eme_categories ( category_id int(11) NOT NULL auto_increment, category_name tinytext NOT NULL, description text, category_slug text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (category_id) ); CREATE TABLE wp_eme_holidays ( id int(11) NOT NULL auto_increment, name tinytext NOT NULL, list text NOT NULL, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id) ); CREATE TABLE wp_eme_templates ( id int(11) NOT NULL auto_increment, name tinytext, description tinytext, format text NOT NULL, type tinytext, properties text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id) ); CREATE TABLE wp_eme_formfields ( field_id int(11) NOT NULL auto_increment, field_type tinytext NOT NULL, field_name tinytext NOT NULL, field_values text NOT NULL, admin_values text, field_tags text, admin_tags text, field_attributes tinytext, field_purpose tinytext, field_condition tinytext, field_required boolean DEFAULT false, export boolean DEFAULT false, extra_charge boolean DEFAULT false, searchable boolean DEFAULT false, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (field_id) ); CREATE TABLE wp_eme_events_cf ( answer_id int(11) NOT NULL auto_increment, event_id mediumint(9) DEFAULT 0, field_id int(11) DEFAULT 0, answer text NOT NULL, UNIQUE KEY (answer_id), KEY (event_id), KEY (field_id) ); CREATE TABLE wp_eme_locations_cf ( answer_id int(11) NOT NULL auto_increment, location_id mediumint(9) DEFAULT 0, field_id int(11) DEFAULT 0, answer text NOT NULL, UNIQUE KEY (answer_id), KEY (location_id), KEY (field_id) ); CREATE TABLE wp_eme_answers ( answer_id int(11) NOT NULL auto_increment, booking_id mediumint(9) DEFAULT 0, person_id mediumint(9) DEFAULT 0, member_id mediumint(9) DEFAULT 0, field_id int(11) DEFAULT 0, answer text NOT NULL, grouping int(11) DEFAULT 0, occurence int(11) DEFAULT 0, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (answer_id), KEY (booking_id), KEY (person_id), KEY (member_id) ); CREATE TABLE wp_eme_payments ( id int(11) NOT NULL auto_increment, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, random_id tinytext NOT NULL, member_id INT(11) DEFAULT 0, pg_pids text, pg_handled boolean DEFAULT false, UNIQUE KEY (id) ); CREATE TABLE wp_eme_discounts ( id int(11) NOT NULL auto_increment, name varchar(50) DEFAULT NULL, description tinytext, type tinyint UNSIGNED DEFAULT 0, coupon tinytext, dgroup tinytext, value tinytext, maxcount tinyint UNSIGNED DEFAULT 0, count tinyint UNSIGNED DEFAULT 0, strcase boolean DEFAULT true, use_per_seat boolean DEFAULT false, valid_from datetime DEFAULT NULL, valid_to datetime DEFAULT NULL, properties text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id), UNIQUE KEY (name) ); CREATE TABLE wp_eme_dgroups ( id int(11) NOT NULL auto_increment, description tinytext, name varchar(50) DEFAULT NULL, maxdiscounts tinyint UNSIGNED DEFAULT 0, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id), UNIQUE KEY (name) ); CREATE TABLE wp_eme_mqueue ( id int(11) NOT NULL auto_increment, mailing_id int(11) DEFAULT 0, person_id int(11) DEFAULT 0, member_id int(11) DEFAULT 0, status tinyint DEFAULT 0, creation_date datetime DEFAULT CURRENT_TIMESTAMP, sent_datetime datetime NOT NULL DEFAULT '1000-01-01 00:00:00', read_datetime datetime NOT NULL DEFAULT '1000-01-01 00:00:00', read_count int DEFAULT 0, receiveremail tinytext, receivername tinytext, replytoemail tinytext, replytoname tinytext, subject tinytext, body text, random_id tinytext NOT NULL, error_msg tinytext, attachments text, UNIQUE KEY (id), KEY (status) ); CREATE TABLE wp_eme_mailings ( id int(11) NOT NULL auto_increment, name varchar(50) DEFAULT NULL, planned_on datetime DEFAULT '1000-01-01 00:00:00', creation_date datetime DEFAULT CURRENT_TIMESTAMP, read_count int DEFAULT 0, total_read_count int DEFAULT 0, subject tinytext, body text, replytoemail tinytext, replytoname tinytext, mail_text_html tinytext, status tinytext, stats varchar(255) DEFAULT '', conditions text, UNIQUE KEY (id) ); CREATE TABLE wp_eme_members ( member_id int(11) NOT NULL auto_increment, membership_id int(11) DEFAULT 0, person_id int(11) DEFAULT 0, status tinyint DEFAULT 0, status_automatic boolean DEFAULT true, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, start_date date NOT NULL DEFAULT '1000-01-01', end_date date NOT NULL DEFAULT '1000-01-01', reminder INT(11) DEFAULT 0, reminder_date datetime DEFAULT '1000-01-01 00:00:00', renewal_count INT(11) DEFAULT 0, transfer_nbr_be97 varchar(20), payment_id mediumint(9) DEFAULT NULL, payment_date datetime DEFAULT '1000-01-01 00:00:00', paid boolean DEFAULT false, pg tinytext, pg_pid tinytext, extra_charge tinytext, discount tinytext, discountid INT(11) DEFAULT 0, dgroupid INT(11) DEFAULT 0, UNIQUE KEY (member_id) ); CREATE TABLE wp_eme_memberships ( membership_id int(11) NOT NULL auto_increment, name varchar(50) DEFAULT NULL, description tinytext, type varchar(50) DEFAULT NULL, start_date date DEFAULT '1000-01-01', duration_count tinyint DEFAULT 0, duration_period varchar(50) DEFAULT '', properties text, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (membership_id) ); CREATE TABLE wp_eme_memberships_cf ( answer_id int(11) NOT NULL auto_increment, membership_id mediumint(9) DEFAULT 0, field_id int(11) DEFAULT 0, answer text NOT NULL, UNIQUE KEY (answer_id), KEY (membership_id), KEY (field_id) ); CREATE TABLE wp_eme_countries ( id int(11) NOT NULL auto_increment, alpha_2 char(2) DEFAULT NULL, alpha_3 char(3) DEFAULT NULL, num_3 char(3) DEFAULT NULL, name varchar(100) DEFAULT NULL, locale tinytext, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id) ); CREATE TABLE wp_eme_states ( id int(11) NOT NULL auto_increment, code tinytext, name varchar(100) DEFAULT NULL, country_id int(11) DEFAULT NULL, creation_date datetime DEFAULT CURRENT_TIMESTAMP, modif_date datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, UNIQUE KEY (id) ); CREATE TABLE wp_eme_attendances ( id int(11) NOT NULL auto_increment, type varchar(20) DEFAULT NULL, person_id int(11) DEFAULT NULL, related_id int(11) DEFAULT NULL, creation_date datetime DEFAULT CURRENT_TIMESTAMP, UNIQUE KEY (id) );
24 juli 2020
It's work very well as shortcode - [eme_calendar author=#_MYSELF]. Each user can keep their own personal private calendar
26 maart 2020
It would be great if I could have added even a single event. Or if the video the developer posted showed how to do the MOST BASIC THING POSSIBLE... that being actually showing how to add a new event. And don't be fooled at over 40 minutes long, the video is NOT a "quick rundown". Every time I tried to add even a simple test event, I kept getting this type of error Table 'db822076813.ieThOZcyeme_events' doesn't exist
30 oktober 2019
Ich verwende EME seit mehreren Jahren und bin top zufrieden damit! Auch wenn es einem als Nicht-Programmierer schwer fällt, die ein oder andere persönliche Anforderung an das Plugin umzusetzen, die Möglichkeiten sind jedenfalls schier unendlich. Das Plugin wird ständig weiter entwickelt und realisierbare Feature-Wünsche werden auch umgesetzt.
22 oktober 2019
After several tested plugins for ticket bookings, I decided to go with EME because it is very flexible and you can get used to it very quickly. Also a good export function is built in order to be able to print booking lists. Very important: The developer regularly provides updates and responds quickly to notifications about bugs or new ideas/features/requests in the EME-forum. ... and it's absolutely free - which is a good reason for a donation (everyone has to pay for his coffee)! Keep it up...
Lees alle 96 beoordelingen

Bijdragers & ontwikkelaars

“Events Made Easy” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

“Events Made Easy” is vertaald in 7 talen. Dank voor de vertalers voor hun bijdragen.

Vertaal “Events Made Easy” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

2.1.92 (2020/09/20)

  • Fix jquery thing when checking for required fields
  • Fix the bug where the ical location format setting was not taken into account for the ical output (a fixed format was used)
  • Avoid using new reserved variable grouping in mysql 8.0.1
  • #_DELETEBOOKINGFORM allowed too (next to #_DELBOOKINGFORM)

2.1.91 (2020/09/02)

  • Fix the combo of calendar_day and location_id (corrects the redirection in case of 1 event and no longer ignores the calendar day if location_id is mentioned)
  • Allow to configure the attendance message for active members when the qr code is scanned by a person with enough rights
  • Added booking placeholders #_AMOUNTRECEIVED and #_AMOUNTREMAINING, so people can let others know how much they already paid and how much is remaining
  • Fix editing bookings with dyndata fields in the backend

2.1.90 (2020/08/29)

  • Improve search events when sending mail (you can now search all events, not just future ones)
  • Update Mollie API to v2.22.1
  • Add some more textual explanatioin to the mail templates settings to indicate when a mail is not being sent
  • If logged in, you can’t change your name/email for rsvp/memberships if not an admin. Log out if you want to enter other info then.
  • Added back the load_plugin_textdomain call, so the backend changes language based on the user language and not on the site language

2.1.89 (2020/08/14)

  • More resilient event CSV import
  • New shortcode [eme_members], to allow to show specific member info on a site
  • Jquery and phpmailer fix (the code mentioned by wordpress is wrong, so this needed a fix)

2.1.88 (2020/08/03)

  • Logic fix to be able to allow rsvp until 0 hours before the evend ends
  • Allow date to be set when manually adding an attendance
  • Correct some EME option explanations

2.1.87 (2020/07/27)

  • Sanitize fix for templates (was being too strict now …)
  • Captcha fix

2.1.86 (2020/07/27)

  • Fix #_MYSELF as an calendar day argument too
  • Added a search mail functionaility to allow to search all sent emails, even those not belonging to a specific mailing (if queuing is on)
  • Allow to add an attendance record manually
  • Added specific access rights to list or manage (add/delete) attendances
  • Fix showing values for option textarea fields (typo for showing option values if those were a html textarea)

2.1.85 (2020/07/24)

  • For new installations, the mail sending method now defaults to WP Mail and allows html by default too.
  • Update select2 to 4.1.0-beta.1
  • New option to redirect pages protected with EME memberships to a custom url. The original page will be added to the query string in the form of “redirect=URL”.
  • Allow author or contact_person to be “#_MYSELF” if you want to limit events to only those where you’re the author:
    [eme_events author=#_MYSELF]
    or the contactperson:
    [eme_events contact_person=#_MYSELF]
    or both of course 🙂
    This is also possible for the [eme_calendar] shortcode, and also for the event and calendar widget options.
  • Fix the access rights when updating a recurrence (it denied access even when it should be allowed to update)

2.1.84 (2020/07/11)

  • Localize multiprice too
  • Change the attendance field on RSVP forms from dropdown to checkbox, and add a class to it
  • Added the conditional placeholder #_IS_RSVP_STARTED
  • Reuse input from custom fields of type “people” in the frontend too
  • Make sure no newsletter mail is sent if no events are planned
  • Add a new menu to consult attendance reports on memberships or past events
  • Prepare for new 5.5 release of wordpress (5.5 has a newer phpmailer version included in a new location)
  • If booking approval is needed and auto-approve after payment is on and the price to pay is 0 (due to discount reduction for example), then mark the booking as approved and not pending
  • Attendance records are now stored (for events or memberships that want it) if an EME admin scans the RSVP attendance QRCODE or the member QRCODE

2.1.83 (2020/06/26)

  • Allow empty discounts being entered if no discount is required
  • Obey the ignore massmail setting for mailings to all people
  • Fix the #_RSVP_STATUS placeholder

2.1.82 (2020/06/23)

  • Fix the switch for Instamojo from sandbox to live
  • Fix hiding existing comments for memberships
  • Fix the newsletter functionality

2.1.81 (2020/06/13)

  • Hide comments/pings/trackbacks and disable comment form on pages that are members-only
  • Also hide the featured image for member protected pages
  • Renamed some global constants to avoid conflicts. If you use these in your functions, please verify and correct:
    STATUS_TRASH => EME_EVENT_STATUS_TRASH
    STATUS_PUBLIC => EME_EVENT_STATUS_PUBLIC
    STATUS_PRIVATE => EME_EVENT_STATUS_PRIVATE
    STATUS_DRAFT => EME_EVENT_STATUS_DRAFT
    RSVP_STATUS_ACTIVE => EME_RSVP_STATUS_ACTIVE
    RSVP_STATUS_TRASH => EME_RSVP_STATUS_TRASH
    PEOPLE_STATUS_ACTIVE => EME_PEOPLE_STATUS_ACTIVE
    PEOPLE_STATUS_TRASH => EME_PEOPLE_STATUS_TRASH
    MEMBER_STATUS_PENDING => EME_MEMBER_STATUS_PENDING
    MEMBER_STATUS_ACTIVE => EME_MEMBER_STATUS_ACTIVE
    MEMBER_STATUS_GRACE => EME_MEMBER_STATUS_GRACE
    MEMBER_STATUS_EXPIRED => EME_MEMBER_STATUS_EXPIRED
  • Allow online payments to succeed for membership extensions
  • Added #_SUBMIT to the list of filter form placeholders, so you can put the submit button (with custom text) wherever you want it
  • #_FILTER_CATS, #_FILTER_LOCS, #_FILTER_TOWNS and #_FILTER_COUNTRIES (and their #_EVENTFUL equivalents) now allow an argument to indicate the title for that search field
  • Added a setting to disable refunds globally

2.1.80 (2020/06/05)

  • #_ATTENDANCE_QRCODE and #_MEMBER_QRCODE now support an argument to define the size. The options: any number from 1 to 8 or the predefined sizes small (=1), medium (=2, the default), large (=4), huge (=8)
    Examples: #_ATTENDANCE_QRCODE{huge} or #_MEMBER_QRCODE{4}
    Since the default is 2, this can change the size of the generated image (it used to be 3 for #_ATTENDANCE_QRCODE). If your layout depends on this, please verify.
  • Revert an attempt to optimize the filter the_content
  • Added placeholders #_MEMBERNEXTENDDATE (identical to #_MEMBERENDDATE, but will give the end date of the next period if the person would pay again)
  • Member placeholder #_PAYMENT_URL now allows to pay for active members too, this also works for #_MEMBERSHIP_PAYMENT_URL

2.1.79 (2020/06/02)

  • Fix to allow non-ASCII characters in the global e-mail template settings (thanks to Sebastian Lisken)
  • The placeholders #_USER_HAS_CAP, #_USER_HAS_ROLE, #_USER_IN_GROUP, #_USER_IS_MEMBER_OF, #_IS_USER_MEMBER_PENDING and #_IS_USER_MEMBER_EXPIRED now also allow multiple arguments (separated by “,”)
  • Revert an attempt to optimize the filter the_title

2.1.78 (2020/05/30)

  • In the frontend, allow the edit of firstname, lastname or email in the rsvp/member form if the respective value is empty, even for logged in users. Also allow edit of all other info in the frontend (so people can correct their address, … on a subsequent signup)
  • Generate a payment id for imported members too
  • The placeholders #_ADDBOOKINGFORM_IF_USER_HAS_CAP, #_ADDBOOKINGFORM_IF_USER_HAS_ROLE, #_ADDBOOKINGFORM_IF_USER_IN_GROUP and #_ADDBOOKINGFORM_IF_USER_IS_MEMBER_OF now allow multiple arguments (separated by “,”) so you can e.g. show the form to only users that are in one of the mentioned EME groups, with certain rols, or if member of one of the mentioned memberships
  • Added an option so you can set the text when WP membership (login) is required for a membership
  • Added a new bulk action in the members admin interface so you can resend the mail for paid memberships
  • Improve the logic to send paid mails (if total price=0 due to a discount, it will be sent too)
  • Added an option to disable browser caching of pages (and I recommend activating it …)
  • Added attendance count to CSV export report for bookings
  • Added eme_if condition ‘notincsv’, so for ex. you can compare if a certain value is not in a CSV list (like groups/categories) and based on that show/hide stuff. Also added this as a test condition for dynamic data.
  • Fix the #_USER_HAS_ROLE placeholder

2.1.77 (2020/05/20)

  • Improve custom field purpose behaviour (you can use ‘generic’ again, to indicate a field can be used as a member or rsvp field and the usage of these 3 purposes has become a bit more blurred, so in fact ‘generic’ is no longer deprecated).
  • Use all available basic person info in RSVP/member forms when user is logged in
  • Officially add the eme_mymemberships shortcode (it already existed but just returned a comma-separated list of membership names, now it has a template/header/footer that can contain member and membership placeholders
  • Added placeholder #_RSVPSTART and corrected #_RSVPEND, these give in localized date/time the start or end date/time when rsvp can be done

2.1.76 (2020/05/02)

  • Improve paypal error output
  • PDF output now has a configurable font setting, which defaults to the unicode font “Dejavu Sans” (setting in section “Other”)
  • Add organizer info to google ld+json html header

2.1.75 (2020/04/24)

  • Actually release the new version …

2.1.74 (2020/04/23)

  • Make google metadata datetime headers show up in correct format for online-only events
    For that, the event placeholders #_STARTDATETIME_8601 and #_ENDDATETIME_8601 have been introduced
  • Refund made possible for paypal payments (not for existing stored payments though, since the stored paypal id was not the correct one to be able to refund)
  • Expand eme_for to allow also lists with a custom separator, and also allow #_LOOPVALUE (plus #URL_LOOPVALUE) and #_LOOPCOUNTER in the repeating content (see doc)
  • Fix copy/paste error that causes auto-approve after payment to not approve the booking

2.1.73 (2020/04/15)

  • Fix the usage of discount groups
  • Make sure sanitized event properties are stored in the event
  • Add Mercado Pago the the list of payment gateways
  • Fix some SQL for retrieving bookings for registered users

2.1.72 (2020/04/04)

  • Fix some undefined variables
  • Fix call to wp_kses when saving the EME access denied option

2.1.71 (2020/04/04)

  • Fix some undefined variables
  • Fix the location url for the google ld+json html header

2.1.70 (2020/04/02)

  • When adding a person, custom person field weren’t saved upon creation but only upon edit
  • Location admin interface overhaul
  • Added #_LOCATION_EXTERNAL_URL, as a location can now be totally online (virtual), physical or a combo (and then you might need the url)
  • Added eventAttendanceMode to google json+ld output for events
  • Existing filter eme_extra_event_headers_filter renamed to eme_extra_event_headers_json_filter, to indicate it is really only used for the json-part of the extra headers for an event
  • New filter eme_extra_event_headers_filter that can filter on other extra event headers being added (meta tags)
  • You can now receive partial payments for a booking too (only via the admin itf for bookings)
  • Added refund option (only for Mollie and Instamojo for now)
  • Updated Mollie api to 2.17.0

Oudere wijzigingen zijn te vinden in changelog.txt