News – Events Manager for WordPress http://wp-events-plugin.com Event Registration, Bookings, Calendars, Locations Fri, 26 Jan 2018 08:43:40 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.2 17180428 Timezone support now available! http://wp-events-plugin.com/blog/2017/12/13/timezone-support-now-available/ http://wp-events-plugin.com/blog/2017/12/13/timezone-support-now-available/#comments Wed, 13 Dec 2017 17:52:17 +0000 http://wp-events-plugin.com/?p=3185 We’ve just released our latest beta/dev version for the upcoming release of 5.8.2, which includes the much-anticipated timezone support, allowing different events to have different timezones! We ask that anyone that has a staging server, or a local install to please try it out and let us know if you

The post Timezone support now available! appeared first on Events Manager for WordPress.

]]>
We’ve just released our latest beta/dev version for the upcoming release of 5.8.2, which includes the much-anticipated timezone support, allowing different events to have different timezones!

We ask that anyone that has a staging server, or a local install to please try it out and let us know if you experience any issues. Since we’re adding new fields to the database and UTC-based start/end times for previous events, we’d be interested to know of any issues experienced during the upgrade. We also certainly recommend backing up before upgrading, although any database modifications are completely backwards compatible with older versions.

You can install dev versions directly from your WordPress site, much like a regular update.

Timezone support will seem like a relatively subtle change from the outside (and it should just ‘work’), but from coding/architecture standpoint, it is another important building block to the foundation of the plugin that opens doors to other possibilities. We have already written a somewhat lengthy documentation article describing the changes for developers.

One major improvement out-the-gate is within event lists and displaying future/past events. Previous versions of Events Manager have always shown future events only taking dates into consideration, whereas now events that started a minute earlier (wherever in the world it may be) will now automatically be removed from that list and would appear on lists showing past events. Another important feature that will be coming soon (and is already in alpha stages – lack of timezone awareness was a blocker) is an importer/exporter which will be able to take timezones into consideration as well.

We’re really excited to get this feature out the gate and move onto even cooler features! Given the subtle yet fundamental changes to the plugin in this release, whilst this has already gone through extensive testing, we’re going to hold off until right after Christmas holidays before releasing an update.

Happy Holidays!

The post Timezone support now available! appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2017/12/13/timezone-support-now-available/feed/ 7 3185
Events Manager 5.8 http://wp-events-plugin.com/blog/2017/11/14/events-manager-5-8/ http://wp-events-plugin.com/blog/2017/11/14/events-manager-5-8/#comments Tue, 14 Nov 2017 09:08:35 +0000 http://wp-events-plugin.com/?p=3069 We’re pleased to announce the release of Events Manager 5.8. This announcement post will be longer than usual, as it adds a lot of under the hood improvements, loads of bug fixes, and a few new features to boot worth going over in more detail. One more thing… ;) whilst

The post Events Manager 5.8 appeared first on Events Manager for WordPress.

]]>
We’re pleased to announce the release of Events Manager 5.8. This announcement post will be longer than usual, as it adds a lot of under the hood improvements, loads of bug fixes, and a few new features to boot worth going over in more detail.

One more thing… ;) whilst there’s lots to cover in this release, we’re already nearing completion of our next update which will introduce timezone support to events. See the section further down for more details!

New Features and Improvements

Performance Improvements

We’ve made some important improvements to how events, bookings and locations are loaded which will yield significant performance improvements for many, most notably those with larger numbers of events and bookings. In some cases, we’ve seen a 90%+ decrease in database lookups for a single page, which translates to much faster page loads!

We’d love to talk more specifically about the improved areas, and we’ll do so further down in the developer notes, since it can be somewhat techy. One thing worth knowing, is that a specific improvement we’ve made has temporarily been limited so that it’s only applied if this line of code is added to your wp-config.php file:

define('EM_DISABLE_OPTIONAL_JOINS', true);

Whilst we’re quite happy with the results and have extensively tested this out, given the multitude of possible setting combinations available in EM, we can’t test them all and so we’d like to give the opportunity to everyone to try this out on their specific installs before we enable it by default in an upcoming release. If it doesn’t work for you, remove that line and let us know what went wrong on our support forums!

Event and Location List Grouping

A regularly requested feature is to be able to list upcoming events, but only show the first recurrence of each recurring event set. We’ve gone a step further to not only allow this sort of list, but to group lists by pretty much any field in our event and location tables! We’d like to introduce you to the new groupby, groupby_orderby and groupby_order attributes, which you can use in shortcodes and PHP search functions! By using these attributes, you can do things like retrieve or show:

  • a list of upcoming events, showing both single and recurring events, but only the next upcoming recurrence per recurring event.
  • a list of locations, but show the first alphabetical town per country.
  • a list of upcoming events, showing only the LAST upcoming event in each state

