News – Events Manager for WordPress http://wp-events-plugin.com Event Registration, Bookings, Calendars, Locations Wed, 18 Jul 2018 00:29:36 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.6 17180428 Events Manager 5.9.5 and Pro 2.9.6 Released http://wp-events-plugin.com/blog/2018/07/18/events-manager-5-9-5-and-pro-2-9-6-released/ http://wp-events-plugin.com/blog/2018/07/18/events-manager-5-9-5-and-pro-2-9-6-released/#respond Wed, 18 Jul 2018 00:25:17 +0000 http://wp-events-plugin.com/?p=3295 This latest release mainly addresses the recent price changes from Google, which is something we’ve been working on over the past few weeks since their announcement and we have also issued a separate more detailed announcement about today’s update including links to new documentation arising from these changes. Below is

The post Events Manager 5.9.5 and Pro 2.9.6 Released appeared first on Events Manager for WordPress.

]]>
This latest release mainly addresses the recent price changes from Google, which is something we’ve been working on over the past few weeks since their announcement and we have also issued a separate more detailed announcement about today’s update including links to new documentation arising from these changes.

Below is a summary of all changes in the recent updates:

Events Manager 5.9.5 Changelog

  • added new Google Maps display options to help prevent cost increases
  • fixed booking status emails getting resent when attempting to change status to same status
  • fixed potential consent issues with editing/validating bookings made by other registered users
  • fixed broken #_LATT custom field attributes for locations
  • fixed #_ATT placeholders with dropdown options not selecting default option if not defined
  • added em_locate_template_default filter to allow for further template overriding
  • fixed certain unsanitized permalink output on admin settings page
  • fixed weekly and daily recurrence creation inconsistencies when traversing DST change dates

Events Manager Pro 2.9.6 Changelog

  • added support for Google Maps Static API display options and caching for relatively sized static map images

The post Events Manager 5.9.5 and Pro 2.9.6 Released appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2018/07/18/events-manager-5-9-5-and-pro-2-9-6-released/feed/ 0 3295
Google Maps API Pricing Changes (and how it probably affects you) http://wp-events-plugin.com/blog/2018/07/17/google-maps-api-pricing-increases/ http://wp-events-plugin.com/blog/2018/07/17/google-maps-api-pricing-increases/#respond Tue, 17 Jul 2018 21:59:48 +0000 http://wp-events-plugin.com/?p=3251 Events Manager 5.9.5 and Events Manager Pro 2.6.4 were released to address the new Maps API price changes by Google. This blog post get into the what and why: Let’s start by saying that we’re fans of Google. They’ve provided lots of valuable services to us all, most of them

The post Google Maps API Pricing Changes (and how it probably affects you) appeared first on Events Manager for WordPress.

]]>
Events Manager 5.9.5 and Events Manager Pro 2.6.4 were released to address the new Maps API price changes by Google. This blog post get into the what and why:

Let’s start by saying that we’re fans of Google. They’ve provided lots of valuable services to us all, most of them free to the masses, and have pushed and shaped the internet into a wonderful resource of information and productivity. That said…

As of July 16th, Google Maps has changed the pricing structure of its API by reducing its free limits and significantly increasing the usage price. For many users, this likely won’t affect you, for many others it means Google Maps will no longer be a free service in its current state.

The intention of this post isn’t to alarm you, but the reality is that these changes are alarming for a multitude of reasons (of which we won’t get into here). Our intention here is to put the price changes into perspective, and also inform you about how Events Manager will react to this.

The Price Changes

For many years, Google was quite generous with its free usage allowance but slowly, over the years, this has changed and yesterday marked the biggest one of all. The difference between using the Google Maps API service has jumped up from by %1400 up to %2800 depending on the service used. Yup, that’s not a mistake, we’re talking THOUSAND percents from one day to another!

