APPCRASH is back in Dreamweaver CC 2014

Less than a month ago I've asked the community on the issue related to APPCRASH in Dreamweaver CC (APPCRASH returns again). Due to community's assistance the problem was solved.
But upgrading DW to ver. CC 2014, I get the same error:
Problem Event Name: APPCRASH
Application Name: Dreamweaver.exe
Application Version: 15.0.0.6947
Application Timestamp: 5423e59e
Fault Module Name: StackHash_3e6f
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea91c
Exception Code: c0000374
Exception Offset: 000c3873
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1049
Additional Information 1: 3e6f
Additional Information 2: 3e6fc7e166444b80e7560d81933fce23
Additional Information 3: 8f90
Additional Information 4: 8f903d64a2252455f95692b4c3db2cb5
Can the problem be solved in any way?

Dear Kusha!
At the current moment I have no problems with Dreamweaver's start. Below I described the steps, which went to the crash. They are simple and straightforward.
Using Creative Cloud
I've installed both the Dreamweaver and Photoshop apps (trial).
Now I start Dreamweaver, selecting appropriate item from system menu:
and get the issue.
By the way, Photoshop installed simultaneously with Dreamweaver works perfectly:
But today I received true surprise. For the first time Dreamweaver CC 2014 started properly:
I don't understand what happened with the app, but it works.
Dear Kusha, excuse me for disturbance. I suppose, something worked wrong earlier, but now the error disappeared. How can I inform you, if the issue will be back in future?

Similar Messages

Dreamweaver CC 2014.1 Rewriting my ColdFusion Code

This has been an intermittent issue throughout the versions of Dreamweaver, but it's definitely back in Dreamweaver CC 2014.1. When opening ColdFusion templates (.cfm files) sometimes Dreamweaver will rewrite some of the code - often completely removing some of my closing tags (today it just removed a </cfoutput> tag) when I open the file in code view (I don't even use design view). It's gotten very dangerous for me to make ANY changes to my sites as sometimes simply opening the remote file and re-saving it breaks the site because of this rewriting! I have all the code rewriting preferences unchecked and can't find anywhere else to tell Dreamweaver to LEAVE MY CODE ALONE! Anyone else having issues with Dreamweaver being too helpful in trying to do your job for you? Some of these files are quite complex, long templates and pouring over them to track down what Dreamweaver did to my code is ridiculous. It was bad enough when adobe dropped support for ColdFusion extensions in the latest versions of Dreamweaver, but now I can't use it at all because of this and they don't even have an alternative coding product in the creative suite - you have to buy en entirely new product ColdFusion Builder to work with these pages. Next stop: Notepad!

I ended up going back to the previous version (Dreamweaver CC) as that version doesn't seem to have the same coding bug as CC 2014.1. Thank goodness Adobe rolled out the new version as a standalone rather than upgrading my older version! Time to start looking for a new coding IDE, I guess. Thanks @Nancy O. for the CF Eclipse and Sublime Text suggestions - I haven't figured out how to set up local/remote projects in eclipse yet the same way I had it working in Dreamweaver, but so far it's been just as effective a tool (and hasn't screwed up my code, either!).

Is it possible to create an extension containing a panel for Dreamweaver CC 2014?