The possibilities are endless! Combined with our other search attributes, you can get even more creative:

  • a list of recurring events (no single events), belonging to a specific category, showing only the next event in each town located within a specific geographical radius.

This is a pretty powerful/complex feature which can quite easily be confused with the order and orderby options, so we’ve created some extra documentation to clarify the differences and give some examples as to how this can be used effectively.

New Placeholders and Conditional Placeholders

We’ve added a couple of new conditional and regular placeholders which will help you improve how you display your event information, and are also found in our documentation.

Placeholders

For Placeholders, we’ve added two useful ticket related ones, called #_EVENTPRICEMINALL and #_EVENTPRICEMAXALL. Similar to #_EVENTPRICEMIN/MAX placeholders, these show the minimum and maximum ticket prices, but include all ticket prices rather than just those available to that viewer at that specific time.

We’ve also added webcal placeholders, which is essentially ical links, but format the link using the webcal:// protocol rather than http(s):// which is useful for some calendar apps. These are available for individual events, locations, categories and tags, using the format #_xWEBCALLINK such as #_CATEGORYWEBCALLINK.

Conditional Placeholders

OK, so we haven’t ‘added’ a new conditional placeholder but we’ve improved how the category and tag conditional placeholders work, allowing much more flexibility. Now, you can include multiple tags or categories within the placeholder so only certain content is shown/hidden from users. Previously, you could only use one tag in the conditional placeholder:

{has_tag_cooking-class}Bring your own ingredients!{/has_tag_cooking-class}

Now, you could use multiple categories in one placeholder filter:

{has_tag_cooking-class,bbq}Bring your own ingredients!{/has_tag_cooking-class,bbq}

Important Notes for Developers

There’s various improvements here that we’d like to get techy about, especially since they may affect some developers working with the plugin.

Taxonomy objects have been rewritten

Whilst most developers, even those making use of our hooks to manipulate or extract information, this won’t affect you. However, it’s worth noting anyway. We’ve restructured our category and tag objects so that most of the heavy lifting is done by an abstract parent class. Much of the same logic required to manage both taxonomies are handled by one set of code which reduces the probability for errors, simplifies maintenance.

Aside from that, one important advantage for developers is that integrating a custom taxonomy for Events Manager has never been easier! Take a look at how we’ve done this with our own Category/Tag objects within the classes folder. With minimal amounts of code you can couple a taxonomy to Events or Locations and even make use of our placeholders automatically!

We’ve also renamed the these classes:

  • EM_Categories_Taxonomy > EM_Categories_Admin
  • EM_Category_Taxonomy  > EM_Categories_Frontend
  • EM_Tags_Taxonomy > EM_Tags_Admin
  • EM_Tag_Taxonomy > EM_Tags_Frontend

In case you’ve thought up of a scenario where you needed to use these classes outside the core plugin, you’ll want to tweak your code accordingly.

Optimized EM_Events and EM_Locations Lookups

This could also be considered a performance tweak, but worth mentioning separately as you can also implement these tweaks to your own code.

Previously, when loading events or locations of any kind, you’d want to first obtain a specific number of events (e.g. limit to 20 events) and also know how many events in total are available, in case you’d like to add a ‘more events’ link, or some sort of pagination style. Previously, this required two functions which forced two separate SQL calls:

$events = EM_Events::get( array('limit' => 20, 'pagination' => 1) );
$events_count = EM_Events::count();
...

If you’re using the above code (note the use of ‘pagination’), we recommend making a small tweak. Now, only one lookup is needed, as we also determine the total number of events without limits in the same query, and store it in a static variable like so:

$events = EM_Events::get( array('limit'=> 20, 'pagination' => 1) );
$events_count = EM_Events::$num_rows_total;

You can also access the EM_Events::$num_rows to determine how many events were actually returned by the ‘get’ statement, rather than running count($events) on the above code. Those of you that regularly use $wpdb will notice the similarity.

Performance Tweaks

As mentioned further up, we’ve made some important tweaks that can dramatically improve performance in some areas of the plugin. This specifically revolves around events, locations and bookings. We’d like to talk a little more about it here…