The bigger impact of this originates from the fact that alongside this price hike, they’ve also significantly lowered their free allowance which translates roughly to a %750 decrease in value/usage allowance for loading dynamic maps, or a whopping %2600 decrease in free map loads! Previously, you were able to load Google Maps on your site 25,000 a day (750,000 a month), now were you to only load Maps on your site, you’d have a 28,000 load allowance per month.

We’re referencing Google’s old pricing and comparing it with the new pricing. It’s hard to put this into numbers, because aside from a previously reasonable API pricing structure and (admittedly) generous free usage limits, the pricing structure was fairly simple to understand, whereas now every API call has a different price.

To put this into perspective, we’ve made some conservative (i.e. low) daily usage estimations for a somewhat popular events site and compare the price difference, based on a 30-day month.

Map API Use Type API Calls / Day New Price (Monthly)
Location(s) Map Display (Dynamic) 1,000 $210.00
Search Autocomplete 300 $51.00
Geocoding (Adding Locations) 300 $2.00
Credit Allowance -$200.00
Total $63.00

That’s a new $63 monthly cost for a site where their event/location pages containing maps are loaded 1000 times a day (not visitors, page loads), 300 searches are attempted per day using the location auto-completion feature, and adding 10 locations per day. We consider this to be fairly conservative and likely a quota many users will meet. If your traffic doubled, your bill jumps to $325, if it goes up tenfold, that becomes $2145.

How to manage and reduce API usage costs with Events Manager

We have created some new documentation pages that describes our new map load types, what APIs we use and how to optimize API usage.

Sadly, our hands our tied with regards to Google. If you want to continue using Google Maps as-is, you may face some steep cost increases depending on how much traffic your site gets. We have little option but to roll with the punches and attempt to provide the best balance between functionality and price possible.

Fortunately, we have figured out some ways that’ll drastically reduce (or mitigate entirely) the cost of using the API based on this current pricing structure. We’ve done this mainly by providing alternatives to dynamic map loads, which are likely to be the most expensive and crucial feature to website owners.

With Events Manager 5.9.5 you can opt to use Embedded Maps , which is a slightly different way of loading maps, but is completely free. The downside is that you have little control over what gets displayed on the map and around your location. For many, this will be an attractive option though.

With Events Manager Pro 2.6.4, we have also included integration with Google Static Maps, which is significantly cheaper to load than Dynamic Maps, affording you much higher monthly usage limits, along with caching which will optimize load times and further help stretch your budget. Aside from this, to provide a good user experience to your visitors, we also provide linking and click actions on these static maps so that users could open the map on a (free) google.com maps page, or load a dynamic/embedded map when clicked on. The idea here is to reduce the loading of expensive maps to when specifically requested.

Thinking ahead…

These price changes were only announced just over 2 months ago, affording us little reaction time. Our primary priority was to react accordingly with the current Google integrations we had, in order to reduce usage costs to plugin users as much as possible. We were forced to shift our focus from other features we’re currently working on to address this, we’ll be shifting that focus back on some awesome features (although one actually includes some Google API integration :/).

However, whilst we will still certainly continue to integrate with Google services, this recent price change has prompted us to think about where we go from here…  The harsh reality is that Maps and location-based services will not be free in larger volumes, but there are alternatives, many alternatives which are certainly significantly cheaper at higher volumes.

We have been looking at multiple alternatives, talking to Mapping service providers and are still exploring our options. However, one thing is certain, we will over time work towards decoupling the Google Maps functionality in Events Manager so that other services can hook into Events Manager and take over to display maps instead. This won’t be immediate, but it is now something we’ll be keeping in mind with every key we press whilst dealing with anything location-related. We look forward to providing you with further mapping-related announcements in the near future!

