Archive for the ‘Development’ Category

2016 WordPress Hosting Survey

TL; DR
We want you to take our 2016 Web Hosting Survey (below).

Siteground - web hosting survey featured image

Siteground’s Jenga game

When we asked the Event Espresso community if they love their hosting company in our 2015 web hosting survey, the responses we received were somewhat enlightening. As far as Hosting Support, Server Uptime, and Hosting Features were concerned Siteground clearly came out on top. While WP Engine put up a great fight, they came in a very strong second place. InMotion did pretty well overall, coming in third.

Over the years I’ve had the pleasure of meeting many members of their respective support and development teams in real life. We’ve played oversized Jenga games, shared meals and talked shop with many of these folks at many WordCamps over the years.

Not only do all three of these web hosting companies come highly recommended, but they’re all really nice folks. I’ve seen first hand that they truly love their customers and the WordPress Community.

Are You Happy With Your Web Host?

Take the 2016 Web Hosting Survey!

Now the time has come to ask once again, who has the best web hosting in 2016?
(survey ends May 9, 2016)

This survey has expired.


Disclosure: This post contains affiliate links, which means we may receive monetary benefits if you make a purchase after clicking one of the links.

Save

Tags:
Posted in WordCamp, Development, Developers, Hosting | No Comments »

Introducing the Event Espresso Public Roadmap

Simple-kanban-board-

In our journey to empower business and organization leaders with the event registration, ticketing, and management tools that maximize the success of their events, we’ve learned that customer feedback and open communication are an important asset to the success of the Event Espresso plugin for WordPress.

However, up until recently, we haven’t had a very efficient way of tracking each request, allowing the community a place to vote on features, or tracking progress of the Event Espresso project. We felt we needed a public roadmap to help keep the community in the loop and to keep feature requests from getting lost.

Without a roadmap it’s sometimes easy to get lost. #EventEspresso #EventTech #RoadMap Click To Tweet

Using Trello as Our Public Roadmap

trello1Trello is an easy to use, real time, visual project management tool based on the Kanban system, which was developed in Toyota as a system to keep production levels high and maintain flexibility. It is best represented as a whiteboard filled with post-it notes. Each post-it represents different tasks involved in the project.

We felt a public Trello Board was a great place for us to engage with the community, get feedback, share our development, and keep you up-to-date on upcoming features & releases.

So last year we quietly launched our Event Espresso Public Roadmap on Trello to give our community a place to follow feature  planning and development. Since making the board public, we’ve already had quite a few votes and comments come through over the past few months, by way of mentioning the public roadmap in the support forums.

What to Expect

managing_expectationsWe hope this gives the Event Espresso community a bird’s eye view of features that are in the backlog and which are being completed in preparation for a major release. Going forward we plan to follow the roadmap as best we can and will continue to post requested features to the public roadmap for the community to vote on.

However, sponsored development is a service we offer to the community. If a community member sponsors a feature, then we agree to prioritize that feature ahead of some other things. A perfect example of this is when Event Espresso users want a new payment gateway, they can fund the initial development and we put that feature higher on the priority list and try to work on it asap.

Some very popular items, like recurring events, require development of underlying systems and features.

For example, core features such as Attendee Reassignment or wait lists, will need to be in place before we start work on the Recurring Events add-on (you wouldn’t want to have dozens of recurring events without an easy way to move attendees from one event to another would you?). Another example would be the Automated Email Reminders add-on, which will require the Messages Activity core feature (notice that’s a feature in and of itself).

Requesting a New Feature

If you have a new feature you want to see listed in the public roadmap, please create a new thread in our support forums and describe the feature as best you can. That way our support team can discuss the feature with you, and if appropriate, get it added to the roadmap.

Voting & Commenting

Event Espresso Public Roadmap VoteOnce your feature request is added to the roadmap, yourself and other community members will be able to vote and leave comments on the feature. Our support team will also forward any new requests for the feature to the roadmap.

