I have the same problem with Fireworks CS5.5.

I've brought this thread to the attention of the Fireworks dev team. But please also file detail bug reports on the wishlist:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Bug reports are logged, and the more identical incidents they receive, the higher priority an issue can get.

Any updates on resolving this bug?

Exactly same problem here - it is very annoying.

I use CS6 and would love to have a fix.

I posted this same topic today. Sad to see that months later Adobe has not solved the problem.

+1

Same problem...

Hmm, still no solution? Moved yesterday to 10.8.2 and had the same error with CS5.5

I'd really like to see this fixed.  It's just annoying.  Can we just drop in a dummy file to replace the "missing file" that FW is looking for?

I just encountered this same problem. I did a File --> Image Preview, and when I hit save got the message:

"Could not save the file.

The file was not found."

Attached is a screenshot of the dialog.

This is very troublesome and undermines my faith in Fireworks.

I'm running Fireworks CS6, version 12.0.0.236 and OSX 10.8.2. I'm also submitting this to the detail bug report in that wishlist link https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

+1

Saving file after adding 10 pages, hangs upon saving CS5 OSX 10.8.2, and 1X corrupted the file.  I need to add 5 more pages.  Should I duplicate the file, delete the pages, use the master and create the last 5 pages separately. I am planning to export all 15 pages to dreamweaver. Any other solution?

+1

I get the same message when I try to open a file in Fireworks CS6 that I had done in CS5.  I get a popup saying that I need to update the font because it came from an older version.  If I try to change the font or leave it the same I get the same error

.

I too have received a similiar problem albeit with a slightly different error message.

As of right now I cannot save any files. So this makes the Fireworks 100% non-usable.

Has anyone received updates yet? Or gotten a similiar error message to mine "An error occured." as opposed to "The file was not found."?

Might finally be getting some help. I tweeted this multiple times and they finally responded. Get the Fireworks Dev team to notice by retweeting.

https://twitter.com/fybix/status/265453328362778625

Thanks for the link, but that solution is only for users who upgraded OSX after Fireworks was installed. That won't help those of us who installed Fireworks on a new Mac. I'm still having the issue -- surprised Adobe hasn't responded or fixed this yet.

That presents a pretty big unknown. What if all my files are in the fw.png format? I have a website I'm working on with upwards of 30 fw.png files? Can these be migrated to photoshop? I really hope we're not just dropped. It's things like this that make someone hesitant to invest in a certain app for their workflow, because later they'll get no support. What do they expect us to do? Go back in time and use another program?

heavymark wrote:

 

Exact same issue. Been happening for months. I'm also using the latest version from Creative Cloud on a brand new retina mac.

 

The app is hardly useable due to the Retina issue and with no promise that it will ever be updated for Retina I assume the reason Adobe hasn't fixed this export bug yet is because they are A) abandoning the software rather than updating it to retina and carbon, and focus on photoshop B) they are near release of a completely new version with retina, carbon, etc like there new apps such as Reflow and they figure they would rather devote time to the new version that update the bugs of the current version.

 

I recommend everyone retweet this: https://twitter.com/fybix/status/265453328362778625 and post about this bug to all their facebook properties. It's sad that we have to revert to that but whether it be adobe or your cable company, they only way to get things resolved is to scream for everyone to hear.

Glad to know this is only an "annoyance."  Sure seems like a strange thing for Adobe.  If this were a Microsoft thing, I'd brush it off as business-as-usual.

https://twitter.com/fybix/status/275227943666585600 ReTweeter. I called a few times too and the most I got was their department has been notified. I'm almost certian a small patch could fix this issue.

Suggest we start motivating Adobe a little by spreading the word a little further about this on Twitter. Really is shameful how long they are taking to address this issue... #fixfireworks @Adobe_Care @AdobeFireworks