Thank you for fixing the customizer compatibility

You’re welcome!

Hey. Actually every time I attempt to save an image (within customizer) with either ‘automatically add paragraph’ turned on and viewing in text mode, or ‘automatically add paragraph’ turned off and viewing in visual mode, it parses into this:

&_lt;p&_gt;&_lt;img src=”[path]” alt=”logo-footer” width=”46″ height=”47″ /&_gt;&_lt;/p&_gt;

this was all i put in originally:

<img src=”[path]” alt=”logo-footer” width=”46″ height=”47″ />

(underscore added so it shows the same)

Visual view:

Scenario A: A simple image added (image tag with no wrapper element of any kind) to a widget viewed through the customizer. Auto p turned on.
Result A: it works and no weird parsing happens.

Scenario B: Same as scenario A. Auto p turned off.
Result B: Doesn’t work, spinning infinitely, parses weird p tag and html.

Text view:

Scenario C: Same as scenario A. Auto p turned off.
Result C: Works fine, no p added, no unusual parsing.

Scenario B: Same as scenario A. Auto p turned on.
Result B: Doesn’t work, spinning infinitely, parses weird p tag and html.

Another glitch is even if i’m in text view and i add a wrapping div to the image tag, i get the spinning wheel of death and weird parsing.

I couldn’t edit the original post any more to clarify but this is replacing the last point:

Another glitch in the working scenario or either view, if i add a wrapping div around the image tag it I get the spinning wheel of death and weird parsing with a paragraph attempting to substituted for my div.

like this:

<div><img src=”[path]” alt=”logo-footer” width=”46″ height=”47″ /></div>

Please let me know when this is fixed. I can’t use this reliably in customizer until then.

Hi there,
thanks for your detailed report. Unfortunately I am not able to reproduce any of the issues you reportd in the different scenarios. Everything works fine for me with BSTW 2.2.4 and WP 4.2.2, so I believe there could be a conflict with another plugin or theme. Please follow our troubleshooting guide (see FAQ) to locate the source of the problem.
In particular check your browser javascript console when you get the endless spinning wheel.