For locations and events, we’ve leveraged the use of WordPress’ caching features. This enables two significant performance improvements; firstly when displaying the same event on different parts of the page (for example viewing an event list/page with another events widget on the sidebar), Events Manager does not need to recreate the object each time, saving unnecessary database lookups and overhead. Secondly, if you’re using caching plugins which leverage object caching you’ll also see performance improvements from page to page, since reloading the same page does not require a trip to the database when looking up the same event.

Aside from caching, we’ve also improved our SQL statements so that when searching for events or locations, we won’t search (join) the events or locations tables unless it’s necessary.

The way bookings are retrieved and totals are calculated have been rewritten to optimize performance. In short, individual bookings of an event are not loaded for reference unless absolutely necessary, and not loaded at all when counting bookings such as pending bookings, confirmed bookings, booking totals, etc. This has shown huge performance gains by dramatically reducing the number of SQL queries on a single page load, especially when dealing with events containing hundreds or thousands of bookings.

One more thing…

We’ve been working on another greatly anticipated feature… Timezone support! We were hoping to add this to 5.8, but as development ensued, it became clearer that this is a pretty big feature in terms of the subtle yet fundamental changes required in terms of coding. Therefore, we decided to firstly release all the other improvements we had already and follow up with a beta of this new feature in the form of a dev version that anyone can test out and provide us with feedback before we release it.

Whilst it should only be a matter of days until we release the beta (likely to be named 5.8.0.1 and released officially as 5.8.1), we’ll follow up with another post dedicated to what’s coming in terms of timezone support.

Changelog

