Event Espresso is an event ticketing and registration platform for WordPress. Event Espresso makes it easy for you to register attendees for classes, workshops, events, trainings, conferences or concerts, all from your WordPress website. Event Espresso events are created from the WordPress admin area. You can create signup forms to collect information about your attendees, accept payments, and create reports.

Purchase a Premium Support License to get access to more features (including one-click upgrades, growing list of add-ons).

Event Espresso can be installed via the WordPress Dashboard or through FTP or SFTP.

View Event Espresso 4 Install Documentation →

Resources on Event Espresso 4 for a beginner to advanced users.

View Event Espresso 4 Documentation →

Notable changes for each released version of the project can be found in our changelog

The Event Espresso 4 check-in & ticket scanning event app is available for Android and Apple devices.

View Mobile Event App Documentation →

Be the first to know when we ship new features ... signup here.

Join a real-time community chat group for professionals that are leading the way in events from event management, event technology and event marketing to work-life balance.

Join the Discussion →

This is the full version of the plugin and provides everything that you need to sell tickets, collect payments, and manage events all from within your WordPress dashboard.

Buy a Premium Support License to get access to more features (including one-click upgrades, growing list of add-ons).

Note: for non stable versions. We currently use minor versioning numbers such as (4.1.rc.125) for rapid development occurring. On master, minor versions represent minor releases i.e. (4.1.1.p) that typically only include bug fixes and minor features. Releases including bigger features bump the second number (i.e. 4.1.1 -> 4.2.0 ). "rc" in the version number indicates that it is a non-stable release candidate version. "p" in the version number indicates a released version (usually only tags will have .p) In the list below we do not include minor version numbers.

This is the Core for Event Espresso 4. This README.md file is targeted for display with our GitHub repo. For detailed information via traditional readme, see the readme.txt file.

Extra: The code structure and phpdoc parsed documentation can be found at http://code.eventespresso.com

Developer Targeted Documentation can be found at http://developer.eventespresso.com/docs Developer News & Updates can be found at http://developer.eventespresso.com

At Event Espresso we follow a set pattern for releases:

1. Active development for new features happens on a FET/{ticket-number}/{description} branch. We continually merge master into the feature branch while its in development. Once its complete, then testing is done on it and its merged back to master ready for release.
2. Bug fixes etc. are done on a BUG/{ticket-number}/{description} branch. Same methodology is used as with Feature branches.
3. Stable releases are tagged both with a tests folder and without the tests folder.
4. Master is technically always production ready and release ready but may not be equal to what the current stable release is (that is what tags are for).

For all testers on GitHub, please take note of the following when reporting issues.

1. There is a difference between a feature and a bug, we consider a bug is something that reveals brokenness in intended functionality. A feature, is something beyond intended functionality. To help determine the difference, think about your issue like this, "I know A does C, however I wish it did D." If you find yourself saying that, its a feature. For Event Espresso, GitHub is not the place to suggest a new feature UNLESS you've already got a pull request to implement it (see pull requests section below). Info on sponsoring new features can be found here. If you aren't sure whether something is a feature or bug feel free to post the issue - however we give priority to bug issues here.

2. UI/UX issues may be considered a bug but not if it requires a major change in design. Feel free to report things you find confusing or needing improvement however reports accompanied by a pull request will likely get faster attention.

3. Report your issue as clearly as possible. By "clear" we mean:

   i. Specify the branch this occurred in.

   ii. Be specific about the steps you took to reproduce.

   iii. Feel free to use screenshots/screencasts to illustrate

   iv. Use URLs for the page the issue to place on where possible.

4. Don't "bump" bug reports if we don't respond right away. We see every report coming in, but we'll only reply if we need clarification or if we think its invalid. Otherwise, we're likely working on a fix and the issue will be updated when the fix is complete.

One of the reasons we published this repository on GitHub is because we wanted to open up EE development to 3rd party developers who might want to contribute to the codebase. GitHub makes this really easy to do so via pull requests. If you don't know what pull requests are, please read up on them via the GitHub help/documentation.

Here's how we deal with pull requests for our repo:

1. Any new FEATURES in a pull request should be based off of the master branch. If your feature pull request is based off any other branch it will not be considered.
2. Any BUGFIX pull requests should be based off of the branch the bug was found. Please verify if it is in master before submitting the pull request. If it is in reproducible on master, we'd prefer to have the pull request based off master.
3. We greatly appreciate any pull-requests submitted for consideration, but please understand we are very selective in what we decide to include in EE core. If the "feature" is something that expands too much on our design decisions for EE core then we may suggest you develop your pull request into an add-on for EE.

You may find our post on contributing to open source software helpful.