We feel voting on features is especially useful to us, because it means we can list a bunch of features that we want to get done on the board, and then let the public vote up the features that they want the most. This allows us to take the community’s input for what they deem most important into our process for setting priorities.

Please feel free to vote on as many feature as you like.

Basic Overview of Trello

How it Works
Trello uses a system of boards, lists and cards. This creates a system that allows for individuals or teams to track a project and collaborate or contribute where they can be most useful or where it is most needed.

start-here-1

Board
A board is typically a project or product that is under development or consistently being worked on.

List
A list is a way to divide a board into different categories. Typically a list represents a stage of progress (to do, in progress, finished).

Card
A card is the most basic and flexible part of the system. It represents a specific element of a project (A new feature, a software bug, research for a post). We can move cards between lists as they progress through the project.

Subscribe to Updates
There are three ways to subscribe for updates in Trello. You can subscribe to the entire Trello Board, individual lists, and/or individual cards.

  • Subscribing to the Trello Board – Click the “Show Menu” button in the top right corner (screenshot) of the Trello Board, then click the “…More” link, then click “Subscribe” (screenshot).
  • Subscribe to a List – In the top right corner of each list is a tiny down arrow. Click the arrow, then click the “Subscribe” link (screenshot).
  • Subscribe to a Card – Click to open an individual Trello card, then click the “Subscribe” button under the “Actions” heading (screenshot).

Current Status of EE4 Development

We’ve been focused on making core improvements over the last several months and are currently wrapping up development on EE 4.9, which includes a major refactor of the Event Espresso Messages System.

The messages system refactor introduces a few new features, such as a messages queue, batch message processing, a recording system for sent messages, and the ability to resend failed messages. After that we will start work on the Attendee Reassignment feature and the Automated Email Reminders add-on.

Get Updates When New Features Release

Be the first to know when we ship new features … signup for our newsletter here: https://eventespresso.com/newsletter/

Wrapping Up

We realize many of you use Event Espresso as the backbone of your business and we hope this roadmap will help give you an idea of where the project is going. Please let us know in the comment section below if you have any questions.

ee4-public-roadmap-banner-900-1

Tags: , ,
Posted in Home Page, News, Development, Open Source, EE4 | 3 Comments »

Development Started on Event Espresso 4 Mobile Ticketing Apps

We are pleased to announce that development has started on the Event Espresso 4 mobile ticketing apps for Android and Apple mobile devices.

mobile ticketing apps

Mobile App Mockups

About the Event Espresso 4 Mobile Apps

Here’s what you can expect from the new mobile apps:

  • Feature parity with Event Espresso 3 mobile apps
    For the initial release, we are only working on feature parity with the Event Espresso 3 version of the mobile apps. Such as viewing events, registrations, and checking-in/out attendees from the mobile apps.
  • The apps will be free
    We care about your ticketing needs and want to make your lives better. You’ll be able to do check-in/out attendees, and those who use the Ticketing add-on will be able to scan tickets too.

Timeline?
The plan right now is to get the apps built, tested and release ASAP. If everything goes as planned, we can expect the development to take around 10 to 12 weeks.

What functions will the apps perform?
Event Espresso users will be able to check-in/out attendees and scan tickets using mobile devices, such as iPhones, iPads, and Android phones and tablets.

What about ____ feature?
We have a few ideas for features such as point-of-sale capabilities, etc, but these will have to come at a later date.

The team we’ve brought on to build the mobile apps has a lot of experience with building event related apps and we’re looking forward to working with them to add more great features in the future.

Tell us what you need/want?
Have some ideas you want to see the in Event Espresso mobiles apps? Let us know in the comments below.

Tags: , ,
Posted in Development, API, EE4 | 29 Comments »

REST API Now In EE4 Core

Events REST API

Events REST API

It’s official, now that the WordPress REST API (WP-API) has been rolled into WordPress core, we’ve added our own REST API  into the Event Espresso 4 (EE4) core plugin.