Last but not least, here’s the full list of specific changes/improvements/fixes we’ve made in Events Manager 5.8. Enjoy!

  • fixed category color picker and image uploader problems
  • created base classes for EM taxonomies to make adding custom EM taxonomies even easier in the future,
  • added tag image and color settings/data
  • added sortable option for date columns of events and recurring events in the admin area
  • fixed saving an event recreating ticket_meta and wiping out ML settings
  • fixed multilingual translations of event in WPML not hiding/showing right meta boxes
  • fixed saving multilingual translation of event overwriting original language ticket names
  • changed admin headers to use new and accessible WP inline HTML structure
  • fixed serialization problems for deprecated event/location attributes and attributes with multiple post meta entries for one post
  • removed deprecated attributes editor from admin area as this is confusing and error prone when combined with other plugins manipulating custom fields
  • fixed #_EVENTEXCERPT without arguments stripping HTML since 5.7
  • added ability to list multiple categories/tags in conditional placeholders e.g. {has_tag_123,1234,tagname}…
  • added #_EVENTPRICEMINALL and #_EVENTPRICEMAXALL to show prices of unavailable tickets as well
  • fixed JS issues with MS Global mode and JS file limiting when displaying subsite single event pages on main blog
  • fixed single initial abbreviation issues in Chinese calendars
  • fixed duplicate events not being published to social networks via jetpack publicize (kudos @gnaag)
  • fixed potential incompatibilities with other plugins using wp_query_reset() on category pages, preventing our page formats from showing
  • fixed taxonomy archive pages returning zero results if taxonomy formatting is disabled and events are excluded from searches (WP Bug workaround)
  • fixed inconsistent line ending causing warnings with PHP compatibility checker
  • unified Tag and Category class functions into sets of parent class functionn
  • fixed PHP fatal error with BP when disabling notifications
  • fixed calendar day links being incorrect if another plugin adds querystring params to permalinks
  • added groupby, groupby_orderby and groupby_order arguments allowing grouping in search results for events and locations
  • improved validation and sanitization of orderby arguments to avoid ambiguous field SQL errors
  • added optimization to optionally join event/location tables when needed for grouped searches or if EM_DISABLE_OPTIONAL_JOINS is defined and set to true
  • moved condition of when argument ‘bookings’ = ‘user’ to EM_Object so it’s accessible by EM_Location too
  • changed default ‘recurring’ argument to null so that non EM_Events searches can by default avoid the recurring conditional being generated
  • added grouping to AJAX response for event_map shortcode and function resulting in performance improvements
  • fixed use of get_terms via deprecated two argument method
  • fixed recreation of tickets for a recurring event having wrong start/end ticket dates
  • fixed custom fields with a 0 value getting deleted instead of saved
  • fixed/changed – shortened SQL search conditions when filtering by array or comma list of event/location ids
  • fixed escaping of apostrophes on search term placeholder
  • added optimized result counts (EM_Events::$num_rows and EM_Events::$num_rows_total) in EM_Events::get() to reduce number of SQL calls
  • added optimized result counts (EM_Locations::$num_rows and EM_Locations::$num_rows_total) in EM_Locations::get() to reduce number of SQL calls
  • changed as a result of the above two additions above we tweaked various event list areas to half number of SQL queries run per list
  • added no_results_msg argument to EM_Events::output() functions for custom ‘no events found’
  • added location_status and event_status search arguments to event and location searches respectively
  • fixed column alignment issues when using quick edit for events in wp dashboard
  • tweaked excerpt filters and reduced redundant calls to our the_content filters (reducing overhead)
  • changed event page the_content loading so it only shows when in_the_loop() and is_main_query() is true
  • fixed issues with WordPress SEO plugin breaking the wp editor front-end
  • added event list default sorting options to locations, tags and categories
  • added em_wp_is_super_admin() replacing is_super_admin() in anticipation of its deprecation
  • changed and optimized postmeta saving process to reduce number of rows by up to 80% per event,
  • optimized events table to save NULL values when possible
  • changed/removed unused event_category_id field from events table
  • added em_object_can_manage filter
  • fixed nested attributes such as {cond}#_ATT{name}{/cond} not being parsed properly
  • fixed some installation SQL PHP errors/warnings
  • fixed capability mapping problems if revisions enabled for events or locations
  • added WEBCAL placeholders to events, locations, categories and tags (e.g. #_EVENTICALLINK > #_EVENTWEBCALLINK)
  • removed unnecessary SQL queries for undeclared wp_options reducing number of queries made per page load
  • tweaked settings page textarea elements to be wider
  • added (possibly temporary) EM_FORCE_RECURRENCES_SAVE constant forcing status save for when recurrences change status,
  • fixed EM_Event::set_status_events() which was not working correctly and now also runs a em_event_set_status_events filter
  • fixed recurring events warning text not appearing in front-end editor if first submission produced validation errors
  • performance improvements to EM_Bookings and EM_Ticket objects by preventing pre-loading of all bookings on instantiation and when querying availability
  • added cache optimization for event and location loading,
  • improved optimized loading of EM_Location via em_get_location() by checking globals first,
  • changed bookings/tickets template for event editor to avoid loading all bookings for counting purposes
  • added $include_adjustments argument to get_price_pre_taxes and get_price_post_taxes for calculation of prices without discounts/surcharges (those making use of the em_booking_get_price_post_taxes and em_booking_get_price_pre_taxes filters should check for this passed argument in their custom code)
  • fixed bug where event categories saved via quick or bulk edit in multisite global mode aren’t reflected in subsite event lists filtering by that category
  • fixed events created before changing to multisite and enabling global mode not displaying images via placeholders
  • fixed bug in filter em_ticket_get_post where function argument $post was not passed on
  • improved taxonomy color retrieval so it makes use of caching
  • improved/optimized deletion of multiple bookings and tickets at once if belonging to an event
  • fixed my_bookings shortcode outputting content at top of content irrespective of where it is located within content
  • fixed invalid recurrence ticket start/end cut-off date/times if both are not set for the recurring event
  • fixed bug where ticket start/end dates cannot be unset in recurring events

The post Events Manager 5.8 appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2017/11/14/events-manager-5-8/feed/ 13 3069
Events Manager 5.6.6.1 http://wp-events-plugin.com/blog/2016/09/04/events-manager-5-6-6-1/ Sun, 04 Sep 2016 16:00:03 +0000 http://wp-events-plugin.com/?p=3003 This is a minor update which fixes an issue which cropped up in the 5.6.6 update where search forms disappear when search form styling is turned off in the admin settings. The reason for this bug was due to changes in 5.6.6 where the search form was updated to become ADA

The post Events Manager 5.6.6.1 appeared first on Events Manager for WordPress.

]]>
This is a minor update which fixes an issue which cropped up in the 5.6.6 update where search forms disappear when search form styling is turned off in the admin settings.

The reason for this bug was due to changes in 5.6.6 where the search form was updated to become ADA compliant. If your search form has disappeared from your events and locations search pages please update and refresh your search pages (including flushing the caches if you have any) it should reappear again.

 

The post Events Manager 5.6.6.1 appeared first on Events Manager for WordPress.

]]>
3003
Events Manager 5.6.6 http://wp-events-plugin.com/blog/2016/09/02/events-manager-5-6-6/ Fri, 02 Sep 2016 14:54:05 +0000 http://wp-events-plugin.com/?p=3001 Events Manager 5.6.6 fixed various issues and made a few minor improvements. One fixed issue in particular that cropped up in WordPress 4.6 and prompted this update to come out early was for themes that enable thumbnails/featured images for a specific subset of custom post types and throw a PHP error/warning. Additionally,

