Huge error while uploading WordPress Theme purchased from ThemeForest

I keep getting this error message when I try to upload the wordpress theme I purchased. I am not finding this process as intuitive as it is proclaimed to be.

I am not really sure what I am supposed to do. I ended up spending so much money trying to follow all the installation instructions and nothing seems to work.

RECOMMENDED: Text domain problems in field_groups.php. You have not included a text domain!
Line 147: ‘title’ => __(‘Title’),
RECOMMENDED: Text domain problems in field_group.php. You have not included a text domain!
Line 727: ‘publish’ => __( ‘Publish’ ),
Line 728: ‘pending’ => __( ‘Pending Review’ ),
Line 729: ‘draft’ => __( ‘Draft’ ),
Line 730: ‘future’ => __( ‘Future’ ),
Line 731: ‘private’ => __( ‘Private’ ),
Line 732: ‘inherit’ => __( ‘Revision’ ),
Line 733: ‘trash’ => __( ‘Trash’ )
Line 746: $choices[‘super_admin’] = __(‘Super Admin’);
RECOMMENDED: Text domain problems in dummy.php. You have not included a text domain!
Line 19: $this->label = __(‘Dummy’);
WARNING: The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
WARNING: Found base64_encode in the file class.options_machine.php. base64_encode() is not allowed.
Line 1124: $output .= ‘<textarea id=’export_data’ rows=’8′>’.base64_encode(serialize($smof_data)) /* 100% safe – ignore theme check nag
WARNING: Found base64_encode in the file OAuth.php. base64_encode() is not allowed.
Line 118: return base64_encode(hash_hmac(‘sha1’, $base_string, $key, true));
Line 198: return base64_encode($signature);
WARNING: Found base64_decode in the file functions.interface.php. base64_decode() is not allowed.
Line 232: $smof_data = unserialize(base64_decode($_POST[‘data’])); //100% safe – ignore theme check nag
WARNING: Found base64_decode in the file OAuth.php. base64_decode() is not allowed.
Line 202: $decoded_sig = base64_decode($signature);
WARNING: Both DOS and UNIX style line endings were found in the file media-queries.css. This causes a problem with SVN repositories and must be corrected before the theme can be accepted. Please change the file to use only one style of line endings.
WARNING: file_get_contents was found in the file field_groups.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 379: $items = file_get_contents( $path . ‘readme.txt’ );
WARNING: file_get_contents was found in the file OAuth.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 272: file_get_contents(self::$POST_INPUT)
WARNING: curl_init was found in the file twitteroauth.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 203: $ci = curl_init();
WARNING: curl_init was found in the file mokka-instagram.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 232: $ch = curl_init();
WARNING: curl_exec was found in the file twitteroauth.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 229: $response = curl_exec($ci);
WARNING: curl_exec was found in the file mokka-instagram.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 236: $result = curl_exec($ch);
WARNING: .ds_store Hidden Files or Folders found.
REQUIRED: The theme uses the register_post_type() function, which is plugin-territory functionality.
REQUIRED: The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output
REQUIRED: upgrade.php. Themes should use add_theme_page() for adding admin pages.
Line 77: add_submenu_page(‘edit.php?post_type=acf’, __(‘Upgrade’,’acf’), __(‘Upgrade
REQUIRED: export.php. Themes should use add_theme_page() for adding admin pages.
Line 50: $page = add_submenu_page(‘edit.php?post_type=acf’, __(‘Export’,’acf’), __(‘Export’,
REQUIRED: class-tgm-plugin-activation.php. Themes should use add_theme_page() for adding admin pages.
Line 352: $this->page_hook = add_submenu_page( $args[‘parent_slug’], $args[‘page_title’], $args[‘menu_ti
REQUIRED: addons.php. Themes should use add_theme_page() for adding admin pages.
Line 42: $page = add_submenu_page(‘edit.php?post_type=acf’, __(‘Add-ons’,’acf’), __(‘Add-ons
REQUIRED: acf.php. Themes should use add_theme_page() for adding admin pages.
Line 586: add_menu_page(__(‘Custom Fields’,’acf’), __(‘Custom Fields’,’acf’), ‘manage
RECOMMENDED: No reference to add_theme_support( “title-tag” ) was found in the theme. It is recommended that the theme implement this functionality for WordPress 4.1 and above.
RECOMMENDED: No reference to add_theme_support( “custom-header”, $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: No reference to add_theme_support( “custom-background”, $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality.
RECOMMENDED: Author URI: is missing from your style.css header.
INFO: Non-printable characters were found in the field_groups.php file. You may want to check this file for errors.
Line 252: ‘ href='<?php echo admin_url(‘edit.php?post_type=acf&info=whats-new’); ?>’><?php _e(‘What???s New’,’acf’); ?>
INFO: Non-printable characters were found in the content-quote.php file. You may want to check this file for errors.
Line 13: ??? <?php the_field(‘quote_author’); ?>
INFO: user.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 126: require_once( ABSPATH . ‘/wp-admin/includes/user.php’ );
Line 148: require_once( ABSPATH . ‘/wp-admin/includes/user.php’ );
INFO: twitteroauth.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 11: require_once(‘OAuth.php’);
INFO: repeater.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 165: include( $this->settings[‘path’] . ‘views/field.php’ );
Line 184: include( $this->settings[‘path’] . ‘views/options.php’ );
INFO: index.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 87: require_once ( ADMIN_PATH . ‘functions/functions.load.php’ );
Line 88: require_once ( ADMIN_PATH . ‘classes/class.options_machine.php’ );
INFO: functions.load.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 10: require_once( ADMIN_PATH . ‘functions/functions.php’ );
Line 11: require_once( ADMIN_PATH . ‘functions/functions.filters.php’ );
Line 12: require_once( ADMIN_PATH . ‘functions/functions.interface.php’ );
Line 13: require_once( ADMIN_PATH . ‘functions/functions.options.php’ );
Line 14: require_once( ADMIN_PATH . ‘functions/functions.admin.php’ );
Line 15: require_once( ADMIN_PATH . ‘functions/functions.admin.php’ );
INFO: functions.interface.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 87: include_once( ADMIN_PATH . ‘front-end/options.php’ );
INFO: flexible-content.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 207: include( $this->settings[‘path’] . ‘views/field.php’ );
Line 226: include( $this->settings[‘path’] . ‘views/options.php’ );
INFO: field_group.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 415: include( $this->settings[‘path’] . ‘core/views/meta_box_fields.php’ );
Line 429: include( $this->settings[‘path’] . ‘core/views/meta_box_location.php’ );
Line 443: include( $this->settings[‘path’] . ‘core/views/meta_box_options.php’ );
INFO: field.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 90: include( ‘field-layout.php’ );
Line 118: include( ‘field-layout.php’ );
INFO: fave-init.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 23: require_once ( FAVE_PATH.’/includes/widgets/mokka-flickr-photos.php’ );
Line 24: require_once ( FAVE_PATH.’/includes/widgets/mokka-instagram.php’ );
Line 25: require_once ( FAVE_PATH.’/includes/widgets/mokka-most-viewed.php’ );
Line 26: require_once ( FAVE_PATH.’/includes/widgets/mokka-latest-posts.php’ );
Line 27: require_once ( FAVE_PATH.’/includes/widgets/mokka-latest-comments.php’ );
Line 28: require_once ( FAVE_PATH.’/includes/widgets/mokka-featured.php’ );
Line 29: require_once ( FAVE_PATH.’/includes/widgets/mokka-about-site.php’ );
Line 30: require_once ( FAVE_PATH.’/includes/widgets/mokka-twitter.php’ );
Line 31: require_once ( FAVE_PATH.’/includes/widgets/mokka-video.php’ );
Line 32: require_once ( FAVE_PATH.’/includes/widgets/mokka-image-banner.php’ );
Line 33: require_once ( FAVE_PATH.’/includes/widgets/mokka-code-banner.php’ );
Line 34: require_once ( FAVE_PATH.’/includes/widgets/mokka-most-commented.php’ );
Line 35: require_once ( FAVE_PATH.’/includes/widgets/mokka-most-liked.php’ );
Line 41: require_once ( FAVE_PATH.’/includes/sidebar.php’ );
Line 47: require_once ( FAVE_PATH.’/admin/index.php’ );
Line 53: require_once ( FAVE_PATH.’/includes/mokka-mega-menu.php’ );
Line 54: require_once ( FAVE_PATH.’/includes/secondary-walker.php’ );
Line 60: include_once( FAVE_PATH.’/includes/acf/acf.php’ );
Line 61: include_once( FAVE_PATH.’/includes/acf/acf-fields.php’ );
Line 64: include (FAVE_PATH. ‘/includes/twitteroauth/twitteroauth.php’);
Line 71: include_once( FAVE_PATH.’/includes/register-scripts.php’ );
Line 76: include_once( FAVE_PATH.’/includes/class-tgm-plugin-activation.php’ );
Line 77: include_once( FAVE_PATH.’/includes/register-plugins.php’ );
Line 82: include_once( FAVE_PATH.’/includes/styling-options.php’ );
Line 83: include_once( FAVE_PATH.’/includes/google-fonts.php’ );
Line 86: include_once( FAVE_PATH.’/includes/fave-views.php’ );
Line 87: include_once( FAVE_PATH.’/includes/functions/fave-functions.php’ );
INFO: export.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 93: include_once($path . ‘core/actions/export.php’);
Line 320: include_once(‘advanced-custom-fields/acf.php’);
INFO: dummy.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 276: include_once(‘fields/dummy.php’);
INFO: acf.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 355: include_once(‘core/api.php’);
Line 357: include_once(‘core/controllers/input.php’);
Line 358: include_once(‘core/controllers/location.php’);
Line 359: include_once(‘core/controllers/field_group.php’);
Line 365: include_once(‘core/controllers/post.php’);
Line 366: include_once(‘core/controllers/revisions.php’);
Line 367: include_once(‘core/controllers/everything_fields.php’);
Line 368: include_once(‘core/controllers/field_groups.php’);
Line 373: include_once(‘core/fields/_functions.php’);
Line 374: include_once(‘core/fields/_base.php’);
Line 376: include_once(‘core/fields/text.php’);
Line 377: include_once(‘core/fields/textarea.php’);
Line 378: include_once(‘core/fields/number.php’);
Line 379: include_once(‘core/fields/email.php’);
Line 380: include_once(‘core/fields/password.php’);
Line 382: include_once(‘core/fields/wysiwyg.php’);
Line 383: include_once(‘core/fields/image.php’);
Line 384: include_once(‘core/fields/file.php’);
Line 386: include_once(‘core/fields/select.php’);
Line 387: include_once(‘core/fields/checkbox.php’);
Line 388: include_once(‘core/fields/radio.php’);
Line 389: include_once(‘core/fields/true_false.php’);
Line 391: include_once(‘core/fields/page_link.php’);
Line 392: include_once(‘core/fields/post_object.php’);
Line 393: include_once(‘core/fields/relationship.php’);
Line 394: include_once(‘core/fields/taxonomy.php’);
Line 395: include_once(‘core/fields/user.php’);
Line 397: include_once(‘core/fields/google-map.php’);
Line 398: include_once(‘core/fields/date_picker/date_picker.php’);
Line 399: include_once(‘core/fields/color_picker.php’);
Line 401: include_once(‘core/fields/message.php’);
Line 402: include_once(‘core/fields/tab.php’);
Line 464: include_once(‘core/controllers/export.php’);
Line 465: include_once(‘core/controllers/addons.php’);
Line 466: include_once(‘core/controllers/third_party.php’);
Line 467: include_once(‘core/controllers/upgrade.php’);
INFO: acf-repeater.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 22: include_once(‘repeater.php’);
Line 41: include_once( dirname( __FILE__ ) . ‘/acf-repeater-update.php’ );
INFO: acf-gallery.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 18: include_once(‘gallery.php’);
Line 37: include_once( dirname( __FILE__ ) . ‘/acf-gallery-update.php’ );
INFO: acf-flexible-content.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 22: include_once(‘flexible-content.php’);
Line 41: include_once( dirname( __FILE__ ) . ‘/acf-flexible-content-update.php’ );
INFO: acf-fields.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 1327: include_once(‘add-ons/acf-gallery/gallery.php’);
Line 1328: include_once(‘add-ons/acf-repeater/repeater.php’);
Line 1329: include_once(‘add-ons/acf-flexible-content/flexible-content.php’);