removed vendor from gitignore to fix travis build errors

.gitignore

@@ -61,8 +61,6 @@ node_modules
 
 ### Composer ###
 composer.phar
-vendor/
-
 
 # Commit your application's lock file http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file
 # You may choose to ignore a library lock file http://getcomposer.org/doc/02-libraries.md#lock-file
@@ -72,4 +70,3 @@ vendor/
 .sass-cache
 
 release
-

vendor/autoload.php

@@ -0,0 +1,7 @@
+<?php
+
+// autoload.php @generated by Composer
+
+require_once __DIR__ . '/composer/autoload_real.php';
+
+return ComposerAutoloaderInit30055955403cd3da33362c5540e7ceb9::getLoader();

vendor/cmb2/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,30 @@
+### Expected Behavior:
+
+
+
+### Actual Behavior:
+
+
+
+### Steps to reproduce (I have confirmed I can reproduce this issue on the trunk branch):
+
+1.  
+2.  
+
+### CMB2 Field Registration Code:
+
+```php
+add_action( 'cmb2_admin_init', 'yourprefix_register_demo_metabox' );
+function yourprefix_register_demo_metabox() {
+
+	$cmb = new_cmb2_box( array(
+		// Box Config...
+	) );
+
+	$cmb->add_field( array(
+		// Field Config...
+	) );
+
+	// Additional fields...
+}
+```

vendor/cmb2/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+Fixes #{issue-number}.
+
+### Changes proposed in this pull request
+
+-  
+
+-  
+
+-  
+

vendor/cmb2/CONTRIBUTING.md

@@ -0,0 +1,51 @@
+# Contributing to CMB2
+
+Thank you for your interest in contributing back to CMB2. Please help us review your issues and/or merge your pull requests by following the below guidelines.
+
+#### NOTE: The issues section is for bug reports and feature requests only.
+_Support is not offered for this library, and the likelihood that the maintainers will respond is very low. If you need help, please use [stackoverflow](http://stackoverflow.com/search?q=cmb), or the [wordpress.org plugin forums](http://wordpress.org/support/plugin/cmb2)._
+
+Before reporting a bug
+---
+1. Search [issues](https://github.com/WebDevStudios/CMB2/issues) to see if the issue has been previously reported.
+2. Install the trunk version of CMB2 and test there.
+
+
+How to report a bug
+---
+1. Specify the version number for both WordPress and CMB2.
+3. Describe the problem in detail. Explain what happened, and what you expected would happen.
+4. Provide a small test-case and a link to a [gist](https://gist.github.com/) containing your entire metabox registration code.
+5. If helpful, include a screenshot. Annotate the screenshot for clarity.
+
+
+How to contribute to CMB2
+---
+All contributions welcome. If you would like to submit a pull request, please follow the steps below.
+
+1. Make sure you have a GitHub account.
+2. Fork the repository on GitHub.
+3. **Check out the trunk version of CMB2.** If you submit to the master branch, the PR will be closed with a link back to this document.
+4. **Verify your issue still exists in the trunk branch.**
+5. Make changes to your clone of the repository.
+	1. Please follow the [WordPress code standards](https://make.wordpress.org/core/handbook/coding-standards).
+	2. If possible, and if applicable, please also add/update unit tests for your changes.
+	3. Please add documentation to any new functions, methods, actions and filters.
+	4. When committing, reference your issue (if present) and include a note about the fix.
+6. [Submit a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+**Note:** You may gain more ground and avoid unecessary effort if you first open an issue with the proposed changes, but this step is not necessary.
+
+Translations
+---
+If you are looking to provide language translation files, Please do so via [WP-Translations](http://wp-translations.org/project/cmb2/).
+
+Additional Resources
+---
+
+* [CMB2 Documentation Wiki](https://github.com/WebDevStudios/CMB2/wiki)
+* [CMB2 Snippet Library](https://github.com/WebDevStudios/CMB2-Snippet-Library)
+* [CMB2 API Documentation](http://cmb2.io/api/)
+* [General GitHub Documentation](http://help.github.com/)
+* [GitHub Pull Request documentation](http://help.github.com/send-pull-requests/)
+* [PHPUnit Tests Guide](http://phpunit.de/manual/current/en/writing-tests-for-phpunit.html)

vendor/cmb2/bootstrap.php

@@ -0,0 +1,75 @@
+<?php
+/**
+ * Bootstraps the CMB2 process
+ *
+ * @category  WordPress_Plugin
+ * @package   CMB2
+ * @author    WebDevStudios
+ * @license   GPL-2.0+
+ * @link      http://webdevstudios.com
+ */
+
+/**
+ * Function to encapsulate the CMB2 bootstrap process.
+ * @since  2.2.0
+ * @return void
+ */
+function cmb2_bootstrap() {
+
+	if ( is_admin() ) {
+		/**
+		 * Fires on the admin side when CMB2 is included/loaded.
+		 *
+		 * In most cases, this should be used to add metaboxes. See example-functions.php
+		 */
+		do_action( 'cmb2_admin_init' );
+	}
+
+	/**
+	 * Fires when CMB2 is included/loaded
+	 *
+	 * Can be used to add metaboxes if needed on the front-end or WP-API (or the front and backend).
+	 */
+	do_action( 'cmb2_init' );
+
+	/**
+	 * For back-compat. Does the dirty-work of instantiating all the
+	 * CMB2 instances for the cmb2_meta_boxes filter
+	 * @since  2.0.2
+	 */
+	$cmb_config_arrays = apply_filters( 'cmb2_meta_boxes', array() );
+	foreach ( (array) $cmb_config_arrays as $cmb_config ) {
+		new CMB2( $cmb_config );
+	}
+
+	/**
+	 * Fires after all CMB2 instances are created
+	 */
+	do_action( 'cmb2_init_before_hookup' );
+
+	/**
+	 * Get all created metaboxes, and instantiate CMB2_hookup
+	 * on metaboxes which require it.
+	 * @since  2.0.2
+	 */
+	foreach ( CMB2_Boxes::get_all() as $cmb ) {
+
+		if ( $cmb->prop( 'hookup' ) ) {
+			$hookup = new CMB2_hookup( $cmb );
+			$hookup->universal_hooks();
+		}
+
+		if ( $cmb->prop( 'show_in_rest' ) && function_exists( 'rest_get_server' ) ) {
+			$rest = new CMB2_REST( $cmb );
+			$rest->universal_hooks();
+		}
+
+	}
+
+	/**
+	 * Fires after CMB2 initiation process has been completed
+	 */
+	do_action( 'cmb2_after_init' );
+}
+
+// End. That's it, folks! //