Known Participant

Question

issue with OSX 10.8... Could Not Save File

Forum|Forum|13 years ago
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.

Show previous replies

Z

ZebraMark

Participating Frequently

I've been seeing this bug for YEARS. The main problem is this: no one at Adobe actually seems to USE their products on an intensive daily basis. There are those of us who use them 8 hours a day and know the flaws inside and out. They won't listen to us.

M

m2tno

Participating Frequently

I started having this problem when I upgraded to OS X 10.8. Annoying yes, detrimental to getting work done no.

What I have discovered is that if I bypass the normally (cmd, Shift, X) image preview panel before exporting, by just going to File-Export (cmd, Shift, R) I do not get the error message. That leads me to believe there is an error in the preview panel.

SteddyShots

Known Participant

It's been 6 months, and 5605 people have viewed this (presumably all with the same issue) and their are other threads on the forums with the same issue and so far we have only heard from Adobe twice saying they are aware of it.

This isn't something minor each and every day when exporting files I see the error all day long.

How long can they get away without fixing this? Another 6 months? Adobe Cloud was suppose to mean faster fixes but still no resolution so I think we as the community need to take action. Twitter helps but we need to do things that people can see easier such as posting to Adobe Fireworks Facebook page, building a website such as "couldnotsavethefile.com" with a screenshot of the error, links to all these forum posts about it, a tweet button that users can click if they are having the issue that will automatically tweet to @adobefireworks and @adobecare with a prewritten message and hash tag such as #fixfireworks. In the off chance it get's picked up by HackerNews then you can be sure that this six month bug will be resolved over night and available in the next update.

It's unfortunate we need to spend so much time and work to get Adobe to resolve an issue but simply waiting is no longer an option.

T

Tom Nunamaker

Participant

I saw two updates to Adobe products today. Naturally I hoped one would be for Fireworks, but alas, no. PhotoShop was updated. I can't remember when the last time Fireworks had an update.

Maybe it's time to admit Fireworks is not a priority at Adobe and start learning PhotoShop. Too bad as I like working with Fireworks much better for the web.

M

Mastov1

Participating Frequently

Or perhaps just start giving money to Sketch.

J

jeffro_69

Participant

My entire design group has the same issue since we upgraded to CS6 and Mountain Lion. It's annoying enough that we may have to dump Fireworks and start using Photoshop for everything. Fireworks seems to have become Adobe's neglected child.

J

jimct101

Participant

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

AllDayDev2

Community Manager

Sorry for the frustration, folks. The Fireworks team is actively working on a resolution to solve this issue for you; however, we do not yet know when the fix will be released.

F

fosforuscw

Participating Frequently

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.

SteddyShots

Known Participant

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.

M

Mastov1

Participating Frequently

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.

groove25

Inspiring

A possible solution to this problem was suggested by another Fireworks user in the following forum thread:

http://forums.adobe.com/message/4833573#4833573

T

TheOriginalDJD

Participant

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.

J

johnnie_n

Participating Frequently

Guys, you're not doing yourselves any favors by hijacking this thread to report issues that are kinda like this one but kinda not.

If you don't see a thread with your exact issue, start a new one -- I'd be willing to bet you'll get a better response from Adobe since this thread is about a very specific (and now known) issue... and your issues are different. And it looks like more serious. :-)

C

CLUNA3

Participating Frequently

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

B

bc80921

Participant

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

.