The post Events Manager 5.6.6 appeared first on Events Manager for WordPress.

]]>
Events Manager 5.6.6 fixed various issues and made a few minor improvements. One fixed issue in particular that cropped up in WordPress 4.6 and prompted this update to come out early was for themes that enable thumbnails/featured images for a specific subset of custom post types and throw a PHP error/warning.

Additionally, we’ve made some improvements to the ical feed format, providing more information about the event.

Whilst on the topic of ical feeds…. we’ve got an awesome Import/Export add-on we’ve been working hard on which will enable you to sync with any valid ical feed. That includes sites running Events Manager, Google Calendar among others! It’ll be capable of much more, this is just a teaser of what’s to come ;) We’ll be announcing the beta release of this new feature in the coming weeks with more info about what it can do. This will start off as a closed beta available to all Pro customers.

Stay tuned!

5.6.6 Changes

  • improvements to ical formatting, including static/unique UIDs, more accurate locations with geo coordinates, categories and featured image
  • replaced code using stripslashes() with wp_unslash() (kudos @webaware)
  • removed use of jQuery.live() on settings page
  • tweaked event search form elements and events list table to be ADA compliant
  • added $EM_Ticket_Booking to em_tickets_bookings_add filter arguments
  • removed translations of weekdays within EM and using WP translations instead,
  • changed calendar templates to stop using ucfirst() to uppercase month first letters since it breaks some languages and the languages that need it don’t capitalize their months anyway
  • fixed anonymous event submitter info not showing in recurring event admin area
  • fixed wrong nav id in BuddyPress (kudos @lyevalley)
  • fixed ‘no location’ checkbox not remaining checked if event submission returns a validation error
  • tweaked templates/forms/event/location.php and added some extra output sanitization
  • fixed 404 errors in calendar links to eventful day list for a specific location
  • fixed syncing of tables when WP uses utf8mb4 collation which causes errors when saving emojis in post content
  • fixed WP 4.6 PHP warnings and featured image problems when using a theme that limits specific CPTs to use thumbnails
  • fixed action typo in EM_Ticket::get_post() from em_location_get_post_pre to em_ticket_get_post_pre
  • fixed location not showing up in admin area within dropdown if previously assigned to an event but not available to user due to permission changes

The post Events Manager 5.6.6 appeared first on Events Manager for WordPress.

]]>
3001
Events Manager 5.6.5 http://wp-events-plugin.com/blog/2016/07/06/events-manager-5-6-5/ http://wp-events-plugin.com/blog/2016/07/06/events-manager-5-6-5/#comments Wed, 06 Jul 2016 18:57:24 +0000 http://wp-events-plugin.com/?p=2983 We’ve just released 5.6.5 which is a minor release mainly aimed at the new changes in Google’s Maps API policy, requiring all new sites to start supplying an API key in order to produce maps. This was a sudden announcement by Google with no advanced warning, though it seems that

The post Events Manager 5.6.5 appeared first on Events Manager for WordPress.

]]>
We’ve just released 5.6.5 which is a minor release mainly aimed at the new changes in Google’s Maps API policy, requiring all new sites to start supplying an API key in order to produce maps.

This was a sudden announcement by Google with no advanced warning, though it seems that only sites starting to use Google Maps from June 22 onwards are mostly affected (for example, we haven’t added an API key to our demo site yet).

Google still offers a free API key if your site serves up to 25,000 maps a day, which should suffice for most. We suggest you take a look at their grandfathering plan for sites using Maps before their cut-off date, and we’d suggest getting an API key anyway to avoid any sudden surprises.

Here’s a list of changes to the plugin:

  • added option to add Google Maps API key (located in Events > Settings > Formatting > Maps)
  • fixed category image uploader not working properly on some specific setups
  • fixed display issues of first/last names mixing middle names in booking admin tables under no-user mode
  • fixed #_TAGSLUG not being parsed
  • fixed blank space in email triggering validation errors when booking
  • fixed ‘view bookings’ ticket link pointing to back-end when on front-end

The post Events Manager 5.6.5 appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2016/07/06/events-manager-5-6-5/feed/ 4 2983
Events Manager 5.6.4 (minor release) http://wp-events-plugin.com/blog/2016/05/02/events-manager-5-6-4-minor-release/ http://wp-events-plugin.com/blog/2016/05/02/events-manager-5-6-4-minor-release/#comments Mon, 02 May 2016 17:27:48 +0000 http://wp-events-plugin.com/?p=2956 Events Manager 5.6.4 is a minor maintenance release that fixes a few compatibility issues with WP FullCalendar 1.x as well as some category related issues: fixed WP FullCalendar (versions using FC 2.x library) not showing events outside current month fixed long events not showing on last day in WP FullCalendar fixed

The post Events Manager 5.6.4 (minor release) appeared first on Events Manager for WordPress.

]]>
Events Manager 5.6.4 is a minor maintenance release that fixes a few compatibility issues with WP FullCalendar 1.x as well as some category related issues:

  • fixed WP FullCalendar (versions using FC 2.x library) not showing events outside current month
  • fixed long events not showing on last day in WP FullCalendar
  • fixed event category and tag pages 404-ing when slugs match taxonomy slugs and these pages aren’t parents of events page
  • fixed image upload buttons not working properly on event category add/edit pages of WP Dashboard

The post Events Manager 5.6.4 (minor release) appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2016/05/02/events-manager-5-6-4-minor-release/feed/ 2 2956
Pro 2.4.4.2 – Important Update from 2.4.4 http://wp-events-plugin.com/blog/2016/05/02/pro-2-4-4-2-important-update-from-2-4-4/ Mon, 02 May 2016 13:09:44 +0000 http://wp-events-plugin.com/?p=2952 We’ve discovered a bug in Events Manager Pro which was introduced in the 2.4.4 update which can accidentally delete bookings when ALL the following are met: You’re using the Multiple Bookings Mode Beta feature The booking was made using our PayPal gateway You’ve set PayPal bookings to auto-delete after x minutes

The post Pro 2.4.4.2 – Important Update from 2.4.4 appeared first on Events Manager for WordPress.

]]>
We’ve discovered a bug in Events Manager Pro which was introduced in the 2.4.4 update which can accidentally delete bookings when ALL the following are met:

  • You’re using the Multiple Bookings Mode Beta feature
  • The booking was made using our PayPal gateway
  • You’ve set PayPal bookings to auto-delete after x minutes if they haven’t been paid
You’ll notice an approved transaction in the transactions table, yet if you click on the multiple booking record you won’t see any individual event bookings associated with it, as these have been deleted. This will only affect bookings made from the time you updated the plugin to 2.4.4.
Update: This also seems to affect Authorize.net bookings, however the bookings don’t get deleted, the individual event bookings remain in ‘Processing’ status and require manual approval, although the Multiple Booking itself shows as approved with a completed transaction. The solution here is to update and manually approve the individual event bookings. To avoid sending another email confirmation, change the status individually within the edit page of the booking and uncheck the ‘send email’ checkbox.
The update 2.4.4.2 fixes this issue, and therefore we strongly urge you to update to this version. We’ll be following up with a second email in a few minutes with the plugin attached, in order to minimize the risk of this email hitting your spam folder due to the attachment.
For those that updated to 2.4.4 and your license expired between then and now, we’ve emailed all applicable users, as well as those who’s licences expire in the coming days with a copy of the recent update. Please check your inbox, if you haven’t received an email and your license was active whilst 2.4.4 was out please get in touch and we’ll provide you with a copy.
We’d like to personally apologize for any inconvenience caused, in the event that this affected you. Aside from this fix, we’re also working on additional layers of safety measures including:
  • Searching PayPal transactions BEFORE deleting anything, in the event a payment was made but there are IPN issues.
  • Adding a ‘trash’ feature so that deleted bookings are recoverable for at least 30 days, to avoid any accidents in the future.

The post Pro 2.4.4.2 – Important Update from 2.4.4 appeared first on Events Manager for WordPress.

]]>
2952
5.6.3 and Pro 2.4.4 Released http://wp-events-plugin.com/blog/2016/04/17/5-6-3-and-pro-2-4-4-released/ Sun, 17 Apr 2016 15:58:41 +0000 http://wp-events-plugin.com/?p=2949 This is a maintenance release fixing various issues along with incompatibilities with PHP 7 and the recent release WordPress 4.5 Events Manager 5.6.3 Changes fixed events disappearing from calendar with WP FullCalendar plugin fixed PHP warning for delete booking when a user can’t manage booking removed our EM_PHPMailer class and

The post 5.6.3 and Pro 2.4.4 Released appeared first on Events Manager for WordPress.

]]>
This is a maintenance release fixing various issues along with incompatibilities with PHP 7 and the recent release WordPress 4.5

Events Manager 5.6.3 Changes

  • fixed events disappearing from calendar with WP FullCalendar plugin
  • fixed PHP warning for delete booking when a user can’t manage booking
  • removed our EM_PHPMailer class and started using the one shipped with WordPress
  • added %passwordurl% placeholder for new user registration email template
  • added check for whether categories are enabled in many areas of code potentially avoiding a array_map PHP notice
  • fixed preview mode duplicating tickets
  • fixed widget formats stripping certain HTML elements
  • fixed erratic date picker range behaviour when adjusting a start date later than the end date
  • fixed original image getting deleted when modifying duplicated event image
  • fixed orderby not including event_date_created and event_date_modified since 5.6.2
  • fixed PHP warning when calling #_ATT to a non-existent attribute
  • changed event debug meta box to display when WP_DEBUG_DISPLAY is also true rather than just WP_DEBUG
  • fixed front-end submission false validation errors when submitting events with bookings enabled
  • changed headers to new h1 standard on WP Dashboard pages
  • fixed bookings admin viewer table not showing specific ticket bookings on front-end
  • fixed ML hooking into em_event_save_meta and messing up the internal hook pointer by triggering it again
  • fixed translated options PHP fatal error in rare occasions/setups
  • fixed deprecated get_currentuserinfo notice in WP 4.5
  • fixed PHP 7 division by zero warning
  • fixed PHP 7 “array to string” notice
  • fixed PHP 7 issues with EM_Ticket validation
  • fixed grouped events list not showing long events on each group provided limit=0 is also supplied
  • fixed apostrophes not passing email validation
  • fixed buddypress fatal error when booking with notifications disabled,
  • fixed buddypress activity stream items being created twice for new bookings
  • fixed booking admin notes not being added in the front-end
  • updated google maps api version and removed deprecated sensor parameter
  • fixed searches not working for search terms containing apostrophes
  • fixed blank settings pages due to 4.5 code changes to wp_get_referer()
  • added em_bookings_deleted action which will execute when one or more bookings are deleted
  • added em_bookings_delete filter for when a group of bookings are deleted with event(s)
  • fixed EM_Bookings->delete() not deleting bookings properly
  • deprecated use of EM_Event->delete_bookings() and EM_Event->delete_tickets() in favor of EM_Event->EM_Bookings->delete()

Events Manager Pro 2.4.4 Changes

  • fixed CSV custom delimiter issues for attendees which were also fixed in EM 5.6.2
  • changed use of some translated text using textdomain dbem to events-manager for update EM 5.6.2
  • fixed partial refunds always cancelling
  • changed WP Dashboard admin page titles to h1
  • fixed some PHP errors and plugin conflicts in update script (kudos Ross McKay)
  • fixed load_plugin_textdomain firing before some plugins loaded (WPML conflicts)
  • fixed MB bookings form giving permission errors when submitting form second time after failed validation
  • fixed transactions not displaying in individual bookings part of an MB booking
  • fixed booking registration meta showing empty user data instead of querying user meta
  • updated Chinese, French, Swedish and German
  • fixed PHP 7 ‘array to string conversion’ errors on custom booking form placeholders
  • fixed PHP warning for manual bookings with BuddyPress enabled
  • fixed double booking errors if admin making a manual booking but also booked that event
  • fixed double ‘required’ errors for user fields with different labels on the booking form to user fields editor
  • added warning to authorize.net settings if choosing live mode with an invalid SSL certificate
  • fixed rare MultiSite Multi Bookings bug in MS Global Mode when deleting an event booking from cart
  • fixed coupons not being freed from cancelled and rejected bookings
  • fixed WP 4.5 redirection errors due to changes in wp_get_referer (requires EM 5.6.3)
  • fixed coupons not being freed when bookings are deleted with an event (requires EM 5.6.3)
  • fixed deletion of event or modification of recurring event not deleting related booking translations
  • fixed some texdomain typos in the authorize.net gateway

The post 5.6.3 and Pro 2.4.4 Released appeared first on Events Manager for WordPress.

]]>
2949
5.6.2 Released http://wp-events-plugin.com/blog/2015/12/18/5-6-2-released/ Fri, 18 Dec 2015 15:34:26 +0000 http://wp-events-plugin.com/?p=2939 This latest release fixes various bugs including a few issues which cropped up in the weeks following the the latest WordPress 4.4 release. We have also done a large maintenance review of translations whilst migrating to the new way of translating Events Manager on translate.wordpress.org. As of now, our new

The post 5.6.2 Released appeared first on Events Manager for WordPress.

]]>
This latest release fixes various bugs including a few issues which cropped up in the weeks following the the latest WordPress 4.4 release.

We have also done a large maintenance review of translations whilst migrating to the new way of translating Events Manager on translate.wordpress.org. As of now, our new text domain for translating Events Manager strings will be events-manager (previously dbem). Additionally, alongside adding various new languages and updates, we have fixed various typos throughout the plugin and updated every single language file to reflect this.

