Dreamweaver CC 2014.1 / Windows 8.1 Bug

When opening a .aspx file i'm getting the below errors:
An alert pops up for each asp.net control on the page.
This is happening to myself and a colleague sat next to me - could this be looked in to, i need to know if this is an issue at your end or our end.
Thanks,
Michael

Have you tried restoring preferences yet?
Restore preferences | Dreamweaver CS4, CS5, CS5.5
or
Restore preferences | Dreamweaver CS6, Dreamweaver CC

Similar Messages

  • Frequent crashing in Adobe Dreamweaver CC 2014 on Windows 7 Professional 32bit

    Dear All,
    We have Adobe Dreamweaver CC 2014 installed as part of a Creative Cloud package across multiple machines running Windows 7 Professional 32bit.
    EVERY time we open the software, we are able to run through the "demo" introduction but when we get to the create new document screen we get an "Adobe Dreamweaver CC 2014 has stopped working" error and have to close it.
    We have tested this on multiple machines (adequate system specs) with multiple users and it is happening every time. I can confirm we have the latest version of DW CC 2014 installed and all Windows Updates.
    Note: We have packaged Adobe Dreamweaver CS6 and this works without issue, we are able to open a new document with no problem.
    Any help would be appreciated!
    Regards,

    Hi Mcarlinx,
    Can you please share the screenshot of this location -
    In Registry entry navigate to HKEY_CURRENT_USER\Software\Adobe\Dreamweaver CC 2014.1(or which ever version in which you are seeing the crash)\Cloud Sync preferences.
    Also please share the logs -
    How to Create crash logs on win –
    You need to add these entries in registry.
    1.  Go to run, type regedit and enter. This will open Registry Editor.
    2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting->Right Click->New->Key. New key named "New Key #1" will be created. Rename it to LocalDumps. Add two entries LocalDumps
    Right click on LocalDumps->New->Expandable String Value (REZ_EXPAND_SZ). Double click on the  entry created and add value name : DumpFolder and value data : %LOCALAPPDATA%\CrashDumps.
    Right click on LocalDumps->New->DWORD (32 bit) Value(REG_DWORD). Double click on the value created and add value name : DumpType and value data :1
    Next time when the application crashes you will find the crash dump at C:\Users[UserName]\AppData\Local\CrashDumps. Dumps will be created only in case of crash and not hang.
    Thanks!
    Kusha

  • DreamWeaver CC 2014 live view not correct

    I am using the new DreamWeaver CC 2014 on Windows 7. I have a html doc using a separate CSS style sheet, JQuery, JQuery UI, and Modernizr. The page is setup using flexbox and displays as expected in Chrome and IE. Everything validates outs without warnings or errors.  I turned on live view and the displayed page is not even close to how chrome shows the page.
    Is any one else having similar issues? 

    Hi All,
    This issue has been fixed in the latest Dreamweaver CC 2014.1 update, which is now live.
    We would encourage all of you to give it a try and would love to know your experience around it.
    Please read this post (Dreamweaver October 2014 release is now live! Read this first.) before you proceed with the installation.
    Cheers,
    Subhadeep

  • Can't paste into Dreamweaver CC 2014.1 after opening any browser on Windows 7 system...

    I couldn't paste anything in Design or Code view after updating to Dreamweaver CC 2014.1 this week on my Windows 7 system. I discovered that if I rebooted my computer and opened Dreamweaver without opening any browsers (have tried Chrome, Firefox, IE, Safari, and Opera), then I could paste in both Design and Code views. After I opened ANY browser, however, I could no longer paste in Dreamweaver and couldn't paste in Dreamweaver again unless I rebooted and didn't open any browsers. At first I thought it was a problem with Chrome (a common culprit) and uninstalled all of my extensions, but Chrome clearly was not the culprit this time. All five of my browsers (with tedious system reboots in-between) triggered the same inability to paste into Dreamweaver. I had not installed the update on my Windows 7 laptop yet, and I found that that still was working just fine, so I uninstalled the 2014.1 update from my desktop system and reinstalled the previous version. That eliminated the problem, but I'd sure like to be able to keep my Adobe software updated without experiencing these deal-breaking issues.

    Thanks, Preran. After uninstalling the 2014.1 update and reinstalling the previous version, I now installed the 2014.1 update again. Instead of jumping straight into restoring the preferences, I decided to test it out as-is, and it worked! No problems with pasting after opening any of my five browsers. I wonder what may have gone wrong the first time...or what was corrected during the uninstall/reinstall process. In any case, it is working again now and I am grateful. Thanks!

  • Why there is no "Extensions" under "Window" menu in Dreamweaver CC 2014?

    Hi, I just installed Dreamweaver CC 2014. I found there is no "Extensions" under "Window" menu. Do I need to install Extension Manager manually? If so, where is the link to install Extension Manager?

    Hello chifang1,
    first, my Extension Manager is situated here: Program Files (x86)/Adobe/Adobe Extension Manager CC/Adobe Extension Manager CC.exe. From there I start it. In my case the CC manager mamnages cc and so too the 2014 extensions.
    Please explore the following sources. First of all I would have a look there: http://helpx.adobe.com/pdf/extension_manager_reference.pdf. At many places, so too here - it is noted this "Important note: MXP type extensions are not supported in Extension Manager CC. The MXP format has been replaced by the ZXP extension format. An MXP extension can be converted to a ZXP extension using the “Convert MXP Extension To ZXP” tool which can be found in the Tools menu in Extension Manager CS6." This might be a possible sources of error.
    Then, did you try to download your ext-manager from there: http://www.adobe.com/exchange/em_download/ and could you explore esp. this bundle: http://helpx.adobe.com/extension-manager/topics/extensions.html?
    To avoid these problems I work with the both, DWCC and DW 2014 simultaneously. Ok, that does not sound so good, but for me it is easier, than hold up with a complicated troubleshooting.
    Hans-Günter

  • 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 CC 2014 crashes every 3 to 5 minutes. Windows 8.1. Uninstalled and reinstalled again today, not any better.

    I had the trial version for the last 30 days. I bought the product Sunday and entered the license code. The next day it started crashing every few minutes. I looked up similar reports in this forum and tried what has been recommended. I made sure Verdana and Tahoma fonts are set to "visible". I checked my CSS for open curly parenthesis. I uninstalled Dreamweaver and reinstalled. I rebooted. I cleared the cache.
    I have a simple little site for a historical society. There are no extensions installed. I have one CSS file and no other files except for the few HTML pages that make up the site. There are no forms or javascript in use.
    Val
    I don't see anything broken in my CSS
    body {
      background-image: url(images/map.jpg);
      margin-top: 50px;
      margin-bottom: 10px;
    #container {
      width: 960px;
      text-align: center;
      margin: auto;
    #top {
        height:83px;
        background-image:url(images/Top.jpg);
    #middle {
      background-image: url(images/Middle-1.jpg);
      list-style-type: disc;
      list-style-position: inside;
      color: #9E221F;
      font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
      font-size: 1.15em;
      line-height: 150%;
    #bottom {
      height: 83px;
      background-image: url(images/Bottom.jpg);
      background-position: 0 -417px;
      margin-bottom: 10px;
    #container_foot {
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      font-size: 0.7em;
      line-height: 120%;
      color: #663300;
      border-top: 1px solid #663300;
      width: 800px;
    #container_site_nav {
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      font-size: 0.8em;
      line-height: 80%;
      color: #663300;
      border-top: 0px solid #663300;
      border-bottom: 0px solid #663300;
      padding-bottom: 8.5px;
      width: 800px;
    .nav_subtext {
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      font-size: 0.86em;
      line-height: 70%;
      font-weight: 600;
      margin-top: 0px;
    .nav_text {
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      font-size: 1.15em;
      line-height: 120%;
        font-weight: 600;
      margin-top: 0px;
        margin-bottom: 0px;
    a:link {
      color: #131266;
      text-decoration: none;
    a:visited {
      text-decoration: none;
      color: #131266;
    a:hover {
      text-decoration: underline;
    a:active {
      text-decoration: none;
    h1 {
      font-weight: normal;
    h2 {
      font-size: 1.3em;
      line-height: 100%;
      font-weight: 550;
      padding-top: 22px;
      padding-bottom: 6px;
      color: #9E221F;
    h3 {
      font-size: 1.1em;
      line-height: 170%;
      margin-top: 0px;
      margin-bottom: 0px;
      color: #131266;
    h4 {
      font-size: 1.05em;
      font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
      line-height: 100%;
      margin-top: 22px;
      margin-bottom: 2px;
      color: #131266;
    h5 {
      font-size: 1.2em;
      line-height: 100%;
      margin-top: 32px;
      margin-bottom: 12px;
      /color: #131266;
    .dropcap {
        float:left;
        color: #131266;
        font-size:82px;
        line-height:70px;
        padding-right:15px;
        padding-top:2px;
        font-family:Constantia;
        /text-shadow:1px 1px 1px #444;
    p2 {
      font-size: 0.85em;
      font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
      line-height: small;
      color: #9E221F;
      margin-top: 0px;
      margin-bottom: 0px;
      font-style: oblique
    p3 {
      font-size: 0.85em;
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      line-height: 80%;
      color: #9E221F;
      font-weight:600;
      word-spacing:-1px;
      margin-top: 0px;
      margin-bottom: 0px;
      font-style: oblique;
    p4 {
      font-size: 0.85em;
      font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
      line-height: 100%;
      color: #9E221F;
      font-weight:600;
      margin-top: 0px;
      margin-bottom: 0px;
      font-style: oblique

    OK I will remove the Ps. The crashes started before I created those, but I will remove them. Here is one of the crash reports.
    Log Name:      Application
    Source:        Application Error
    Date:          11/18/2014 12:15:27 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Muffin
    Description:
    Faulting application name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
    Faulting module name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
    Exception code: 0xc0000005
    Fault offset: 0x00000000004fa27e
    Faulting process id: 0x2324
    Faulting application start time: 0x01d00352ce09bc96
    Faulting application path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
    Report Id: 7cf25798-6f46-11e4-8288-a0886943af3e
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-11-18T17:15:27.000000000Z" />
        <EventRecordID>123445</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Muffin</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Dreamweaver.exe</Data>
        <Data>15.0.0.6947</Data>
        <Data>5423eb8a</Data>
        <Data>Dreamweaver.exe</Data>
        <Data>15.0.0.6947</Data>
        <Data>5423eb8a</Data>
        <Data>c0000005</Data>
        <Data>00000000004fa27e</Data>
        <Data>2324</Data>
        <Data>01d00352ce09bc96</Data>
        <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
        <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
        <Data>7cf25798-6f46-11e4-8288-a0886943af3e</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    This is what the DETAILS tab on the error report says:
    Log Name:      Application
    Source:        Application Error
    Date:          11/18/2014 12:15:27 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Muffin
    Description:
    Faulting application name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
    Faulting module name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
    Exception code: 0xc0000005
    Fault offset: 0x00000000004fa27e
    Faulting process id: 0x2324
    Faulting application start time: 0x01d00352ce09bc96
    Faulting application path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
    Faulting module path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
    Report Id: 7cf25798-6f46-11e4-8288-a0886943af3e
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-11-18T17:15:27.000000000Z" />
        <EventRecordID>123445</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Muffin</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Dreamweaver.exe</Data>
        <Data>15.0.0.6947</Data>
        <Data>5423eb8a</Data>
        <Data>Dreamweaver.exe</Data>
        <Data>15.0.0.6947</Data>
        <Data>5423eb8a</Data>
        <Data>c0000005</Data>
        <Data>00000000004fa27e</Data>
        <Data>2324</Data>
        <Data>01d00352ce09bc96</Data>
        <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
        <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
        <Data>7cf25798-6f46-11e4-8288-a0886943af3e</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

  • 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

  • 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.

  • Cannot activate Dreamweaver MX 2004 on Windows 7 64 bit pc?

    Hello.
    Does anybody in here know how to activate Dreamweaver MX 2004 on a Windows 7 64 bit pc?
    I keep getting the message that there is an internet connection problem.
    I have deactivated my firewall etc., but it doesn't help me.
    Anybody got an idea? Adobe Chat does not have the answer for me!
    Regards Anders Fj

    Wow! Thank you. It Works! Clever!
    This is really helpful for those
    of us who are nore professionals. I only use Dreamweaver MX 2004 to
    maintain and repair my own small homepage with photos. And I know how to
    use Dreamweaver MX 2004 and I am not interested in learning new tools -
    not now
    ONE MORE QUESTION THOUGH: Where and how do I update my
    Dreamweaver MX 2004 now that I have installed Dreamweaver MX 2004 on my
    new Win 7 64 bit pc?
    Regards
    Anders Fjeldberg, Denmark
    Ken Binney
    skrev den 2014-05-04 00:01:
    CANNOT ACTIVATE DREAMWEAVER MX 2004 ON
    WINDOWS 7 64 BIT PC?
    created by Ken Binney  in _Dreamweaver
    support forum_ - View the full discussion 
    >

  • A few Problems/Glitches with InDesign CC 2014 on Windows 7 and CC on Mac OS 10.6.8

    We're experiencing some quirky glitches with InDesign CC on a Mac running OS 10.6.8, and with CC 2014 on Windows 7. I'll indicate which system on each problem...
    Anchored objects disappear when anchored into boxes that are, in turn, anchored into text flow.
    We publish catalogs and anchor all our images to the accompanying text so that as we remove/add products, all the text and images flow together. We have several instances in which we use a box to highlight certain products. In that box might be 1, 2, 3, or more products, each with anchored images. When we anchor those boxes within the main text flow, many of the images inside the box disappear. The anchors are still there but we can't see the images. This is happening on both systems.
    "Replace" field disappears when selecting anything from the “wildcard/special char.” menu in "find and replace". Windows.
    Shift click to unlock master page items bring background item to foreground.
    In CS4 and 5.5, if you shift-clicked to release an item from the master page, the top-most item was released. Now it seems as though the item that is farthest behind gets released first, which makes it impossible to select any other items if that one is a full-page background. Both systems.
    Double/triple clicking on a word to select it does nothing.
    You could literally click for 5 minutes and it wont select anything. You have to click off the box, use selection tool then click back onto the box and then it will work. You can move the cursor a few letters away and it will select the appropriate line or paragraph but it did not work this way in earlier versions. Both systems.
    Any suggestions, or is it something we're doing wrong?
    Thanks,
    Lloyd

    The list of obvious errors and glitches and illogical behaviour in all Indesign versions is long. With newer versions, some items disappeared from the list, but new ones were added.
    Best is to use the Adobe bug report form to let Adobe know in hope, they really read, care and someday do something about it.

  • Erreur à l'ouverture et à l'enregistrement d'un fichier dans Dreamweaver cc 2014.1

    windows 8.1
    Dreamweaver cc 2014.1
    6947 build
    Bonjour,
    Suite à la mise à jour de Dreamweaver cc 2014.1,  j'ai des alertes à chaque ouverture et fermeture de fichier (voir captures ci-dessous).
    J'ai désinstallé et installé de nouveau l'application sans solutionner le problème. Pas de résultat sur ce cas, en faisant une recherche dans les FAQ et forum.
    Quelqu'un a-t-il une solution ou une manip pour supprimer cette erreur ?
    merci bien
    Erreur à l'ouverture d'un fichier
    Erreur à l'enregistrement d'un fichier

    résolu
    pour info :
    il faut supprimer le fichier .dat dans le dossier C:\Users\[utilisateur]\AppData\Roaming\Adobe\Dreamweaver CC 2014.1\fr_FR\Configuration
    et redémarrer l'application

  • 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 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!).

  • 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.

Maybe you are looking for

  • New version of GarageBand is not working on iPhone 4!

    Since I've upgraded to version 2.0, I can't make music with iPhone 4 anymore. The piano is late and it's IMPOSSIBLE to record complexed tracks. I'm extremely disappointed and angry because GarageBand is the main software I use for making music. Does

  • Using TreeViewer and creating a pop-up menu?

    I am using Eclipse Ganymede(3.1?) to write my program. This project has multiple parts(most issues/progress can be tracked back in java-forums.org) and I am trying to get the last bit of my GUI finished. I have a TreeViewer that displays on top of a

  • How to retrive archived messages in sxmb_moni

    Hi, My client  want to see specific date archive messages, how to see those messages in SXMB_MONI window.  Let me know any standard program and procedure.  I am using PI 7.0 version SP19.

  • ArrayBindSize and Size for PLSQLAssociativeArrays

    Hey there, I'm a complete newbie to ODP.NET and was hoping someone may be able to help with an issue. I basically need to call an SP from a VB.NET application and got as far as I could with the code below. The problem is that the parameters associate

  • Use of "picture" on my vCard

    I find that the tiny image in the top left of my vCard (the one with the account icon) somehow has a randam photo from iPhoto. I don't know how it got there. I would now like to edit this "picture" to use a snapshot portrait from Photo Booth. I've fo