Dear Adobe Community,
Currently we work in Dreamweaver CS6 with some custom extensions. Since we're now looking into upgrading to CC 2014, obviously, we need to make sure we can either re-use, port or create new extensions to maintain the functionality we have now.
In short: I haven't been able to create an extension for CC 2014 featuring a panel in any shape or form.
Creating a HTML5 based (CES 5) extension results in an error only visible in the log (attached).
Fiddling around in a flash based extension, upping the host application version gives no such error. But, like a HTML 5 based one, doesn't show up in Dreamweaver. (And I'm using the Sublime plugin, since Extension Builder 3 lacks DW support.)
Mind you, the "extensions" tab in the "Window" menu is lacking entirely.
Can anyone tell me if it is at all possible to create an extension for DW CC 2014?
Full log:
2014-09-01 16:11:24 : INFO PlugPlug version : 5.0.0.74
2014-09-01 16:11:24 : INFO LogLevel : 6
2014-09-01 16:11:24 : INFO Copy RGB Background Color Information for AppBar
2014-09-01 16:11:24 : INFO Fallback: Copy RGB Background Color Information for AppBar for sRGB usage
2014-09-01 16:11:24 : INFO Copy RGB Background Color Information for Panel
2014-09-01 16:11:24 : INFO Fallback: Copy RGB Background Color Information for Panel for sRGB usage
2014-09-01 16:11:24 : INFO Windows 32-bit PlugPlug logs
2014-09-01 16:11:24 : INFO ----------------------------
2014-09-01 16:11:24 : INFO PlugPlugSetup() API called:
2014-09-01 16:11:24 : INFO hostData->appName : DRWV
2014-09-01 16:11:24 : INFO hostData->appVersion : 14.0
2014-09-01 16:11:24 : INFO hostData->locale : en_US
2014-09-01 16:11:24 : INFO hostData->userInterfaceLocale : en_US
2014-09-01 16:11:24 : INFO hostData->supportedTypes : 31
2014-09-01 16:11:24 : INFO hostData->apeVersion : unknown
2014-09-01 16:11:24 : INFO hostData->overrideManifestLocation : (null)
2014-09-01 16:11:24 : INFO isApplicationOffline : false
2014-09-01 16:11:24 : INFO hostData->hostCEPHtmlEngineDirectory : (null)
2014-09-01 16:11:24 : INFO hostData->hostExtensionDirectory :C:\Users\BC-OLO\AppData\Roaming\Adobe\Dreamweaver CC 2014\en_US\Configuration\CEP\Extensions\
2014-09-01 16:11:24 : INFO hostData->hostStageManagerDirectory : C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\
2014-09-01 16:11:24 : INFO hostData->imsLibPath: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\P7\IMSLib.dll
2014-09-01 16:11:24 : INFO skinInfo->baseFontSize : 10
2014-09-01 16:11:24 : INFO skinInfo->baseFontFamily : MS Shell Dlg 2
2014-09-01 16:11:24 : INFO skinInfo->appBarBackgroundColor->antialiasLevel : PlugPlugAntialiasLevel_None
2014-09-01 16:11:24 : INFO skinInfo->appBarBackgroundColor->type : PlugPlugColorType_RGB
2014-09-01 16:11:24 : INFO ExtensionRegistry started
2014-09-01 16:11:24 : INFO Found ExtensionManifest in cache: C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\csxs\manifest.xml
2014-09-01 16:11:24 : INFO Found ExtensionManifest in cache: C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\csxs\manifest.xml
2014-09-01 16:11:24 : INFO Searching for valid extensions in 'C:\Users\BC-OLO\AppData\Roaming\Adobe\Dreamweaver CC 2014\en_US\Configuration\CEP\Extensions\'
2014-09-01 16:11:24 : INFO Searching for valid extensions in 'C:\Program Files (x86)\Common Files\Adobe\CEP\extensions'
2014-09-01 16:11:24 : DEBUG Searching for valid extensions in 'C:\Program Files (x86)\Common Files\Adobe\CEP\extensions'
2014-09-01 16:11:24 : INFO Searching for valid extensions in 'C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions'
2014-09-01 16:11:24 : DEBUG Searching for valid extensions in 'C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions'
2014-09-01 16:11:24 : DEBUG ExtensionManifest in cache is still the same (C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\csxs\manifest.xml).
2014-09-01 16:11:24 : DEBUG ExtensionManifest in cache is still the same (C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\csxs\manifest.xml).
2014-09-01 16:11:24 : INFO ExtensionManifest 'C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\csxs\manifest.xml' contains '1' valid extensions for this host
2014-09-01 16:11:24 : INFO Found extension with id 'com.example.ext'
2014-09-01 16:11:24 : DEBUG -> BasePath                    : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext
2014-09-01 16:11:24 : DEBUG -> ExtensionBundleId           : com.example.ext
2014-09-01 16:11:24 : DEBUG -> ExtensionBundleVersion      : 1.0.0
2014-09-01 16:11:24 : DEBUG -> ID                          : com.example.ext
2014-09-01 16:11:24 : DEBUG -> Version                     : 1.0.0
2014-09-01 16:11:24 : DEBUG -> MainPath                    : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\index.html
2014-09-01 16:11:24 : DEBUG -> ScriptPath                  : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\jsx\hostscript.jsx
2014-09-01 16:11:24 : DEBUG -> ScriptEngineId              : com.example.ext_Engine_Id
2014-09-01 16:11:24 : DEBUG -> AutoVisible                 : true
2014-09-01 16:11:24 : DEBUG -> StartOn -> Event            : 0
2014-09-01 16:11:24 : DEBUG -> Type                        : Panel
2014-09-01 16:11:24 : DEBUG -> Menu                        : Extension-Name
2014-09-01 16:11:24 : DEBUG -> MenuPlacement               : (null)
2014-09-01 16:11:24 : DEBUG -> Size
2014-09-01 16:11:24 : DEBUG    -> Height                   : 300
2014-09-01 16:11:24 : DEBUG    -> Width                    : 300
2014-09-01 16:11:24 : DEBUG -> MaxSize
2014-09-01 16:11:24 : DEBUG -> MinSize
2014-09-01 16:11:24 : DEBUG -> IconPath
2014-09-01 16:11:24 : DEBUG    -> IconPath -> Normal       : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconNormal.png
2014-09-01 16:11:24 : DEBUG    -> IconPath -> Disbaled     : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconDisabled.png
2014-09-01 16:11:24 : DEBUG    -> IconPath -> RollOver     : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconRollover.png
2014-09-01 16:11:24 : DEBUG    -> IconPath -> DarkNormal   : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconDarkNormal.png
2014-09-01 16:11:24 : DEBUG    -> IconPath -> DarkRollOver : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconDarkRollover.png
2014-09-01 16:11:24 : DEBUG -> DefaultExtensionData        : (null)
2014-09-01 16:11:24 : DEBUG -> SpecialExtensionData        : (null)
2014-09-01 16:11:24 : DEBUG -> RequiredRuntimeList            : 1
2014-09-01 16:11:24 : DEBUG    -> RequiredRuntime -> Name     : CSXS
2014-09-01 16:11:24 : DEBUG    -> RequiredRuntime -> Version : 5.0.0
2014-09-01 16:11:24 : INFO ExtensionManifest 'C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\csxs\manifest.xml' contains '1' valid extensions for this host
2014-09-01 16:11:24 : INFO Found extension with id 'com.OLO.Nemo.extension'
2014-09-01 16:11:24 : DEBUG -> BasePath                    : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo
2014-09-01 16:11:24 : DEBUG -> ExtensionBundleId           : com.OLO.Nemo
2014-09-01 16:11:24 : DEBUG -> ExtensionBundleVersion      : 0.5.0
2014-09-01 16:11:24 : DEBUG -> ID                          : com.OLO.Nemo.extension
2014-09-01 16:11:24 : DEBUG -> Version                     : 0.5.0
2014-09-01 16:11:24 : DEBUG -> MainPath                    : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\Nemo.swf
2014-09-01 16:11:24 : DEBUG -> ScriptPath                  : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\Nemo.jsx
2014-09-01 16:11:24 : DEBUG -> ScriptEngineId              : com.OLO.Nemo.extension_Engine_Id
2014-09-01 16:11:24 : DEBUG -> AutoVisible                 : true
2014-09-01 16:11:24 : DEBUG -> StartOn -> Event            : 0
2014-09-01 16:11:24 : DEBUG -> Type                        : Panel
2014-09-01 16:11:24 : DEBUG -> Menu                        : Nemo
2014-09-01 16:11:24 : DEBUG -> MenuPlacement               : (null)
2014-09-01 16:11:24 : DEBUG -> Size
2014-09-01 16:11:24 : DEBUG    -> Height                   : 400
2014-09-01 16:11:24 : DEBUG    -> Width                    : 232
2014-09-01 16:11:24 : DEBUG -> MaxSize
2014-09-01 16:11:24 : DEBUG -> MinSize
2014-09-01 16:11:24 : DEBUG -> IconPath
2014-09-01 16:11:24 : DEBUG    -> IconPath -> Normal       : (null)
2014-09-01 16:11:24 : DEBUG    -> IconPath -> Disbaled     : (null)
2014-09-01 16:11:24 : DEBUG    -> IconPath -> RollOver     : (null)
2014-09-01 16:11:24 : DEBUG    -> IconPath -> DarkNormal   : (null)
2014-09-01 16:11:24 : DEBUG    -> IconPath -> DarkRollOver : (null)
2014-09-01 16:11:24 : DEBUG -> DefaultExtensionData        : (null)
2014-09-01 16:11:24 : DEBUG -> SpecialExtensionData        : (null)
2014-09-01 16:11:24 : DEBUG -> RequiredRuntimeList            : 1
2014-09-01 16:11:24 : DEBUG    -> RequiredRuntime -> Name     : CSXS
2014-09-01 16:11:24 : DEBUG    -> RequiredRuntime -> Version : 5.0.0
2014-09-01 16:11:24 : INFO
********** Number of extensions found : 2 **********
2014-09-01 16:11:24 : INFO Register Extension called for Extension : com.OLO.Nemo.extension, ExtensionType : Trusted
2014-09-01 16:11:24 : INFO ----------------------------------------------------------------
2014-09-01 16:11:24 : DEBUG Extension inPlayerType : 1
2014-09-01 16:11:24 : DEBUG Extension mainUTF8Path : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.OLO.Nemo\Nemo.swf
2014-09-01 16:11:24 : DEBUG Extension iconPathNormal :
2014-09-01 16:11:24 : DEBUG Extension iconPathRollOver:
2014-09-01 16:11:24 : DEBUG Extension iconPathDisable:
2014-09-01 16:11:24 : DEBUG Extension windowType: Panel
2014-09-01 16:11:24 : DEBUG Extension showWindowOnCreate: true
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry topleftx: 0
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry toplefty: 0
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry width: 232
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry height: 400
2014-09-01 16:11:24 : INFO PlugPlugRegisterExtension() callback returned: PlugPlugErrorCode_success //<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<    FLASH BASED plugin
2014-09-01 16:11:24 : INFO Register Extension called for Extension : com.example.ext, ExtensionType : Trusted
2014-09-01 16:11:24 : INFO ----------------------------------------------------------------
2014-09-01 16:11:24 : DEBUG Extension inPlayerType : 2
2014-09-01 16:11:24 : DEBUG Extension mainUTF8Path : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\index.html
2014-09-01 16:11:24 : DEBUG Extension iconPathNormal : C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconNormal.png
2014-09-01 16:11:24 : DEBUG Extension iconPathRollOver: C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconRollover.png
2014-09-01 16:11:24 : DEBUG Extension iconPathDisable: C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\extensions\com.example.ext\icons\iconDisabled.png
2014-09-01 16:11:24 : DEBUG Extension windowType: Panel
2014-09-01 16:11:24 : DEBUG Extension showWindowOnCreate: true
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry topleftx: 0
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry toplefty: 0
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry width: 300
2014-09-01 16:11:24 : DEBUG Extension defaultGeometry height: 300
2014-09-01 16:11:24 : INFO PlugPlugRegisterExtension() callback returned: PlugPlugErrorCode_registerExtCallbackNotFound
2014-09-01 16:11:24 : WARN Service: com.example.ext not registered properly. //<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<   HTML5 BASED plugin
2014-09-01 16:11:24 : INFO PlugPlugSetMenu() callback called for main menu. Extension : , inMenuPosition:
(null), Menu: [{menuId: '1',nameUtf8: 'Nemo',extensionId: 'com.OLO.Nemo.extension'}]
2014-09-01 16:11:24 : INFO PlugPlugSetMenu() callback returned: PlugPlugErrorCode_success
2014-09-01 16:11:24 : INFO ExtensionLoadService activated
2014-09-01 16:11:24 : DEBUG PlugPlugAMTRequest() callback called. Request: <?xml version="1.0" encoding="UTF-8"?><PlugPlugEnvelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="./AmtlibPlugPlug.xsd"><request id="1" functionName="getProductLicenseInfo"><arguments/></request></PlugPlugEnvelope>
2014-09-01 16:11:24 : DEBUG PlugPlugAMTRequest() return value: PlugPlugErrorCode_success
2014-09-01 16:11:24 : DEBUG PlugPlugAMTRequest() XML returned chunk: <?xml version="1.0" encoding="utf-8" ?>
<PlugPlugEnvelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="./AmtlibPlugPlug.xsd">
    <response id="1" functionName="getProductLicenseInfo">
        <AdobeIDCreated>1</AdobeIDCreated>
        <LicenseType>Retail</LicenseType>
        <LicenseExpires>0</LicenseExpires>
        <LicenseRefreshes>0</LicenseRefreshes>
        <LicenseEncryptedSerial>909709176804077038364305</LicenseEncryptedSerial>
        <LicensedProductName>EPIC_APP_598</LicensedProductName>
        <SecondsSinceActivation>0</SecondsSinceActivation>
        <SecondsSinceSerialization>8147122</SecondsSinceSerialization>
        <SecondsBeforeExpiration>0</SecondsBeforeExpiration>
        <SecondsBeforeRefresh>0</SecondsBeforeRefresh>
        <AMTLibResponse>6</AMTLibResponse>
        <LicenseStatus>3</LicenseStatus>
        <SerializationGraceInseconds>3888000</SerializationGraceInseconds>
        <ProductCycle>8</ProductCycle>
        <PendingClaims>
            <PendingClaim>
                <AdobeID>87ADE9246F6370DB6008205B2EAE5B95</AdobeID>
                <TimeStamp>1401433567</TimeStamp>
            </PendingClaim>
        </PendingClaims>
        <IsSuite>SUITE</IsSuite>
        <APIVersion>2.0</APIVersion>
        <PersonGUIDWithAuthSource>10B3010147A877E8992015B9@AdobeID</PersonGUIDWithAuthSource>
    </response>
