DWCC2014.1 - When Inserting an Image, all code is wiped and replaced with HTML framework containing an iFrame

Question

I recently upgraded to DW CC 2014.1 on my Mac - which caused me a number of issues. But the one I'm facing right now is very strange.
Whenever I try to insert an image - either via the shortcut, or through the top level dropdown dialogue - when the file browser comes up, all of my HTML code disappears, to be replaced with a starter template and an iframe. This happens about 90% of the time - but it sometimes works correctly, and I can't figure out why it does work that 10%.
Usually, I can just cancel the file browser and Undo to get my code back. But occasionally that doesn't work (and neither does Revert), and I have to close the document and re-open to my last save.
Here's what appears when my code vanishes:
Anybody know what's happening here? I don't use any specially created shortcuts. I've run into several issues with 2014.1 that have impacted my productivity, and it's getting increasingly frustrating.

Answer 1

I am experiencing the same issue.
Environment: Mac Pro 6,1/OS X 10.9.5/DreamWeaver CC 2014.1 6947 Build
Relevant software: DefaultFolder X 4.6.10 (16690)
Steps:
1) Position cursor on its own line in Code panel of Split View.
2) Press Cmd+Option+I [OR] select Insert > Image > Image
3) Navigate to image using file browser
4) Click OK
5) Repeat the above steps to insert a second image
Result with DefaultFolder X active:
1) The first insert completes as expected [OR] all HTML code between opening and closing body tags disappears, and a frame tag with a source attribute pointing to the file itself is inserted after the closing head tag
2) For subsequent inserts:
If the first insert completed as expected: If the cursor is indented from farthest-left,  all HTML code between opening and closing body tags disappears, and a frame tag with a source attribute pointing to the file selected in the first insert appears after the closing head tag. If the cursor is not indented, *most* subsequent attempts will reproduce the issue
If the first insert produced the issue: all subsequent inserts will reproduce the issue, and the frame source will be the file itself
Result with DefaultFolder X disabled:
1) The first insert completes as expected [OR] all HTML code between opening and closing body tags disappears, and a frame tag with a source attribute pointing to the file itself is inserted after the closing head tag
2) For subsequent inserts:
If the first insert completed as expected: If the cursor is indented from farthest-left,  all HTML code between opening and closing body tags disappears, and a frame tag with a source attribute pointing to the file itself, no matter what file is selected in the file browser dialog, appears after the closing head tag. If the cursor is not indented, *most* subsequent attempts will reproduce the issue
If the first insert produced the issue: all subsequent inserts will reproduce the issue, and the frame source will be the file itself