Yummy Software

had a strange occurrence a little while ago when I was editing a file remotely with BBEdit and YummyFTP. When I tried to save my changes YummyFTP reported an error I've never seen before and I'm kicking myself for not taking a screenshot or writing down the  message. It was something like "YummyFTP could not fill that request due to an error. Please restart YummyFTP and try again" - but I am paraphrasing.

I did so, and now when I try to upload an image (JPEG) with the transfer encoding set to Auto it seems to mangle the image when uploaded - it's all distorted and pixellated.

I tried uploading the image several times under different names and refreshing my browser, etc. to no avail. I also restarted YummyFTP several times. Finally I had to manually set the transfer encoding to Binary for the image to get uploaded correctly.

Any idea what's up?

Check the Suffix Mapping table entry for .jpg to see what the transfer encoding is set to. Maybe you changed it inadvertently?

heya JD :)

indeed the suffix mapping is set to ASCII for .jpg.  in fact, it seems EVERYTHING is set to ASCII  :o

any idea how that happened and is there a quick fix?

the only thing I did with suffix mapping was add .rb so that Ruby files could be opened by TextMate instead of BBEdit.

yet somehow all suffixes are now mapped to ASCII.

is there a way to reset suffix maps to "default"?

DUH!  ::)

i guess what I meant to ask is "is there a way to reset suffix maps to default OTHER THAN clicking on the big "DEFAULTS" button?  ;)

Is this an Intel Mac issue that nobody found? Out of all the beta testers I'd be really surprised if it's the case... but you never know.

Your only option is the Defaults button that you've already seen. This reverts everything to Factory Settings, which *should* mean that they are correct. Again, I can't test this out because I only have a PC here in the Internet cafe!! Let me know - if it's an Intel bug I'll fix it as soon as I return, which is this coming Thursday.

Thanks, and sorry for the trouble!!

-Jason

no worries mate :)

setting everything back to default did the trick. since doing so i haven't had any issues so it's quite possible I may have inadvertently pressed a key command or something to switch everything to ASCII.

thanks again.

Okie dokie :)

I'll check this out now I'm back. Thanks!

hey there - me again :)

there's definitely an issue whereby the transfer encodings seem to magically all get set to ASCII.  Over the past few days there have been at least 3 times I've had to go into the Suffix Mapping panel and click on the Defaults button in order for files to get uploaded/downloaded correctly. For example, I'll download a ZIP archive and when I try to unzip it reports an error. This is because YummyFTP downloaded it as ASCII. Same thing happens if I try to upload a TAR or GZIP archive onto my server and then try to uncompress them on the server - it reports an error because YummyFTP uploaded them as ASCII.

I'm running 1.5.1 on an Intel iMac (10.4.7).

thanks!

Really strange. I did take a look at this area, but I found nothing wrong. I haven't been able to reproduce it, nor have I had other reports of such behavior. Is there something you might be doing that triggers the problem, perhaps?

Does the problem disappear when you next launch Yummy FTP?

When it next happens, quit Yummy FTP then send me the Suffix Mapping file that is located in the Yummy FTP preferences folder. Maybe it will give me a clue.

Thanks!

ok will do.

the only thing I can think of is if there is a key command I'm pressing that automatically sets all suffix maps to ASCII. This would be different then the transfer encoding setting which always remains on "Automatic", instead it is some magical gremlin or key command that resets all suffix maps to ASCII.

There is no such key combination, so that's not it. I was more thinking along the lines of some specific chain of events that results in the behavior, although I appreciate that you've got better things to do than keep track of what you've been doing in Yummy FTP all day...

I'll have to wait until it happens again to you, but one thing to note is that the Suffix Mapping file I asked for will only be present in the Preferences folder if you have changed one or more of the Suffix Mapping entries. If you haven't then the file will be located inside the Yummy FTP package itself - it's this file which is used to reset to defaults. So, I assume that at some point you are changing/adding/removing the Suffix Mapping table. Correct?

No idea if this applies, but recently I (and one other person) had some really odd software issues that took forever to figure out. Had to do with applications writing to pref files... while not doing it. One of them had to do with entering a new parameter in the app GUI, quitting and finding it back to before the change. AND that pref files WAS being written to, time stamps proved that. FWIW

in terms of modifying the Suffix Mappings, I believe the only thing I did was add the extension for Ruby files (.rb) so that they could be opened with TextMate rather than my default editor, BBEdit. This was how you suggested I get around the lack of an "open in secondary editor" option. At the time I needed to do this because the Ruby plugin in BBEdit was specific to PPC and therefore any Ruby files opened in BBEdit on my Intel iMac had no syntax coloring, etc.

Since then BareBones has shared their beta of a built-in Ruby plugin that is Universal Binary, so the need to open Ruby files in TextMate is no longer required. So, if I had to, I suppose I could delete the SuffixMapping file even though I have clicked on the "Defaults" button. Maybe there is something going on with how the user specific SuffixMapping file is getting read/written.

paulc. did the issues you described happen on Intel Macs or PPC Macs?

tu11ym0n - Thanks for the additional information, and the Suffix Mapping file you sent me via email. I'll be looking into this today - sorry for the delay.

paulc - That's interesting about the prefs issues, but I don't think it applies here. I think the bug you're referring to affects the API built into OS X for saving preferences - that API isn't used for the Suffix Mapping table file. Thanks for raising it as a possible cause, though.

PPC... indeed, I thought it MIGHT apply only in the most general sense. Plus, it was a kind of "in the front of the old brain" thing.

This has now been fixed and will be included in an update as soon as possible.

The bug is Intel-specific and would occur if you had made additions or alterations to the Suffix Mapping table.

Thanks to tu11ym0n for his patience :)