</PlugPlugEnvelope>
2014-09-01 16:11:31 : INFO PlugPlugUnloadExtension called for extension : com.OLO.Nemo.extension
2014-09-01 16:11:31 : DEBUG AllocatePlayer() callback called. playerOptions: 0B4CFB01
2014-09-01 16:11:31 : DEBUG AllocatePlayer() callback returned: PlugPlugErrorCode_success
2014-09-01 16:11:31 : DEBUG Connected PlugPlug DOM to APE player
2014-09-01 16:11:31 : DEBUG Looking for available StageManagers
2014-09-01 16:11:31 : DEBUG Looking for available StageManagerBundles in StageManagerManifest at C:\Program Files (x86)\Common Files\Adobe\CEP\StageManager\StageManagerManifest.xml
2014-09-01 16:11:31 : DEBUG No StageManagerManifest found at C:\Program Files (x86)\Common Files\Adobe\CEP\StageManager\StageManagerManifest.xml
2014-09-01 16:11:31 : DEBUG Looking for available StageManagerBundles in StageManagerManifest at C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\StageManager\StageManagerManifest.xml
2014-09-01 16:11:31 : DEBUG No StageManagerManifest found at C:\Users\BC-OLO\AppData\Roaming\Adobe\CEP\StageManager\StageManagerManifest.xml
2014-09-01 16:11:31 : DEBUG Looking for available StageManagerBundles in StageManagerManifest at C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\StageManagerManifest.xml
2014-09-01 16:11:31 : DEBUG Found 1 possible StageManagers in StageManagerManifest
2014-09-01 16:11:31 : DEBUG Added StageManagerBundle StageManagerBundle with Version (5.0.0.20140224_v5_0_0_62), ReleasePath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Release\StageManager-5.0.swf), DebugPath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Debug\StageManager-5.0.swf)
2014-09-01 16:11:31 : DEBUG Determining the most recent StageManagerBundle
2014-09-01 16:11:31 : DEBUG Now checking StageManagerBundle with Version (5.0.0.20140224_v5_0_0_62), ReleasePath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Release\StageManager-5.0.swf), DebugPath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Debug\StageManager-5.0.swf) against (null)
2014-09-01 16:11:31 : DEBUG Will use StageManagerBundle with Version (5.0.0.20140224_v5_0_0_62), ReleasePath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Release\StageManager-5.0.swf), DebugPath (C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Debug\StageManager-5.0.swf) as the most current StageManagerBundle
2014-09-01 16:11:31 : DEBUG StageManager SWF will be loaded from 'C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC 2014\Configuration\CEP\StageManager\Debug'
2014-09-01 16:11:32 : DEBUG Add StageManager event listener
2014-09-01 16:11:32 : INFO StageManagerController: Created StageManager <STAGE_MANAGER_0> for Extension <com.OLO.Nemo.extension>
2014-09-01 16:11:32 : INFO Return value of PlugPlugUnloadExtension call : PlugPlugErrorCode_unknown
2014-09-01 16:11:32 : INFO PlugPlugTerminate called
2014-09-01 16:11:32 : INFO StageManager: Disposing StageManager <STAGE_MANAGER_0>
2014-09-01 16:11:32 : DEBUG Remove StageManager event listener
2014-09-01 16:11:32 : DEBUG Disconnected PlugPlug DOM from APE player
2014-09-01 16:11:32 : DEBUG DisposePlayer() callback called. apePlayerRef: 06C4CE78
2014-09-01 16:11:32 : DEBUG DisposePlayer() callback returned: PlugPlugErrorCode_success
2014-09-01 16:11:32 : INFO Return value for PlugPlugTerminate: PlugPlugErrorCode_success

