Event Espresso 4 Core for WordPress: Build an Event Ticketing Website Today!
Branch: master
Clone or download
EE DevBox Server
EE DevBox Server Bumping version to 4.9.79.rc.004. Previous Commit message: "Update "m…
…ax_input_vars" exceeded message for clarity & make sure limit isn't stale (#963)

* Refresh warning message for clarity & include actionable instruction. Add additional check to get current limit. Fixes #908

* Slight text change.

* Reuse the first BR for additional calls.
"
Latest commit 09211e2 Feb 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github add new label to label-sync tool Feb 11, 2019
acceptance_tests Add fix for automated test helper May 3, 2018
admin_pages Improve open registration notice (#943) Feb 7, 2019
assets Fix errors with instanceof checks for custom objects. (#962) Feb 15, 2019
bin Remove translation configuration related to eejs-core script (#457) May 17, 2018
caffeinated Ensure QSG_identifier is unique when saving new question groups (fixes Feb 13, 2019
core
docs fixing errors in docs Feb 5, 2019
eslint Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
languages removing obsolete lang files Nov 14, 2013
modules Avoid multiple selects too. (#958) Feb 15, 2019
payment_methods improve paypal pro unauthenticatd message (#820) Jan 15, 2019
public Fix issue where espresso_event_status() always echos even if $echo = … Feb 4, 2019
shortcodes Fix phpcs violations with specific rule exclusions on linting rules. … May 6, 2018
tests Improve `Registry::pushData` (fixes #855) (#942) Feb 6, 2019
ui use default_avatar option instead of hardcoding in “Mystery Man” (#800) Nov 30, 2018
widgets Fix phpcs violations with specific rule exclusions on linting rules. … May 6, 2018
wp-assets Merge branch '01-master' into 03-beta Jan 10, 2015
.editorconfig Iteration 1 of the new WordPress editor and blocks system integration ( Nov 9, 2018
.eslintignore Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
.eslintrc.js Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
.gitattributes beefed up gitattributes in alpha version too Mar 8, 2013
.gitignore ignore font cache files Sep 20, 2018
.nvmrc set an .nvmrc and update docs with instructions about node and npm Apr 5, 2018
.travis.yml Fix npm version installed in travis environment and switch to wp-scri… Jan 11, 2019
README.md fix travis badge Jan 16, 2019
babel.config.js Iteration 1 of the new WordPress editor and blocks system integration ( Nov 9, 2018
circle.yml add big_rest_tests to the exclude group in the phpunit.xml [touch: 10… Jun 2, 2017
composer.json Add phpcs linting configuration (fixes #357) (#378) May 2, 2018
composer.lock Fix phpcs violations with specific rule exclusions on linting rules. … May 6, 2018
espresso.php Bumping version to 4.9.79.rc.004. Previous Commit message: "Update "m… Feb 15, 2019
index.php [touch:3381]{t:240}all this work revolved around getting paypal stand… Sep 17, 2013
info.json Bumping version to 4.9.78.p Feb 13, 2019
js-green-licenses.json Update license validation config (#472) May 22, 2018
license.txt Normalize Strings again Mar 8, 2013
package-lock.json Fix errors with instanceof checks for custom objects. (#962) Feb 15, 2019
package.json Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
phpcs.xml Add phpcs linting configuration (fixes #357) (#378) May 2, 2018
phpstorm-webpack.config.js Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
postcss.config.js fix code style for all existing js Apr 10, 2018
readme.txt Fix typos, remove duplicates, update lists Jan 8, 2019
translation-map.json fix exit modal height (#841) Dec 20, 2018
webpack.common.js Implements CRUD behaviour in the custom wp.data stores for EE models Jan 24, 2019
webpack.dev.js Switch webpack-assets-manifest plugin config to use the assets config… May 30, 2018
webpack.prod.js Dont' show archive controls panel when editing pages. (#778) Nov 13, 2018

README.md

Event Espresso Core

Latest Tag Travis PHP WordPress License Join Chat

Event Espresso 4 - Event Ticketing and Registration System

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.

Support License

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

Installing Event Espresso

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

View Event Espresso 4 Install Documentation →

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

Mobile Event Apps

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

View Mobile Event App Documentation →

Newsletter

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

Community Chat

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 →

Developers

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

Event Espresso Releases

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).

Testing

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.

Pull Requests

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.