Since we already have the READ endpoints available in a plugin version of the EE4 REST API, on January 4th, 2016 we released an update (version 4.8.29) with the READ REST API endpoints in EE4 core.

However, we still have more work to do to get the WRITE endpoints done. Once the WRITE endpoints are completed, developer’s will have the ability to directly interface with your event website using the REST API to make updates directly to the database, such as checking-in attendees, creating/updating events, tickets, and attendees.

What Is An API?

In layman’s terms, an API or Application Programming Interface is an agreed set of standardized ways that a particular piece of software can be used; the rules defined for its interaction with the wider world, which govern how other pieces of software can talk to a program and how it will respond.

A few good examples of APIs in action would be:

  1. Anytime an app uses Google Maps to display its location information.
  2. A mobile or desktop twitter client.
  3. A game/service that integrates Facebook features such as login, messaging, etc.

In these instances, and all others like them, the APIs “expose” certain internal functions of the primary applications (Google Maps, Twitter, etc) so that outside developers can use them in their own applications or websites. In these examples, app developers have been given the ability to tap into the powerful features (and/or content) of major web services so that they can build on top of them and/or integrate key content and features into their own products, in clearly defined ways. This allows open collaboration to walk hand in hand with security.

What Is A REST API?

REST or REpresentational State Transfer is an architectural style of building APIs; not a code language or description of its function. A REST API is designed to provide a lightweight form of communication (less bandwidth) between a producer (ex: Twitter) and a consumer (ex: Twitter client), making it a reliable solution for high volume web services like Facebook, Google Apps, Twitter, WordPress, and now Event Espresso.

In this case, you are the producer of content (event information and event data), and the applications you build can consume or use that data through the Event Espresso 4 REST API.

This Will Affect Everyone Who Works With Event Espresso

The EE4 REST API is a simple but powerful way to interact with Event Espresso. Even though the EE4 REST API is not readily visible to users, over time user’s will experience the benefits of more interactive Event Espresso websites. Once we roll out the WRITE endpoints Mobile, desktop and web applications can get data from Event Espresso and do anything you can do via the admin panel. It’s like the admin panel, minus the user interface (UI).

The availability of the EE4 REST API as a core feature also means less time spent by developers creating something similar, and more time spent creating features and custom applications.

How Will The EE4 REST API Be Used?

The Event Espresso 4 (EE4) REST API in Core is intended to allow client-side applications, and apps on different servers, to be able to interact with the WordPress Plugin Event Espresso. It is included in Event Espresso since version 4.8.29, and is built on the WP REST API included in WordPress since version 4.4.

The EE4 REST API can, and will be used in a multitude of different ways, such as:

  • Custom mobile apps
  • Custom admin interfaces
  • Integrating your events with other application platforms
  • Provide interoperability with many different programming languages
  • and much more!

By providing an agreed, standardized programmatic interface between Event Espresso and the outside world, Event Espresso opens itself up to every other application and development environment on earth.

Information for Developers

Now that the REST API is in Event Espresso 4 Core, you can start developing great integration’s for your customers. All you need to get started is review the documentation and start building something GREAT!

Also you should stay tuned to our developer-specific blog at developer.eventespresso.com so you’ll know about any important changes regarding backwards compatibility or other developments.

And if you do build something great with the EE4 REST API, consider listing it on our 3rd party addons page.

Reporting Issues

If you have an REST API feature request, or bug to report, please let us know on our github repo.

Building a WordPress Plugin? Use the EE4 Database Models Instead

If you are building a WordPress plugin that will use Event Espresso 4 data server-side (in the PHP code), generally you do not need to use the API, and can instead use Event Espresso 4’s database models, config, and other modules directly. Check out developer.eventespresso.com for tutorials on how to use many of these systems.

We hope you enjoy using the Event Espresso 4 modern REST API, let us know what you think.

Tags: ,
Posted in News, Development, New Versions, API, EE4 | 1 Comment »

Developers Corner: Datetime System improvements coming with (tentatively) EE 4.8