Assuming we have a CSXS Flash based extension which works with DW CC 2014, steps to be followed for the extension to show up in DW CC 2014:
1. The extension should be placed at /Users/labuser/Library/Application Support/Adobe/Dreamweaver CC 2014/en_US/Configuration/CEP/Extensions . [WIN: C:\Users\labuser\AppData\Roaming\Adobe\Dreamweaver CC 2014.1\en_US\Configuration\CEP\Extensions] . The installation of the zxp should have placed the extension in the above path.
2.   Add a custom menu item like <menuitem mmstring:name="menus/DWMenu_Window_BusinessCatalyst" key="Cmd+Shift+B" enabled="true" command="dw.toggleCSXSExtension("com.adobe.bccsdialog");" checked="dw.getFloaterVisibility('BCModulePanel');" id="DWMenu_Window_BC_Modules" /> where the argument in the call dw.toggleCSXSExtension is the Extension Id as seen in the manifest.xml at the line <Extension Id="com.adobe.bccsdialog">.
Note: All these will work provided the extension is successfully registered with DW.
To know if an extension is registered with DW, do the following:
1. On MAC, there is a CSXS preference plist file Users/labuser/Library/Preferences/com.adobe.CSXS.5.plist which has an entry named LogLevel. Set the value to 5 for detailed log. [On windows –Registry - Computer\HKEY_CURRENT_USER\Software\Adobe\CSXS.5]
2. Quit and Launch DW
3. Open Console application and under ~/Library/Logs/CSXS/, there will be a log file created with name csxs5-DRWV.log [WIN: log file is in C:\Users\labuser\AppData\Local\Temp]
4. In the log, search for "Register Extension called for Extension : com.adobe.bccsdialog, ExtensionType : Trusted" and under that, you should see "PlugPlugRegisterExtension() callback returned: PlugPlugErrorCode_success" which mean this extension is successfully registered with DW.
5. When you try loading the extension from the menu you have added, you should see an entry like "INFO PlugPlugLoadExtension called for extension : com.adobe.bccsdialog" followed in the next few lines by " INFO Return value of PlugPlugLoadExtension call : PlugPlugErrorCode_success" and you should see the extension loaded in DW.
If any of these steps fail with any value other than "PlugPlugErrorCode_success", the extension will not load in DW.
The solution provided here is a temporary one and we are bringing back the functionality we have removed in DW CC 2014 in the next release.

