Featured Images are not able to be set

by

You added your own answer in the comments section:

There is only one total php warning/error: 

wp-admin/admin-header.php:9 
- Cannot modify header information 
- headers already sent by 
(output started at 
    /home/content/p3pnexwpnas13_data03/47/3056147/html/wp-includ‌​es/functions.php:413‌​8) 
include('wp-admin/edit-form-advanced.php'), 
require_once('wp-admin/admin-header.php'), 
header…

The other half of the errors (it’s two different problems you are facing) can also be found in your comments 1)

I also get 6x of these that come up but not sure if has anything to do with the theme. 

Notice: wp_enqueue_style was called incorrectly. 
Scripts and styles should not be registered or enqueued until the 
wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. 
Please see Debugging in WordPress for more information. 
(This message was added in version 3.3.0.) 
in /home/content/p3pnexwpnas13_data03/47/3056147/html/wp-includ‌​es/functions.php on line 4138

The first problem is an error, which was raised in your AJAX call. The reason you do not get to see the error directly is, that —and this is what defines AJAX, the A is for asyncronous— the error was not in your current request, but in a request spawned by your current request, which ran in its own process in the background. Meaning: You will have to inspect the AJAX callback, the functionality that was called, to find the actual error.

Chrome has a nice set of debugging options available:

  1. You can replay that request without loading the whole page again, without repeating the process (e.g. opening a modal) and without bringing the request to a specific state. If you have a callback failing and are in local dev mode, simply change your AJAX endpoint handler, the callback script, hit Replay XHR and you will execute the callback with the changed code. Logical? Yes! Overseen? Yes, often.
  2. You can open any script that runs in the background, during an AJAX request, in a separate tab. That often makes error messages visible as they printed to the screen. Same here: Easy solution, but overseen by most devs.

The second problem is a race condition, a timing issue. A good indicator for a race condition is using a slow connection, something that you can for e.g. set and test in the Chrome developer tools. When things go slow, it’s easier to notice and watch when one script finishes its task earlier than another one that relies on the result. If the result is not available, it will fail. When WordPress tells you, that you enqueued a script too early, then for the reason that some script, shipped with core and noted as a dependency, is not yet ready. Another thing that is noted there is that you enqueued the script before the Dependency API is not yet ready to accept enqueuing a new script. This means that WP will not take and load and output your script, making WP fail at this point.

enter image description hereenter image description here

1) Please, do not hide important information in comments. Always add them as edits to your question.