The Events Calendar WordPress plugin by Modern Tribe
Switch branches/tags
Clone or download
Latest commit 615ba75 Nov 13, 2018
Failed to load latest commit information.
common @ 76a3615 #115899 - update from glotpress Nov 12, 2018
lang #115899 - update view version Nov 12, 2018
src #115899 - update view version Nov 12, 2018
tests #115899 - update release dates and @SInCE tbd Nov 11, 2018
vendor Remove the Mapping since we are not Shipping its file Nov 9, 2017
.editorconfig Add jshint and scss-lint to the .editorconfig Nov 9, 2015
.env udpate the tests and config to force async to be sync in tests Apr 3, 2018
.gitattributes Prevent Generated files to show on Diffs on GitHub Mar 15, 2018
.gitignore merge master into bucket/full-rest-api branch Jul 27, 2017
.gitmodules Attempt at removing again Sep 12, 2017
.travis.yml add dump for aggregatorv1 starting fixture May 7, 2018
CODEOWNERS Add CODEOWNERS Dec 13, 2017 Adding Mar 11, 2016
codeception.dist.yml restore test setup files Jan 10, 2018
composer.json update wp-browser to 2.0.5 Apr 3, 2018
composer.lock first working version Apr 25, 2018
data_collection_disclosure.html Style it to look a bit more like, link docs Jun 11, 2018
gulpfile.js Set product-taskmaster as a npm dependency Mar 11, 2016
license.txt Update Copyright Validity Feb 8, 2017
package-lock.json Version update Oct 5, 2018
package-whitelist.json Fix filename Jun 15, 2018
package.json M18.16 - setup for sprint Oct 22, 2018 completed section adjustment Mar 20, 2018
readme.txt #115899 - update release dates and @SInCE tbd Nov 11, 2018
site_owner_data_collection_statement.html Style it to look a bit more like, link docs Jun 11, 2018 Revert "Revert "Merge pull request #2046 from moderntribe/fix/105116-… Aug 7, 2018
the-events-calendar.php M18.16 - setup for sprint Oct 22, 2018
yarn.lock Latest Translations Apr 17, 2018

The Events Calendar

Welcome to the official git repository for The Events Calendar, a WordPress plugin developed by the team at Modern Tribe.

Please feel free to fork this repository and submit pull requests!

We do have some guidelines that you should keep in mind while working with this repository:

  1. We have an internal release cycle and review pull requests once per cycle. Unfortunately we can't guarantee a regular schedule for our review process, but please know that while it may take 1-2 months (at the most) before we review your request, we WILL review it.

  2. Please submit a detailed description with your pull request. If we can't figure out what you're submitting, then we may close your request.

  3. We do not accept or handle support issues or bug reports here. You may notice that we have disabled the Issues tab on this GitHub project. Please submit bug reports at If you have purchased any of our premium add-ons, you may create an account and submit support requests at our Premium Support Forums.

  4. Please fork master and submit your pull requests against that branch. This is the branch with the latest code we are working on. Pull requests will be re-targeted against the branch for the next appropriate release before merged.

  5. When developing apply define('SCRIPT_DEBUG', true) in your wp-config.php. This will load unminified versions of our js assets and give you some debugging information in your dev console.

  6. Make yourself familiar with the dev folder, its readme and run the appropriate Grunt tasks before committing. Js minification, css minification, debug code removal, linting and more should be performed as you develop. Its all done with the grunt tasks defined in the dev folder.

  7. Lastly: We don't recommend using the develop branch on production sites! You’re welcome to give it a shot, but it is totally unrecommended - and we cannot provide any support if things go wrong. You’re on your own if you run develop code on your site.

That's all! please have fun and code responsibly :)

Further Information