Event Organiser 2.9.0

2.9.0 was released on the 16th September 2014 and brought some long-asked-for features, as well as a lot of tidying up and fixing of iCal feed generation & parsing, and as always additional unit tests to help keep development stable as we go ahead.

Latitude/Longtitude editing

You can now manually enter the latitude / longtitude co-ordinates of a venue on it’s admin edit page. The co-ordinates appear below the address and update as you enter enter the address or drag the marker. It makes use of HTML5’s contenteditable attribute, and by clicking the co-ordinates you can change them. The changes you make will be reflected on the map as soon as the co-ordinates loose focus.


Additional hooks

Three hooks relating to taxonomy registration were added, of the form eventorganiser_register_taxonomy_{taxonomy} for the taxonomies event-venue, event-category, event-tag. This filter allows you to change the properties of these taxonomies.

For example, the following changes ‘venue’ to ‘location’

function my_change_venue_labels( $args ){

    $new_venue_labels = array(
        'name'                       => 'Event Locations',
        'singular_name'              => 'Location',
        'search_items'               => 'Search Locations',
        'all_items'                  => 'All Locations',
        'view_item'                  => 'View Location',
        'edit_item'                  => 'Edit Location',
        'update_item'                => 'Update Location',
        'add_new_item'               => 'Add New Location',
        'new_item_name'              => 'New Location Name',
        'not_found'                  => 'No locations found',
        'add_or_remove_items'        => 'Add or remove locations',
        'separate_items_with_commas' => 'Separate locations with commas',
        'venue_location'             => 'Location address',
        'view_all_items'             => 'View all locations',
        'singular_name_colon'        => 'Location:',
        'no_item'                    => 'No Location',
    $args['labels'] = $new_venue_labels;
    //return false' //return false to disable the taxonomy.
    return $args;
add_filter( 'eventorganiser_register_taxonomy_event-venue', 'my_change_venue_labels' );

You can also disable the taxonomy by returning false.

Additionally the ajax response to the fullCalendar is filtered, via eventorganiser_fullcalendar (see codex). This filters an array of events (which themselves are arrays, see also eventorganiser_fullcalendar_eventcodex)

Minified stylesheets

Unless SCRIPT_DEBUG is enabled in your wp-config.php, WordPress will use minified resources (including Event Organiser’s minified JavaScript files). This now extends to its stylesheets.

Timepicker UI improvement

This is only a small change, which makes it slightly more difficult (though not impossible!) to select a start datetime which occurs after an end datetime. As with the datepicker, (and when the event starts and ends on the same day), you won’t be able to select a start time which is after the end time.

Bug fixes

There were numerous bug fixes. Most notably issues relating to iCal feed’s generation and parsing of the DESCRIPTION property. Additional unit tests have been added to ensure any future changes do not ‘break’ anything. The URL property was also added.

The rich snippet on events pages (particular relating to venue details) has been corrected. A couple of zero-width spaces had crept in, which are impossible to see in a text editor or IDE, but were flagged up on validity check.

Owing to unexpected behaviour, there has been a recent move away from using PHP’s date_interval() (which is only available on php 5.3+ installs anyway). This update addresses a bug which occurred in that change relating to events spanning DST boundaries (see #224).

Behind the scenes…

Screenshots have now been moved to the assets directory. This simple means when you update/install the plug-in from WordPress.org you will not be downloading the screenshots which gives a minor saving on bandwidth for resources that you almost never see anyway. Screenshots will still be visible as before, they will just be served directly from WordPress.org.

There have been substantial improvements to the management of translations, which amount to time being saved for development, the references and comments in .po files being frequently updated to reflect the current code base, and the translations being more routinely updated with your contributions at https://wp-event-organiser.com/i18n/translate/event-organiser/ (thank you!). On the face of it, you won’t notice much difference, but these ‘under the hood’ changes are making a difference.