Hey folks, there are some significant improvements coming to the EE4 date and time system with Event Espresso 4.

Note, these improvements will impact any custom code and/or third party add-ons that utilize the Event Espresso Datetime system.  So developers will want to take note of them and prepare your code for these changes as soon as possible.

Summary of Changes

As we improve systems in Event Espresso 4, our goal is to make them simple, clear, and as flexible as possible; these datetime improvements do just that. Here’s a summary of these improvements, but please see the Important Changes to EE_Datetime System coming to EE article on the Developer Portal for complete details:

1. Dates continue to be saved in the database in mysql format (Y-m-d H:i:s) and UTC+0.  Nothing changes there.

2. Dates live within the models and model objects as PHP DateTime objects.

3. Any unixtimestamps coming into the EE Date Time system are considered to be a true unixtimestamp (time()) and not a timestamp with the calculated offset that current_time('timestamp') provides.

4. Formats are now required for when instantiating EE_Base_Class objects with date time strings that are not a unixtimestamp.

5. New helpers are available for setting up strings for date related queries.

6. New EE_Base_Class helper for displaying localized date.

7. Extensive unit test coverage

When will these improvements be released?

Right now all the changes are found in the FET-3456-promotions-spco branch of Event Espresso 4.  This branch is currently available on our Pre-release Channel (prc) (sign up via your account page) for those who wish to try it out.  We strongly encourage developers to checkout the branch via github and make sure any of your custom code and/or custom add-ons work with the new improvements.

For existing Event Espresso 4 users, we have already updated all our core add-ons that are impacted by these improvements so they work both with the current datetime system and the new datetime system.  So you should see no impact when we release this on the stable channel.

Have any questions or feedback? You can leave a comment below, post in the forums, or even create an issue in Github.

Posted in News, Development, EE4, Developers | No Comments »

Announcing the Promotions add-on beta for Event Espresso 4

Attention discount loving event promoters! Behold the Promotions add-on beta! Finally, the Promotions add-on is ready for you to test its new, more flexible, publicity boosting, discount-ticket-price-obsessed event promoting features!

promotion-at-checkout

The Promotions add-on is compatible with Event Espresso 4.8 (also in beta) and available to download from the pre-release channel.

promotions-input

The new promotions add-on for Event Espresso 4 includes discounting with or without discount codes, cart discounts, and a new UI.

New Automatic (no-code discount) and discount limits features

The Promotions add-on can be used to set up promo-code based discounts and non-promo-code or automatic discounts to help encourage more event ticket buying.

promotions-limits

It allows you to set quantity limits on usage, as well as set a range of dates when promotions are applied to the price of an event ticket transaction.

That’s right, the cart total is discounted

When you set up a fixed discount type promotion, the amount will be taken off the price of the entire cart. This is a departure from how EE3 discounted a set amount for each ticket in the cart.

promotion-applied

Side note: You can still make it so the discount is increased with each ticket purchased by using the percent discount type promotion.

New UI for inputting and managing promotions

All of the promotions management happens within the promotions management screen, which keeps you out of the event editor. This helps speed up the input and management of promotions. Now you’ll have more time to spend on your other event managery tasks!

You’re welcome.

We look forward to your feedback from testing the Promotions add-on beta. Please feel free to start a new topic in the Pre-release channel forum if you have any questions, comments, or suggestions.

Tags: , , ,
Posted in Addons, News, Development, Beta | 11 Comments »

Event Espresso 4 REST API Development Started on Github

We are happy to announce that development of the Event Espresso 4 REST API has begun. You are invited to get involved with the API development by: sharing feedback on the direction of the API, contributing code, testing what is already completed, and encouraging others to get involved.

APIs are for Sharing, Please Share

Hey #app #developers a brand new #API is available for @EventEspresso http://api.eventespresso.com #WordPress #events #plugin #eventtech #mobile.

Please click to share this.

