Skip to main content
A
Anonymous
March 1, 2009
Answered

css copy paste problem in Dreamweaver CS4

  • March 1, 2009
  • 45 replies
  • 43682 views
Having a problem in CS4 when I want to copy and paste things in my stylesheet.
Whenever I do ctrl +c to select a something the whole stylesheet gets selected. And that is not what I want.
Even is I want to copy something from an other css into the css I am working on it won't do the job.

Anyone having the same problem and found a solution?
    This topic has been closed for replies.
    Correct answer

    Forgive me as I'm new to DW CS4, but I may have a solution.  I encountered the css copy problem as well, but I turned off (unchecked) "Enable Related Files" (Edit -> Preferences -> General -> Document Options -> Enable Related Files).  I had to restart Dreamweaver, but this seems to have fixed the bug.

    I've never used the "Enable Related Files" feature, so it's not a big deal to me - much less of a big deal than not being able to copy and paste.  At least it seems to be a stable work around to the "css copy paste" problem.

    Hope it helps!  Let me know if this resolves the issue for anyone else.

    -- Trevor

    Vista Home Premium 64

    DW CS4 Version 10.0 Build 4117

    45 replies

    Show previous replies
    M
    Malveka
    New Participant
    April 12, 2009

    I am experiencing a copy-paste problem very similar to that described in this thread.  Thankfully, I was able to find this thread and hence a workaround.  For me, copy-paste in an HTML document simply didn't work in my custom workspace.  The text selection would highlight properly and when I pressed Ctrl-C the highlight color would change.  When pressing Ctrl-V, however, the only thing that happened was that the selection highlight disappeared.  The text was not copied.

    Switching my workspace to Classic and back has fixed the problem for now.  I've only just discovered the problem (I'm a new user and this is my first custom workspace) so I don't know how it will play out over time.  Thanks to the people in this thread, however, I have an apparent workaround.  8^)

    A
    Anonymous
    April 2, 2009
    I just submitted a bug report. I have exactly the same problem you all mention here and have tried all the things you all have tried and I'm still having this annoying issue. I'm on a PC, using CS4. As much as I paid for this product, I'd really like some help from Adobe on fixing this bug. Please.
    N
    Newsgroup_User
    Inspiring
    March 30, 2009
    Roy Sinclair wrote:
    > Update: After restarting my Mac at the weekend and opening only DW CS4, Firefox
    > and Mail, the bug is no longer apparent. This means that it is probably being
    > triggered by another app, or a sub-app within CS4. This is good news (that it
    > might be traceable) so I will watch for it returning then note what I did and
    > will report back.

    Please do. Several people seem to have this problem, but most people are
    not affected. Tracking down the trigger is the key to solving this mystery.

    --
    David Powers
    Adobe Community Expert, Dreamweaver
    http://foundationphp.com
    R
    Roy Sinclair
    Participating Frequently
    March 30, 2009
    Update: After restarting my Mac at the weekend and opening only DW CS4, Firefox and Mail, the bug is no longer apparent. This means that it is probably being triggered by another app, or a sub-app within CS4. This is good news (that it might be traceable) so I will watch for it returning then note what I did and will report back.
    N
    Newsgroup_User
    Inspiring
    March 26, 2009
    Al Sparber - PVII wrote:
    > I didn't know Adobe was still supporting Dreamweaver CS4. That's good to
    > know :-)

    :-)

    --
    David Powers
    Adobe Community Expert, Dreamweaver
    http://foundationphp.com
    N
    Newsgroup_User
    Inspiring
    March 26, 2009
    "David Powers" <david@example.com> wrote in message
    news:gqfmsj$kn9$1@forums.macromedia.com...
    > Roy Sinclair wrote:
    >> Further info about the bug now that I am using DW4 more...
    >
    > That's useful information. I'll pass it on to the QA team to see if it
    > helps them identify the cause.
    >
    > Small nitpick, it's DW CS4. DW4 is an ancient version. Confusing name, I
    > know, but referring to the wrong one could give the incorrect impression
    > that you're talking about an ancient version that's no longer supported.

    I didn't know Adobe was still supporting Dreamweaver CS4. That's good to
    know :-)


    --
    Al Sparber - PVII
    http://www.projectseven.com
    Dreamweaver Menus | Galleries | Widgets
    http://www.projectseven.com/go/apm
    An Accessible & Elegant Accordion




    N
    Newsgroup_User
    Inspiring
    March 26, 2009
    Roy Sinclair wrote:
    > Further info about the bug now that I am using DW4 more...

    That's useful information. I'll pass it on to the QA team to see if it
    helps them identify the cause.

    Small nitpick, it's DW CS4. DW4 is an ancient version. Confusing name, I
    know, but referring to the wrong one could give the incorrect impression
    that you're talking about an ancient version that's no longer supported.

    --
    David Powers
    Adobe Community Expert, Dreamweaver
    http://foundationphp.com
    R
    Roy Sinclair
    Participating Frequently
    March 26, 2009
    quote:
    Originally posted by: Newsgroup User
    Small nitpick, it's DW CS4. DW4 is an ancient version. Confusing name, I
    know, but referring to the wrong one could give the incorrect impression
    that you're talking about an ancient version that's no longer supported.

    Noted - thank you.
    R
    Roy Sinclair
    Participating Frequently
    March 26, 2009
    Further info about the bug now that I am using DW4 more...

    The bug only occurs when one first switches to a page/script, so if one is working on a single script then it will only show itself until one carries out an action that negates it e.g. when first selecting a script, place the cursor anywhere among the code, press return, then delete. Once this is done the bug remains hidden until another script is selected.

    As mentioned above, the area that is selected by the bug is limited to the current section of php (for example) if one is working on a script with both php and html within.

    So, if you work with single scripts and do not hand-code, you may not notice the bug but if like me you are constantly cutting or copying and pasting code from script to script, this is a serious impediment to work flow efficiency.
    V
    viveredesign
    Known Participant
    March 24, 2009
    My current work-around (until Adobe pushes out a patch) is to quickly change workspaces (saved pallet locations) to some random workspace and then back to my workspace. This seems to reset some bit inside Dreamwaver getting the code-selection working again TEMPORARILY (it will eventually creep back in).

    I highly suspect the "Element View" (right click on a div in design view) has something to do with it since it seems to want to select whole-blocks as though the element views were set to "hidden."

    Does anyone have a quicker work-around?
    Milo_Z
    Milo_Z
    New Participant
    March 25, 2009
    I haven't really found a workaround. One thing I did notice, though, is that if I work with the code in the Code Inspector as opposed to the Code View it doesn't happen. So, I'll now have to just use F10 a whole lot. Still not an ideal workflow that's for sure. Hope they fix it soon!
    R
    Roy Sinclair
    Participating Frequently
    March 24, 2009
    Yes I realise that David. If you look at where I came in a few hours ago, I was mearly letting people know that I had raised a support ticket for this issue. Murray and yourself kept the thread going, to which I naturally responded - as one does when conversing.

    Thank you for emailing the product manager. I hope that he bumps this bug up the order of priorities because I really don't want to have to start learning a new app interface after all these years of using DW.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices