Fetch Softworks

Fetch automatically appends ".html" (4 posts)

• Started 19 years ago by mdavis
• Latest reply 19 years ago from Jim Matthews

• mdavis Member

  We have a few users who have started to work with Fetch 4.0.3 under Mac OS X (10.3.4). They develop Web content with DreamWeaver, then upload it with Fetch. (FWIW, the FTP/Web server is running OpenVMS w/ HP's TCP/IP Services for OpenVMS.) The users often need to upload files with ".htmlx" suffixes. (The trailing "x" indicates to the Web server that the files need to be pre-processed for directives.) When these files are uploaded with drag-n-drop via Fetch, a ".html" suffix is appended, so we end up files like "index.htmlx.html". Apart from uploading each file separately with the "Put Files..." button, is there any other way around this behavior? This is behavior that did not occur under Mac OS 9.

  Posted 19 years ago #

• Jim Matthews Administrator

  Make sure that "Add Internet Config suffix to Raw Data uploads" is not checked in the Upload section of Fetch Preferences. That's the only reason I can think of for Fetch adding a .html suffix to a file. If that is not checked (or unchecking it does not fix the problem) my guess would be that DreamWeaver is adding the suffix.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 19 years ago #

• mdavis Member

  I discovered that these files are, in fact,
  named as *.htmlx.html by setting the Finder preferences to show all extensions. When Fetch transfers them, it's merely preserving the full filenames. While enabling the viewing of all extensions helps work out what's happening, I'm wondering if there's a way that Fetch could be made aware of the setting in the Finder for hiding/showing the extensions, and honoring this setting when it names the transferred file(s) on the remote side. For example, for a file named index.htmlx.html with extensions hidden, thus only visible in the Finder as index.htmlx, when Fetch transfers this file, it would name it index.htmlx, rather than index.htmlx.html.

  Posted 19 years ago #

• Jim Matthews Administrator

  Thanks for the suggestion. I don't think the Finder should ever hide extensions, and it certainly shouldn't show a file as having one extension when in fact it has another one. But I'll think about your suggestion.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 19 years ago #