WordPress and Event Espresso Developers will be most interested in the EE4 REST API, because it will allow for faster development of a wide array of features, including custom reporting tools, mobile application development, and theme development. The EE4 REST API will provide an easy to use API, available via HTTP, to grab your site’s event and registration data in simple JSON format. Retrieving or updating data is as simple as sending a HTTP request.

Purpose of the Event Espresso 4 REST API

RESTful-APIAs you may have guessed already, the Event Espresso 4 REST API is not a new way to relax or catch some Z’s in between coding sessions. The Event Espresso 4 REST API is actually an application programming interface (API), intended to allow client-side JavaScript, and apps on different servers, to be able to interact with the WordPress Plugin Event Espresso. It is built on WordPress, Event Espresso 4 and the WP API; however once the WP API is merged into WordPress core, it is anticipated that this Event Espresso REST API will likewise be merged into Event Espresso 4 core.

Other WordPress plugins that intend to use Event Espresso 4 data server-side (in the PHP code) generally do not need to use the API, and can instead use Event Espresso 4’s models, config, and other modules directly. Check out developer.eventespresso.com for tutorials on how to use many of these systems.

Example applications could include:

  • JavaScript and HTML snippets that could be pasted onto non-WordPress sites that could list events from Event Espresso
  • Mobile applications for signing attendees into events in Event Espresso
  • WordPress plugin that controls Event Espresso data entirely on the client-side

Roadmap

Generally, the work will be organized into 3 main milestones:

  • READ functionality (API clients will be able to read just about anything from EE4, including information from add-ons)
  • WRITE functionality (API clients will be able to create and update most EE4 info, but we’d like to prevent API clients from breaking the DB so that will be a bit of a challenge)
  • Single page checkout (SPCO) functionality (we will want to present similar functionality to SPCO, except over the API. This will require rather tight integration with SPCO in order to keep them almost identical)

Progress

Current progress (as of this writing):

  • READ functionality is approximately 85% completed. We are actively working on the compatibility with the permissions and capability controls that are built into Event Espresso core.
  • WRITE functionality: 0% completed
  • SPCO functionality: 0% completed

Generally, the central hub for the API should be the EE4 REST API Github repository and milestones; along with blogging about it from developer.eventespresso.com.

Information for Non-developers

I’m not a developer, how does this affect me?

Not a developer, that’s okay! The Event Espresso REST API will allow other applications (other websites, mobile apps, etc) to access your Event Espresso data through an application programming interface (API).

We recommend you share this with your development team, agency or app developers because they will be excited about this. You should ask them to consider building an integration for the Event Espresso 4 API so that you can use your data in their applications.

Hey #app #developers a brand new #API is available for @EventEspresso http://api.eventespresso.com #WordPress #events #plugin #eventtech #mobile.

Please click to share this.

Another benefit of the API is that if you want a certain edge case feature that is not available in our core products, you can hire a developer to build it for you, without having to understand the Event Espresso 4 code base.

Have ideas for the API, fill out the survey below or leave a comment.

Information for Developers

How do I get access to the files?

Anyone with an account on Github.com can download and install the EE4 REST API on their site.

How do I get involved?

For the most part, at the time of this writing, we are still in the planing and development stages. Developers that are interested in the Event Espresso 4 REST API can get involved in the development and planning process from within the EE4 REST API page on Github.com.

Participate in a short survey!

How will you, or your company use the EE4 REST API? Let us know by filling out the survey below.

Posted in Addons, News, WordPress, Development, Open Source | 2 Comments »

Developer’s Guide to Payment Methods for Event Espresso 4.6+

Welcome! Let’s take a brief look at the payment methods as of Event Espresso 4.6.

In the Beginning…

In the old days of Event Espresso (EE3), all of the “payment gateways” (as we called them, then) were included in the core Event Espresso file system, which made the overall file size rather large and unwieldy over time. Some gateway folders ended up weighing in at around 2 – 3 megabytes each!