The post Google Maps API Pricing Changes (and how it probably affects you) appeared first on Events Manager for WordPress.

]]>
http://wp-events-plugin.com/blog/2018/07/17/google-maps-api-pricing-increases/feed/ 0 3251
Events Manager 5.9.4 & Pro 2.6.3.1 http://wp-events-plugin.com/blog/2018/06/10/events-manager-5-9-4-pro-2-6-3-1/ Sun, 10 Jun 2018 18:01:32 +0000 http://wp-events-plugin.com/?p=3240 Today’s release is a maintenance release following up last month’s release, which contained various privacy-related features for the European GDPR laws that came into force. Both updates fix a few issues that arose from consent boxes and different contexts where events, locations and bookings are submitted/edited. We’ve also ensured that

The post Events Manager 5.9.4 & Pro 2.6.3.1 appeared first on Events Manager for WordPress.

]]>
Today’s release is a maintenance release following up last month’s release, which contained various privacy-related features for the European GDPR laws that came into force.

Both updates fix a few issues that arose from consent boxes and different contexts where events, locations and bookings are submitted/edited. We’ve also ensured that anonymously submitted events that have attached locations will now store that information on both objects, allowing them to act independently from each other for exporting/erasing personal data.

Events Manager 5.9.4 Changelog

  • added em_rewrite_rules_array filter for final permalink rule manipulation
  • fixed privacy consent blocking certain actions such as single booking button and admin-side submissions
  • fixed fatal errors when showing the consent checkbox in WordPress 5.9.5 and earlier
  • fixed the quick booking button not working in ajax search results
  • fixed privacy policy consent form label not being translatable for multilingual sites
  • fixed inconsistent date headers in certain situations with UTC manual offset dates
  • fixed incorrect link to .eot dashicon file for IE11
  • added anonymous submitter data to locations for new event submissions and integrated this with GDPR export/erase tools
  • fixed location slug blanks when directly published from front-end via submitting an event
  • added default ical and rss feed limits to avoid overloading as number of events grow
  • corrected docs to include ‘recurrences’ search attribute
  • added timezone pre-formatting to functions that produced incorrect output for timezone date placeholders
  • fixed default categories not being applied for events with no categories
  • fixed locations being selectable for events in other blogs within a multisite global mode when locations don’t all reside on main blog

Events Manager Pro 2.6.3.1

  • fixed data privacy consent checkboxes showing on both individual event and checkout pages for multiple bookings

The post Events Manager 5.9.4 & Pro 2.6.3.1 appeared first on Events Manager for WordPress.

]]>
3240
Upcoming GDPR Compliance Laws http://wp-events-plugin.com/blog/2018/05/03/upcoming-gdpr-compliance-laws/ Thu, 03 May 2018 12:01:08 +0000 http://wp-events-plugin.com/?p=3221 We’d like to make an announcement regarding the upcoming GDPR deadlines and how we’re preparing for it. Update May 22nd 2018:  We expect to release an update today tomorrow, and whilst we’re cutting it pretty close, as it’s now taking its final shape the work involved to get ‘compliant’ will

The post Upcoming GDPR Compliance Laws appeared first on Events Manager for WordPress.

]]>
We’d like to make an announcement regarding the upcoming GDPR deadlines and how we’re preparing for it.

Update May 22nd 2018: 

We expect to release an update today tomorrow, and whilst we’re cutting it pretty close, as it’s now taking its final shape the work involved to get ‘compliant’ will likely be minimal. We’ll be hooking into WP’s export/erasure tools and insert checkboxes to the booking/event forms automatically.

The only initial action on your part is just revising your privacy policy which we’ll already generated text for if you’ve not created one yet. If you already have a policy, we’ll also add a sample of text on our release blog post.

In short, Events Manager (and Pro) is currently not  GDPR compliant, but it will be, and in time for the deadline.

What is the GDPR?

The internet is abuzz with a new acronym – GDPR. This is a new EU Regulation that will come into force on May 25th 2018, which expands on the previous EU Data Protection laws and imposes further responsibilities upon any website owner that interacts with EU users in any way where personal data is collected.

Whilst this doesn’t affect everyone in the world, it will affect the vast majority of websites that are open to the international public. This is particularly true for Events Manager, since information is collected from users any time an event is submitted or a booking is made. Unless you close your site to the whole of Europe, it’s likely you’ll need to be prepared for compliance.