Change color of ColdFusion comments in Dreamweaver CC 2014

Hi All,
I've recently discovered Sublime Text 2, and really like their code coloring theme. 90% of my work still needs to be done in Dreamweaver. I was able to find a Colors.xml file I could use, that got it very close to looking like sublime text. The only real problem are ColdFusion comments.
I changed this line in the XML C:\Users\{me}\AppData\Roaming\Adobe\Dreamweaver CC 2014\en_US\Configuration\
<syntaxColor id="CodeColor_CFCommentText" text="#585835" bgcolor="#434343" /> from the original ffff99 bright yellow background, but after restarting Dreamweaver, the ColdFusion comments are still lite color text on this bright yellow background. Horrible.
It seems Dreamweaver CC 2014 removed a lot of ColdFusion options, sad. Many of us still use it for Front-End work, while ColdFusion Builder works better for back-end.
I really hope there is a way to get a dark color theme into Dreamweaver for ColdFusion.
Any suggestions?

What Adobe has done is blindly pull the rug right out from under our feet. Dreamweaver has been the one and only application I and thousands of others have used to code, design and FTP websites for years. Some of us have been using Dreamweaver as far back as when Allaire built it specifically to help ColdFusion developers. Dreamweaver offered ColdFusion tag support, a design view when needed, and an efficient way to FTP files.
It seems what Adobe is telling us now is that Dreamweaver is some how not the right application for developing ColdFusion websites, but oddly enough the correct one for PHP developers. The only reason I can see that Adobe stripped the support for ColdFusion within Dreamweaver is to sell us CF Builder... which is suspiciously missing from any Creative Cloud subscription. Otherwise there was no real reason to pull support from ColdFusion within Dreamweaver. It is simple greed.
The reality for a lot of developers is that we can barely pay the Creative Cloud subscription fees every month, much less purchase a whole new program just because Adobe has forced our hand. Adobe needs to reestablish ColdFusion support in Dreamweaver or, based on what I have read in many forums, they will be losing a lot of customers. There are a lot of CF developers looking for an alternative to all of Adobe's products because of this "slap in the face" and I am sure there are companies out their already looking at this enormous opportunity.
I, for one, am looking at other programs to replace everything I use from Adobe because I feel betrayed. Adobe may think they own the market but I am afraid they are going to learn the hard way. If you try to force the growth of the bottom line at the expense of ignoring your customers, you will fail. If you put your customers needs first, the bottom line will follow. Has history taught you nothing?