One of the many reasons we rebuilt Event Espresso 4 (EE4) from the ground up, was to make the gateway system more modular. So, in the beginning, we decided to build a simple payment gateway interface, that included only four of our most popular online payment gateways from EE3.  This approach allowed us to ship a working product, or rather a Minimum Viable Product (MVP), while allowing our developers time to fine tune Event Espresso and rebuild the entire gateway system.

Get Noticed!
Developers submit your add-ons to our Third-party Add-ons Directory.

Fast Forward to Event Espresso 4.6

We’ve now finished the “Gateway Rewrite”, or GWRW as we called it, in Event Espresso 4.6 and things are looking pretty sweet for Event Espresso gateway developers. We are now taking the approach of renaming “payment gateways” to “payment methods” in Event Espresso 4.6.

Payment Methods are now modular, and can be developed as an Event Espresso add-on. This allows us to keep EE4 core code and files lightweight, while providing our developers, as well as any third-party developers more flexibility to add new features, without lots of bloat.

As of  Event Espresso 4.6, developers are now invited to start developing new gateways, by following our in-depth payment method documentation.

Getting Started!

Ok, so you’re ready to build your own payment method? Head over to the EE4 Payment Method Development page on our developer documentation website.

Don’t forget, in order to give you a head-start, our developer’s have created an Add-on Skeleton that has  two working payment methods in it: one onsite and the other offsite. Of course neither actually communicates with a Payment Gateway, that’s what you’re going to do by following our gateway documentation!

The skeleton add-on is located in the event-espresso-core/tests/mocks/addons/new-payment-method. Currently the “tests” folder isn’t included by default in order to reduce plugin size, so you’ll need to get it from our github repo.

How Does the New Payment Method System Work?

In Event Espresso 4.6+, payment methods are PHP classes and associated files that take care of accepting payments from customers. They  define a form for its settings, possibly a form for billing information which can be displayed during Single Page Checkout, and possibly a gateway class which takes care of communicating with a payment gateway (eg Paypal.com) to actually transfer funds from the customer to you. They fall into 3 general categories:

  • ONSITE (where the customer enters their billing info directly on your site, and your site transfers billing data to the payment gateway directly),
  • OFFSITE ( where the customer is redirected to the payment gateway, enters their billing info, and then returns to your site afterwards), and
  • OFFLINE (where payment is marked to occur offline without a separate payment gateway).

Payment methods are more narrow in scope than EE Modules, and are generally placed in an EE4 Add-on. If you are building your own Payment Method as an add-on, please feel free to use our sample “New Payment Method” Add-on. For details, see the section Using the New Payment Method Add-on Skeleton section of our documentation.

What’s Next?

So, you’ve created a new gateway, and now you want to release it to the Event Espresso 4 community? First you need to decide if you want to sell and support the gateway, release it for free with limited support, or just keep it to yourself. Here’s some helpful tips on where to go next:

  • Selling & Supporting Your Custom Gateway – The best option is to list the plugin for sale on your website, using a shopping cart system, such as Easy Digital Downloads or eJunkie. Once the plugin is available on your website, please let us know so we can list it for you.
  • Release for Free With Limited Support – There are a few possible options. The easiest is to just release the plugin on Github. If you want other Event Espresso and WordPress users to find it easier, you can post it on WordPress.org plugin repository. Once you’ve uploaded it to one, or both of these locations, please let us know so we can list it on our website for you.
  • Keep it to Yourself – This is by far the easiest option, but no one else benefits from your hardwork 🙁

Wrapping Up

We hope that our gateway documentation works as a helpful guide to incorporating your own payment methods in Event Espresso 4. If you have technical questions, please feel free to post in our support forums. Developers with access to Event Espresso on Github can post questions there.

Tags: ,
Posted in Home Page, Development, EE4, Developers, Payment Methods | 3 Comments »

Announcing the Capabilities System in Event Espresso 4

As of Event Espresso 4.6, there’s a new way to manage event admins/managers. Gone are the days of an unfamiliar roles and permissions system. In EE3 we had the “Roles & Permissions” and “Roles & Permissions Pro“, where you could only allow your “event managers” access to certain areas of the admin. You also had to install two different add-on’s, just so you could get really crazy and allow users even more access to stuff. It was a truly cumbersome system.

