Skip to main content
I
IronADDT
Known Participant
July 29, 2012
Question

issue with OSX 10.8... Could Not Save File

  • July 29, 2012
  • 46 replies
  • 41631 views

After installing Mountain Lion, Adobe Fireworks CS6 (12.0.0.236) now returns an error message when exporting via Image Preview.

“Could Not Save File”

“The File Was Not Found”

However, FW CS6 save the file... how do I get the error message to go away?

    This topic has been closed for replies.

    46 replies

    Show previous replies
    R
    rutherfordcreative
    Participant
    February 11, 2013

    Has anyone else had success with first repairing disk permissions then installing CS6 over your current install? My coworker has not seen any more issues since we performed these tasks.

    J
    jpost-design
    Participating Frequently
    February 14, 2013

    I haven't tried repairing disk permissions then installing CS6 over your current install yet. Could you give a list of instructions for the steps? For example, do you uninstall first, then repair, then reinstall? And are there any specific settings in disk permissions to be set?

    R
    rutherfordcreative
    Participant
    February 14, 2013

    What worked in my case (unless I'm forgetting something) was just these three steps:

    1. Quit Fireworks then move all Fireworks preferences to your desktop.
      1. ~/Library/Preferences/Adobe Fireworks CS6
      2. ~/Library/Preferences/com.macromedia.fireworks.plist
    2. From Disk Utility, repair disk permissions.
    3. Install CS6 over current CS6 install.
    D
    darth_homer
    Participant
    February 7, 2013

    Same problem. CS6 and 10.8.2

    T
    TimTimmers
    Known Participant
    February 11, 2013

    Same problem, CS6, 10.8.2. I also get those idiotic errors when trying to use the updater. Reinstalled the suite, cleaned everything, etc. etc. still happens. Not impressed.

    Please, Adobe, fix your product.

    A
    Anonymous
    January 31, 2013

    Oh, and yes, I've seen this same error as well.

    K
    kwfricke
    Participant
    January 31, 2013

    +1 ....come on Adobe!

    A
    Anonymous
    January 31, 2013

    This happens to me when just doing normal file saves. At a certain point, my Fireworks file refuses to save.

    P
    pixelneer
    Participant
    January 23, 2013

    Seriously? Still nothing?

    The OP is from July of 2012, we are at the end of January 2013, and this issue still persists.

    S
    suntrop
    Participant
    January 29, 2013

    I really don't know what I pay for. Adobe's prices are excessive and you can't stay with older software versions because they have a lot more errors and bugs and won't work at all. Thus you have to upgrade and pay. But their improvements are getting smaller and thinner and bug fixes are rare. I really really would love to switch to another software but unfortunately there is no alternative.

    Z
    ZebraMark
    Participating Frequently
    January 17, 2013

    It's true that Adobe wants Fireworks to die. About a year ago I took part in an Adobe online survey about Fireworks that, if you read between the lines, seemed to imply this was the case.

    J
    johnnie_n
    Participating Frequently
    January 17, 2013

    Makes perfect sense, how much of Fireworks changed in CS6?

    I have to admit that when I filed a bug report for this someone from the Fireworks team got back to me almost immediately which was very encouraging, but that was months ago.

    Earlier someone mentioned Sketch -- if I didn't have the Master Collection that's definitely what I'd be using now for web projects.

    J
    jpost-design
    Participating Frequently
    January 23, 2013

    Actually, a few updates for FW CS6 include the CSS export panel, jQuery mobile themes, and sprites. Though unfortunately the CSS panel has developed issues of its own, details on another thread http://forums.adobe.com/message/4991417#4991417

    R
    rutherfordcreative
    Participant
    January 16, 2013

    A coworker of mine ran into this issue yesterday and I was able to resolve it by reinstalling Fireworks over his current install.

    For Adobe (in case they are reading this), neither removing all preferences nor repairing OSX permissions fixed the issue.

    E
    eNJayBe
    Participating Frequently
    January 17, 2013

    Just tried reinstalling but I’m still getting the error (even after a reboot).

    Let’s just face it, Adobe have abandoned Fireworks to die.

    R
    rutherfordcreative
    Participant
    January 17, 2013

    What I would say then is before I reinstalled I removed all preferences and application support files for Fireworks, Repaired Disk Permissions and then reinstalled Fireworks.

    C
    creative-tags
    Participant
    January 9, 2013

    I'm seeing this too

    R
    Rembem
    Participant
    January 2, 2013

    Same here. 10.8 and Fireworks CS5.

    Come on Adobe, 5 months old this bug.

    B
    brandospeed
    Participant
    December 31, 2012

    A bit off topic, but it's nice to see that a website with a good bit of clout is finally putting a little effort into keeping FW alive. Now that there is a serious need for "Ultra-Rapid Prototyping Tools," maybe people are starting to finally realize that 80 million filter choices slow you down more than help you get the job done!

    https://tutsplus.com/2012/12/photoshop-or-fireworks/

    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