Exit Code 7 error installing Dreamweaver CC 2014

I can't install Dreamweaver CC (2014) - keeps erroring at about 82% installation with the following error (I'm on Windows 7)
Any help much appreciated... I have tried removing the sourceCodePro-Light-ttf font but this is always in use by 'another program' so won't allow me to delete or move temporarily - as for 'file (Seq 9336)???/
Cheers
Steve
Here's the error code:
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR: DF012, DF024 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
----------- Payload: Adobe Dreamweaver CC 2014.1 15.0.0.0 {7F823F8E-4348-11E4-8BF8-81763C49AA32} -----------
ERROR: DF012: Unable to find file(Seq 9336)
ERROR: DF024: Unable to preserve original file at "C:\Windows\Fonts\SourceCodePro-Light.ttf" Error 32 The process cannot access the file because it is being used by another process.(Seq 9336)

Thanks everyone
I'm no techie so reading through all the suggestions was sort of helpful but non gave the answer... or at least an answer I understood. In the end, I just used a bit of common sense after several more failed installation attempts following the use of the adobe cleaner tool/software, I decided that the problem was clearly an issue with permissions on the font mentioned in the error. So, backed up the font on to my desktop, and restarted windows 7 in safe mode. This allowed me to delete the font in question from the c:/windows/fonts folder which couldn't be done when booting up windows normally beacuse it was always 'in use by another application'.
Once the font was deleted, I rebooted again but this time in full windows mode rather than safe mode and installed Dreamweaver CC 2014 successfully.
Thanks for all your help guys, I do appreciate you posting the suggested links... if only the above simple instructions had been listed on the Adobe Troubleshooting pages, I could have done something more constructive with the 4 hours of my life I won't get back spent wasting my time fixing this!!!
Now for some shut-eye!
Steve

Dreamweaver CC 2014.1 is slow.

Dreamweaver CC 2014.1 is slow.

I have been experiencing overall sluggish performance since upgrading to 2014.1 (6947 build) as well. This is on my Win 7/64 desktop and more noticeably on my Macbook Pro (2010/ 8GB) Mavericks 10.9.5.
In particular, switching between local sites within the 'Files' window will quickly indicate the newly selected site, but the old files remain visible for quite a while with the 'beach ball' spinning for up to a couple of minutes. Sometimes it will even quit. This is the most obvious example with other, more subtle sluggish events.
I have restored preferences as recommended and even uninstalled/reinstalled DW. I only use Live Preview for actual previewing not while working on a page.
As I did not really notice these issues in v. cc 2014, I have considered rolling back to it but I would rather take advantage of the new features in 2014.1
Thank you for your attention to this matter.

Dreamweaver CC 2014 has stopped working

I've looked through the discussions for an answer and followed all suggestions. Using Dreamweaver CC 2014 on a PC running Windows 7 it is constantly going non-responsive or crashing.
This only appears to happen when in the Split Code=>Live mode. Doesn't seem to matter what site I'm working on or how simple the code is. I'll edit the code, the live view didn't refresh so I click the refresh icon and . . . frozen.
Here is the most recent error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Dreamweaver.exe
Application Version: 15.0.0.6947
Application Timestamp: 5423eb8a
Fault Module Name: Dreamweaver.exe
Fault Module Version: 15.0.0.6947
Fault Module Timestamp: 5423eb8a
Exception Code: c0000005
Exception Offset: 0000000000f2fa50
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 4baa
Additional Information 2: 4baa1a24fb111f7bdd3d8969cb831386
Additional Information 3: 8f0d
Additional Information 4: 8f0d0dea990ec7f10fa54e62cf026e25

Hi Labadie,
Can you provide us with the solutions that you have tried so far before we look for other options that can help you quickly overcome your problem?
Thanks,
Preran

"Code & Design" and "Code & Live" view problem i am getting in Dreamweaver CC 2014

Please anyone help me.
I have 2 webpages, one is with 12 columns fluid grid based and another is without fluid grid based.
Both are open in same site folder in Dreamweaver CC 2014.
I want to resize/edit my fluid grid div column in design view.
But i m not getting the proper menu (view-->Code and Design)
why the problem is happening ?
If my non-fluid page is active for edit purpose than i am getting the "View"-->"Code and Design"
if my fluid page is active for edit purpose than i am no getting the "View"-->"Code and Design"
but i am getting "View"-->"Code and live"
i am unable to resize my fluid div using the resize handler.
this is fluid based, i need "code and design view"
this is non-fluid based