Capabilities Are Now Baked Right Into Event Espresso 4 Core!

Now that the new capability system is baked right into Event Espresso 4 core, most of the limitations of the old system are history.

This incredible new feature introduces a large number of WordPress roles and capabilities for restricting access to various actions and views in the users dashboard. A number of capabilities follow the capability mapping system WordPress provides, for not only restricting access to general views, but also restricting access based on whether a user “owns” the item being viewed, or not (i.e. Event Authors only being able to edit their own events, or a user being able to edit only their own custom message templates).

What Else Is New?

Most of you know WordPress has a powerful user management system via its roles and capabilities system. We’d like to get things off to a great start with EE4, and so one of the most powerful things we have added to EE 4.6 core is the intelligently-placed capabilities that we use for restricting access to various parts of EE4. Not only that, but we’ve added plenty more goodies:

  • No UI for user management. The system is entirely hidden to the average user.
  • Over 100+ granular capabilities added. A number of capabilities follow the capability mapping system WordPress provides for not only restricting access to general views but also restricting access based on whether a user “owns” the item being viewed or not (i.e. Event Authors only being able to edit their own events, or a user being able to edit only their own custom message templates).
  • Easy to use plugin API for extending functionality. In EE4 we’ve provided a handy API for developers to quickly integrate add-ons with different core components of Event Espresso.
  • Takes care of initializing new roles and adding capabilities to existing roles. When you hook in your new capabilities using this system you are automatically integrated with all the stuff the EE Capabilities system does.
  • Areas of EE4 admin can also be restricted to certain capabilities. This Google Spreadsheet gives you a high level overview and description of all roles and capabilities as of Event Espresso 4.6. We’ve listed all of the EE4 admin routes in the left column and the capabilities across the top. Along the bottom, each sheet represents a different area of Event Espresso.
  • Use any third-party roles and capabilities plugin to manage access to Event Espresso 4 features. More on that below…

How Are Capabilities Managed?

Capabilities can now be managed using any number of third party role and capability management systems, such as Members by Justin Tadlock, to grant users (by role) access to attendee data, events, registrations, and WordPress pages and post content.

The system is entirely hidden to the average user, as there is no UI for user management. For the average EE4 user updating to 4.6.0, there will be no change in behavior, because all the new capabilities have been added to the core WP administrator role by default.

Getting Started with the EE4 Capability System

To get started, you should try to familiarize yourself with the “EE Capability System” and install a third party plugin, such as Members by Justin Tadlock, to use its extensive role and capability management system to grant users (by role) access to attendee data, events, registrations, and WordPress pages and post content.

Extending the EE4 Capability System

In EE4 we’ve provided a handy API for developers to quickly integrate add-ons with different core components of Event Espresso. The EE Capabilities system takes care of initializing new roles and adding capabilities to existing roles.  It is also used for users to reset default roles easily if needed.  When you hook in your new capabilities using this system you are automatically integrated with all the stuff the EE Capabilities system does.

This document highlights the EE_Register_Capabilities plugin API.

Any Questions?

Please first familiarize yourself with the EE4 Capability System and the EE4 Capability System Plugin API. If you have additional technical questions, please feel free to post in our support forums. Developers with access to Event Espresso on Github can post questions there. Feedback is welcome below!

Tags: , , , ,
Posted in Home Page, WordPress, Development, WordPress Plugins, Features, EE4, Developers | No Comments »

Major Release Update: 4.6.0 Now Available

Event Espresso (EE) is the most advanced WordPress events calendar, registration and ticketing plugin—and it just got even better! EE 4.6 includes three significant changes, a bunch of new features, a few enhancements and fixes, and compatibility for several new add-ons that are coming soon. Developers please take note.

Update notifications are being monitored and you will receive your upgrade notice over the course of a few days.
Please backup your website before making any changes.