We will be updating our translation instructions over the coming days and getting in touch with current/previous translators to help make the transition to this new way of adding Events Manager in your language. Stay tuned for more in a follow-up post!

Events Manager 5.6.2 Changes

  • changed translation gettext domain from dbem to events-manager inline with new translate.wordpress.org translation features
  • fixed EM_CSV_DELIMITER not being included in headers, added filter em_csv_delimiter to override EM_CSV_DELIMITER
  • added wpfc-more class to allow hiding of time on ‘more’ link for WP FullCalendar
  • fixed booking cut-off time not working if cut-off days is 0 or empty
  • fixed front-end event submission form permission issues for new recurring events when publish cap is enabled but not edit_others and delete_others
  • fixed Norwegian incorrectly translated placeholders
  • fixed custom decimal separator not used in tax rate display
  • minor js fix which fixes a grecaptcha related error notice
  • fixed recurrence_byday db value saving as null for weekly Sunday events (kudos to Shaun Santa Cruz)
  • removed _event_date_created and _event_date_modified from the postmeta table as these are inaccurate, use the records from the wp_em_meta table or directly via EM_Event->event_date_created or EM_Event->event_date_modified
  • changed settings/admin capability from list_users to manage_options
  • added EM_DISABLE_AUTO_BOOKINGSFORM which prevents booking form showing below post if format overriding disabled
  • fixed WP 4.4 error on front-end event submission form
  • fixed PHP notices in WP 4.4 when categories are disabled
  • fixed Multiple Booking Mode bug in Pro introduced by WP 4.4 allowing NULL db values
  • fixed like_escape debug warning on search form
  • fixed twenty fifteen/sixteen CSS conflict hiding confirmation messages
  • added bookings closed message
  • updated all languages included typo fixes and added Arabic, Australian and Canadian English

The post 5.6.2 Released appeared first on Events Manager for WordPress.

]]>
2939
5.6.1 and Pro 2.4.3 Released http://wp-events-plugin.com/blog/2015/09/16/5-6-1-and-pro-2-4-3-released/ Wed, 16 Sep 2015 18:01:51 +0000 http://wp-events-plugin.com/?p=2937 This latest update is a minor release which fixes various known bugs including a few introduced in v5.6 Events Manager 5.6.1 Changes fixed no arguments being passed onto em_get_post_meta_pre and em_get_post_pre fixed minor PHP warning when viewing settings in paged tab mode fixed em_event_save_pre and em_location_save_pre firing before the get_post

The post 5.6.1 and Pro 2.4.3 Released appeared first on Events Manager for WordPress.

]]>
This latest update is a minor release which fixes various known bugs including a few introduced in v5.6

Events Manager 5.6.1 Changes

  • fixed no arguments being passed onto em_get_post_meta_pre and em_get_post_pre
  • fixed minor PHP warning when viewing settings in paged tab mode
  • fixed em_event_save_pre and em_location_save_pre firing before the get_post and validate functions/filters via the save_post action in the WP dashboard
  • fixed EM loading jQuery UI css when already loaded by another theme (if they enqueue it with id jquery-ui)
  • fixed bug introduced in 5.6 where some error/confirmation notices aren’t showing up on page loads
  • fixed mistaken update of Hungarian language files with German
  • fixed EM_Location::has_events() providing false negatives
  • added has_events and no_locations conditional location placeholders
  • fixed actions column throwing off CSV column spacing since v5.6
  • fixed orderby request parameter being ignored in EM_Bookings_Table
  • fixed booking_date not being a valid orderby value for EM_Bookings
  • fixed recurring events booking cut-off time resetting to 12AM when no days value is given

Events Manager Pro 2.4.3

  • fixed custom email templates per event not saving properly
  • fixed per-event coupon associations not saving when editing in wp dashboard
  • fixed manual no-user bookings not saving user fields correctly
  • fixed manual no-user bookings overwriting user field information to guest bookings user account
  • fixed bug preventing all or last custom event email being removed
  • fixed admin emails per event storing an unnecessary record in em_meta table when there is an empty value
  • fixed ‘awaiting payment’ status for free bookings not reserving spaces,
  • removed redundant EM_Offline::em_bookings_get_pending_spaces() function and related filter
  • fixed certain multi-select values containing characters like & breaking field validation
  • fixed PHP warning for some custom email setups

The post 5.6.1 and Pro 2.4.3 Released appeared first on Events Manager for WordPress.

]]>
2937