There has been much discussion about this lately. You can add your vote for a return of Design View below.
Provide "Design View" for Fluid Grid Webpages
It's an "improvement" made to the October release to promote more people to use Live View editing in FGLayouts. As we're finding out, the removal of Design View in FGLayouts is severely impacting people's workflows.
Workarounds:
Step back to CC June release from links below
Win: http://download.adobe.com/pub/adobe/dreamweaver/win/cc/Dreamweaver_14_LS20.exe
Mac: http://download.adobe.com/pub/adobe/dreamweaver/mac/cc/Dreamweaver_14_LS20.dmg
or put an X in the FGLayout CSS comments
Change this:
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile:        5;
dw-num-cols-tablet:        8;
dw-num-cols-desktop:    12;
dw-gutter-percentage:    25;
to this:
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile:      X;
dw-num-cols-tablet:        8;
dw-num-cols-desktop:    12;
dw-gutter-percentage:    25;
Nancy O.

Jquery widget equivalent to spry dataset for dreamweaver CC 2014.1?

I built a website a while back with either CS4 or CS5. I used spry datasets to pull menu items into the tables on the website. I did some research and found that spry widgets were pulled from the CC suites for some reason and replaced with jquery widgets. I'm not 100% sure why adobe did this, but what jquery widget equivalent is there for the spry datasets in dreamweaver cc 2014.1?
Thanks for your help everyone!
-Joe

The closest that you will get to it http://www.dmxzone.com/go/21863/html5-data-bindings

I updated Dreamweaver to 2014 and this toolbar disapeared. I have a fresh install of 2014 on another computer and the toolbar is there.

I updated Dreamweaver to 2014 and this toolbar disappeared.
I have a fresh install of 2014 on another computer and the toolbar is there.
Anyone know how to get it back?

The file does have a "links to external files"

Dreamweaver CC 2014 won't launch

Just switched to a new Mac Pro. Per Adobe's instructions, I downloaded and installed Creative Cloud. Then from Creative Cloud I selected the Adobe apps to install. Several of the apps run just fine--no issues. However, no matter what I try, I can't get Dreamweaver CC 2014 to launch. The icon in the dock bounces a couple of times and that's it. No splash screen, no crash dialog. I checked CONSOLE and it has nothing showing for "Dreamweaver" or "Adobe" in the message. The ~Library/Logs/CrashReporter has no crash logs (user and root). I've repaired permissions (even though that has no impact on Adobe apps) and rebooted, but nothing works. I've also uninstalled and then re-downloaded and installed Dreamweaver CC 2014, but that didn't help.
What do I try now?
MacOS 10.9.4
Mac Pro 3.5 GHz 6-Core, 32 GB 1867 MHz DDR3

Hi All
I am hoping it is not rude to add my bit here but I am having exactly the same problem. I unistalled Dreamweaver and installed the 2014.....now I click on the icon it bounces twice and does not launch.
I have seen that the extension manager was used to resolve this issue by Montylee.....please can you tell me step by step how you did it as I have adobe extension now and keen to resolve this issue.
Also how do I unistall all traces of earlier versions I have that may be causing clashes?
Many thanks in advance.....
Getting desperate.... I am a relative novice so please treat me gently.....HA HA
John M

How do i find messages in trash back to 7/12/2014

I have checked save all messages on this computer
I cannot go back past 7/21/2014
How do I go further in trash

http://kb.mozillazine.org/Disappearing_mail

Is it possible to have two testing servers in Dreamweaver CC 2014?

Hi,
Is it possible to set up Dreamweaver CC 2014 so that there are two Remote servers and one Testing server? I know how to set it up with 1 of each but I have two live servers running the same site (for business reasons).
Thanks in advance
Ben

Sure. I really wanted two remote servers. We have a live and "backup live" server operational inside and outside of China. We do need to switch between them relatively frequently e.g. this week, external access to Hong Kong servers has been severely restricted, so we switch to a godaddy-hosted solution. But we also want a live testing server / development environment where we can build. Completed solutions get deployed to both live servers.
I can work around it, but am just being lazy really. And Dreamweaver seems to make lots of other things quicker, so I thought I'd ask

Windows 7 64 bit Dreamweaver CC 2014 & Lightroom 5: Trying to insert a lightroom web gallery into a template in Dreamweaver

I am using a template for my website in Dreamweaver CC 2014. I installed a lightroom 5 web gallery into the template. I have an editable region where my main content goes that is where I inserted the web gallery. The main content css height is set at Auto. The web gallery shows up but only the very top half of the gallery. The whole web gallery wont push down the main content section so you can see the whole gallery. If I set the main content at height 700px then the whole gallery shows up, but because this is a template it screws up all my other pages because of the height setting. I need that to be variable. What am I doing wrong?