Significant Changes to Payment Processing, Checkout and HTML Forms

We expect that you will not notice most of these changes unless you start looking into the core code. We have worked hard to make sure the transition from these existing systems to the new systems as seamless as possible.

  • New Payment Processing System – We have improved the system that manages processing payments.  This new payment system will make it easier to add features around managing payment gateways, payment accounts, multiple payments, etc. You should not notice much of a difference right now from the 4.4 gateway system other than the user interface has been standardized. The real magic comes in the code which we will use to build new features that you have been asking for.
  • New Checkout System – The checkout system has been improved to add flexibility in the order of registration steps, and add more intelligence based on the types of tickets being purchased. You may notice the front-end user interface looks even better. Again, the real gains will come over time as we add new features for event organizers and developers to customize the online event registration and ticketing checkout experience for their audience.
  • New System for Displaying and Processing HTML Forms – The new Forms system is a new object oriented dynamic form system utilizing built in strategies for display, normalization, and validation; including over 25 input types.

New Features

We have added more than a dozen new features to our WordPress events calendar, registration and ticketing plugin. This makes this our best brew of Event Espresso ever.

  • New payments system (see above)
    • Open one payment method by default so that one payment method is defaulted or pre-selected for registrants
    • Add compatibility for additional gateway integrations (see below)
    • Developers: Mock payment method add-on (get it via GitHub: event-espresso-core/tests/mocks/addons/eea-new-addon)
  • User capabilities system that allows you to manage access to Event Espresso with your favorite user and role or capability plugin, e.g. Members, User Role Editor (not an official endorsement of which plugin to use), previously an add-on in EE3
  • More modular Single Page Checkout which allows you to re-arrange the order of the checkout steps
  • Free event registrations are now a one step checkout
  • Switch to the new NoCAPTCHA reCAPTCHA
  • Event page template selector to account for different page layouts (e.g. full-width, etc.)
  • Customizable receipt and invoice templates that can be edited from your dashboard to make them better for your organization or country requirements, no more FTPing necessary
  • Message pack template system, and easy way to create different looking message layouts and choose them for each type of message
  • Support for UTF-8 invoices and receipts
  • Developers: New API for registering new Custom Post types and taxonomies with Event Espresso
  • Registrations CSV report for all events so you can get all your data at once

Enhancements and Fixes

While most of the work done on 4.6 is tied to improving a few systems and adding new features, we do have a few small improvements.

  •  Events can be archived by tags, with a front-end tag archive listing page.
  • Upcoming Events Widget now uses the WordPress defined date and time settings.

Compatibility with New Add-ons

While we refactored some major systems, we also took the opportunity to build more add-ons. We are in the final testing phase for many of these add-ons, so look for them to be available soon now that 4.6 is available.

  • Printable tickets (now available)
  • Ticket scanning, via barcode/qr code scanners (now available)
  • WP User Integration (coming soon)
  • Stripe payment gateway integrations (now available)
  • SagePay payment gateway integration (coming soon)
  • iDeal/Mollie payment gateway integration (coming soon)
For a complete history of updates and changes to Event Espresso 4 and the EE4-compatible add-ons, see the change log for Event Espresso 4.

For Developers

Many of the changes in 4.6 deserve your attention. For example, if you have built a custom payment gateway for Event Espresso 4.4 (or less) then you will need to evaluate whether it will be compatible with the new processing system. We have many resources for developers that can help:

The last thing I want to say is that it has been just under a year that we first released Event Espresso 4. In that year, we’ve released six major versions (averaging a major release every two months, which is on-par or better than the industry average). Obviously, our development rate has greatly improved, but we are changing our processes to get you new features even faster! More on that another time. 🙂

Please backup your website before making any changes.

Thank you for using Event Espresso. Let us know what you think or if you have any questions.

Posted in Home Page, Registration, Ticketing, News, Development, New Versions | 44 Comments »

Do NOT follow this link or you will be banned from the site!