Is WordPress GDPR compliant?

Well, the answer is the same as ours… not yet. The WP GDPR compliance team is made of some brave volunteers who have been hard at work discussing, planning and implementing these features for many months now. Today, a beta is scheduled for the 4.9.6 release with the focus on GDPR with an expected release date near the GDPR deadline.

Additionally, it’s worth noting that WordPress will never be ‘Compliant’ out-the-box. No plugin will automatically make your site GDPR compliant, as the burden lies on the website owner to ensure they meet the GDPR requirements. However, it will provide you with additional tools to allow you to comply with the GDPR requirements.

So… how is Events Manager preparing for GDPR compliance?

Like WordPress, we need to provide you with tools and information that’ll allow you to be GDPR compliant.

We are well aware of the upcoming WP GDPR implementation guideline and have been for some time now, following their progress. However, we have held back from implementing anything just yet as we’re keen to integrate with the upcoming GDPR compliance tools currently being produced for WordPress in general, rather than creating our own separate tools. We feel that the more we integrate with the core GDPR tools, the less confusing it’ll be for everyone.

We’re looking forward to exploring the upcoming betas and RC’s as we integrate and implement our own compliance measures to ensure you, our users, can meet your compliance requires as smoothly and painlessly as possible.

How is everyone else preparing for GDPR compliance?

You may be thinking that we’re all leaving this pretty close to the deadline. Well, we’re not alone here, and neither are you!

Take a look at your inbox for proof… You’re probably receiving an unusually high number of emails over the past and upcoming weeks from the various online services  you’re signed up to regarding updated privacy policies(including the big guys like Google, Twitter, Facebook et. al). Some do and some don’t mention the GDPR, but generally speaking, everyone is dotting their i’s and crossing their t’s weeks before the deadline arrives.

Stay tuned…

Over the coming weeks, we’ll be reviewing our plugin features and doing everything possible to ensure that you can use Events Manager and adhere to the new laws. We’ll be following up once this is ready.

 

The post Upcoming GDPR Compliance Laws appeared first on Events Manager for WordPress.

]]>
3221
Pro 2.6.2 Release fixes authorize.net errors http://wp-events-plugin.com/blog/2018/05/02/pro-2-6-2-release-fixes-authorize-net-errors/ Wed, 02 May 2018 14:21:31 +0000 http://wp-events-plugin.com/?p=3215 We’ve pushed out an urgent update today for the Pro plugin, which specifically updates an SSL certificate within our plugin that is causing issues with booking events and paying with Authorize.net. This is a required update for anyone using Authorize.net for payments. However, for those with expired licenses who do

The post Pro 2.6.2 Release fixes authorize.net errors appeared first on Events Manager for WordPress.

]]>
We’ve pushed out an urgent update today for the Pro plugin, which specifically updates an SSL certificate within our plugin that is causing issues with booking events and paying with Authorize.net.

This is a required update for anyone using Authorize.net for payments. However, for those with expired licenses who do not wish to renew, for whatever reason, we do not consider this update as a ‘reason to renew’ (whilst we’d love it if you do!) and we’d like to share how to fix this yourself with some easy steps:

[edit: 2018-05-02 22:32PM CET – please update to 2.6.2.1 and view our follow-up post for updated instructions]

  1. Visit this page, and save it to your computer (which should save as file cert.pem)
  2. Upload the file to your site within the Events Manager Pro plugin folder, replacing the file /add-ons/gateways/anet_php_sdk/lib/ssl/cert.pem

These two steps will fix connection issues to the Authorize.net service.

We apologize for the inconvenience caused. Upon further investigation, this seems to be a change that Authorize.net implemented on May 1st 2018 yet failed to announce it (they usually announce breaking changes of this kind months ahead of time), and has caught a lot of their customers by surprise.

The post Pro 2.6.2 Release fixes authorize.net errors appeared first on Events Manager for WordPress.

]]>
3215
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