Most likely that main content area also contains a floated element and you are not clearing the float before closing the main content container. Floated elements are removed from the normal flow. Being removed from the normal flow means that a container for that floated element does not regard the floated element as being in it, and will collapse around its non-floated content. To prevent this from happening you should clear the float before closing the container, e.g.,
<div>
<img src="very-tall-image.jpg" style="float:left">
<p>some content</p>
</div>
This div will only be as tall as the paragraph tag requires, thus truncating the image.
But here -
<div>
<img src="very-tall-image.jpg" style="float:left">
<p>some content</p>
<div style="clear:left;"></div>
</div>
This div will show the whole image.

Dreamweaver update 2014.1.1 is now live

The Dreamweaver team is happy to announce “Dreamweaver CC 2014.1.1” Win Build #6981 & Mac Build #6982 build.
Please refer to the What’s New for detailed information here
For the list of known issues with this release, see Known issues | Update to Dreamweaver CC 2014 release
For the list of bug fixes, see Bugs fixed in the February 2015 release
While we do not foresee any issue with updating your application, it is always best to complete your immediate tasks before you update your software. I am locking this discussion so that we can discuss topics related to this release under more relevant headings.
Note: On the Creative Cloud application, the version appears as 2014.1. Use the Update button next to it.
If you do not see an update in Creative Cloud application, quit the application. Click the wheel icon on top and select Quit. Relaunch the application and the update should be listed now. To make sure that you have installed the latest update, open Dreamweaver after the update is complete (took me around 5 minutes over a high speed connection today), and select Help > About. You should see this screen. Ensure that the version is listed as 2014.1.1. The build number for Windows is 6981 and for Mac OS is 6982.
Tip: You can launch Dreamweaver directly from the Creative Cloud application by clicking the name of the software.
When you open the latest Dreamweaver update, the latest (and its most exciting feature) becomes immediately apparent. Using data from many sources, the team responsible for content and learning have put together a set of tutorials that will help new users get started with web design, and of course, Dreamweaver. I am very excited especially because we now have one repository that is available immediately within Dreamweaver.
Key feature set for this patch release:
New Welcome screen
Whether you are a beginner or an experienced user, or evaluating the new version of Dreamweaver, you can now get all the essential learning resources right on the Welcome Screen.
CSS Designer enhancements
This update includes a few changes to the CSS Designer user interface and a change in the default setting of the Show Set check box.
Enhancements to Extract panel
Live Guides and Element Quick View icon now appears in Live View when you drag images from the Extract panel. These visual aids help you place the image quickly and precisely in the required position.
Remote debugging of Live View
You can now remotely debug your Dreamweaver documents open in Live View using Google Chrome DevTools.
Change in the view mode of dynamic documents
Dynamic documents such as PHP, CFM, and ASP no longer open in Code View by default. They open in the same mode (Code/Live/Split) as the last closed document or the last document that was in focus.
Enhancements to Live View editing : Drag and drop elements, Marquee selection, Element Display enhancements, New Code View themes.
Thanks,
Preran

The Dreamweaver team is happy to announce “Dreamweaver CC 2014.1.1” Win Build #6981 & Mac Build #6982 build.
Please refer to the What’s New for detailed information here
For the list of known issues with this release, see Known issues | Update to Dreamweaver CC 2014 release
For the list of bug fixes, see Bugs fixed in the February 2015 release
While we do not foresee any issue with updating your application, it is always best to complete your immediate tasks before you update your software. I am locking this discussion so that we can discuss topics related to this release under more relevant headings.
Note: On the Creative Cloud application, the version appears as 2014.1. Use the Update button next to it.
If you do not see an update in Creative Cloud application, quit the application. Click the wheel icon on top and select Quit. Relaunch the application and the update should be listed now. To make sure that you have installed the latest update, open Dreamweaver after the update is complete (took me around 5 minutes over a high speed connection today), and select Help > About. You should see this screen. Ensure that the version is listed as 2014.1.1. The build number for Windows is 6981 and for Mac OS is 6982.
Tip: You can launch Dreamweaver directly from the Creative Cloud application by clicking the name of the software.
When you open the latest Dreamweaver update, the latest (and its most exciting feature) becomes immediately apparent. Using data from many sources, the team responsible for content and learning have put together a set of tutorials that will help new users get started with web design, and of course, Dreamweaver. I am very excited especially because we now have one repository that is available immediately within Dreamweaver.
Key feature set for this patch release:
New Welcome screen
Whether you are a beginner or an experienced user, or evaluating the new version of Dreamweaver, you can now get all the essential learning resources right on the Welcome Screen.
CSS Designer enhancements
This update includes a few changes to the CSS Designer user interface and a change in the default setting of the Show Set check box.
Enhancements to Extract panel
Live Guides and Element Quick View icon now appears in Live View when you drag images from the Extract panel. These visual aids help you place the image quickly and precisely in the required position.
Remote debugging of Live View
You can now remotely debug your Dreamweaver documents open in Live View using Google Chrome DevTools.
Change in the view mode of dynamic documents
Dynamic documents such as PHP, CFM, and ASP no longer open in Code View by default. They open in the same mode (Code/Live/Split) as the last closed document or the last document that was in focus.
Enhancements to Live View editing : Drag and drop elements, Marquee selection, Element Display enhancements, New Code View themes.
Thanks,
Preran

APPCRASH is back in Dreamweaver CC 2014

Similar Messages

Maybe you are looking for