A mystery

Why is it that some can upload files with spaces in the filename to RootsWeb using the FileManager and others cannot? I, personally, have never had a problem, but lots of others, including some in authority, report problems doing this.

The experiment

Here is outlined a standardized procedure to test the parameters of this mystery and try to determine what it is that allows some to do this and others not. Folks are invited to try it and report their experiences to the FreePages Advanced mail list.

What you will need

1. A RootsWeb FreePages account
2. Some (little) knowledge of Windows files, WWW operation, the FileManager.
3. Ability to follow directions.
4. Ability to note anomalies and accurately report results.

The process

In brief, this is what will be done:

1. Create the file to be uploaded
2. Invoke FileManager
3. Upload the file
4. Verify the result
5. Report

Screenshots will be used to help you along. The steps have very detailed instructions to help those who are in unfamiliar territory. It may be useful to print this page for easy reference.

Here we go! (This should only take a few minutes.)

1. fig. 1

   Create the file to be uploaded
   First we must create a file with spaces in the name in a standardized way. Here is a process that has worked for me:
1. Find a clear space on your desktop. Position your mouse pointer there and right click.
   
2. In the context menu that gets displayed, you should see one entry named New.
1. Scroll down (using the down arrow on your keyboard), to the New item.
2. Select New (use the mouse, or the right arrow on your keyboard).
   
3. You should now see a secondary menu (fig.2) with an element txt File or something similar.
   
4. Select the Txt File element.
   
5. A file should be created right there on your Desktop: "New txt File.txt"
   

3. fig. 2

   Note that the new file (fig 2) is initially in Rename mode, allowing you an opportunity to rename it. Don't. Click elsewhere on the Desktop to deselect the new file.
4. Now, because the FM won't upload empty or null files, we must add a line to the new file using a text editor.
   

5. fig. 3

   Right click on the icon of the new file. This will bring up a context menu (fig 3) offering several possibilities for treating the new file. Depending on how your system is set up, you may see any (or all) of these choices which will do what we want:
1. Open with text editor
2. Edit
3. Open with >
   Select an editor from the choices, or Choose Program...
6. Add the single line "A line", and save and exit.
   


2. Invoke FileManager
   

   1. fig. 4

      From your browser, go to: http://freepages.rootsweb.com/fileman/
   2. If you are requested to log in, do so.
   3. For those who are squeamish about mucking about in their established website, let's select an unused Community in the first field near the top of the page (fig 4), just below the huge font instructions. I chose Folklore. The URL to reference this folder then becomes: http://freepages.folklore.rootsweb.com/~your-username
      
   4. Tick all the extensions listed: html, gif, jpg, other
      
   5. If the community is really empty, you should see no files displayed under Name, Last Modified and Size.
      
3. Upload the file
   

   1. fig. 5

      Scroll down to the File Upload Utility (fig 5).
   2. Un-tick the Convert filenames to lowercase
   3. Click the first Browse button and find the file created in step 1, above.
      

   4. fig. 6

      In the File Upload window (fig 6), navigate to your desktop. You should see the file there: "New txt File.txt", as created in step 1.
      
   5. Click the new file.

   6. fig. 7

      You should see the first upload field (fig 7) now filled in with the URL of the new file on your PC. You will probably have to scroll the field to the right to see the whole name.
   7. Click on Send Files.
      
4. Verify the result
   Immediately after you click Send Files, you should see the browser window refresh and the new file shown (fig 8) in place on your selected RW FreePages directory, complete with spaces in the name.
   

   fig. 8

5. Report
   It is important that all results be reported, successes as well as failures. Begin with
   1. The URL of the directory you tested with,
   2. your Windows system type and level, and
   3. your browser name and level -- and:
      
   4. Result:
      • Success can be simply reported with that one word.
        
      • Failure reporting should be accompanied by some details about how the failure manifested: Was there an error message? What was it?
        

 

Thank You!