530163 - Save Page As command mangles name of source that contains near end of file Google Analytics lines including "urchin.js" such that SeaMonkey cannot find source

Status: RESOLVED DUPLICATE of bug 313683

(SeaMonkey :: Download & File Handling, defect)

Description

[Mike]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.0.15) Gecko/2009101600 Firefox/3.0.15
Build Identifier: SeaMonkey 2.0 downloaded, installed, and run on 11/19/2009 Thursday - 11/20/2009 Friday

Using the Save Page As command, and in contrast to SeaMonkey 1.1.18 which exhibits no problems, SeaMonkey 2.0 alters the name of the source, by adding to the end of the name:

 /urchin.js

Whereupon SeaMonkey 2.0 can no longer find the source and save it to whatever location you chose on your computer.

This does not happen with each webpage encountered, but typically it happens when the source of a webpage, includes in the last lines ... something about Google Analytics - EXAMPLE:

 - several lines -
 - then as the last lines -
</div>
<script src="fr.2390941_files/urchin.js" type="text/javascript"></script>
<script type="text/javascript">_uacct = "UA-2288668-1"; urchinTracker();</script>
</body>
</html>







Reproducible: Always

Steps to Reproduce:
1. Probably you should find webpages with Google Analytics urchin.js
2. Use SeaMonkey 2.0 Save Page As command
3.
Actual Results:  
You'll get a pop-down dialog window that explains that the source could not be found ... and of course it cannot, because the source name has been mangled:

  /urchin.js

added at end of source name.

Expected Results:  
See actual results.

Also, SeaMonkey 1.1.18 does not have the problem with any of the webpages that are a "challenge" for SeaMonkey 2.0.

Comment 1

[lenochod]

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3

It's works for me.

Which sites are they?

Can you try and reproduce with SeaMonkey v2.0a3 ?

Please try in Safe mode ( http://kb.mozillazine.org/Talk:Safe_Mode#Safe_Mode_in_SeaMonkey_2 ), or with a new profile ( http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile ).

Comment 2

[lenochod]

(In reply to comment #1)
> Can you try and reproduce with SeaMonkey v2.0a3 ?

Wrong version, please test in 2.0.3 version.

Comment 3

[Mike]

(In reply to comment #2)
> (In reply to comment #1)
> > Can you try and reproduce with SeaMonkey v2.0a3 ?
> 
> Wrong version, please test in 2.0.3 version.

Using version 2.0.3.  Fresh profile.  The "Save Page As" command has completely disappeared from the File menu.  "Save Page" is there, but no "Save Page As" command.

They should both be in the File menu at all times.  Also, the Preferences > Browser > Downloads ... settings region should inform the user, that the "Save Page As" command is "greyed out" in the File menu when the Preference "When saving a file" is set to "Always ask me where to save files".

Users of SeaMonkey 1.1.xx used to be able to set a default Downloads folder to which downloaded files were directed, such as installation files (Mac .dmg files, Mac .sit files, and PDF files --- and that job was distinguished from saving webpages.  Downloading files and saving webpages were two different jobs.

SeaMonkey 2.0.x makes them one type of job - all downloads - effectively eliminating the ability to have both a default downloads folder and saving webpages WITHOUT having to flip switches.

Comment 4

[Mike]

(In reply to comment #2)
> (In reply to comment #1)
> > Can you try and reproduce with SeaMonkey v2.0a3 ?
> 
> Wrong version, please test in 2.0.3 version.

Also, yes, the problem of the "urchin" error still exists ... but with a change.

The webpage is saved, but a "Download Error" pop-down window appears, stating:

  /Users/.../posts_files/urchin.js could not be saved, because the source file cound not be read.

So the error reports, but the webpage *was* saved to the directory of my choice.

Comment 5

[Mike]

(In reply to comment #2)
> (In reply to comment #1)
> > Can you try and reproduce with SeaMonkey v2.0a3 ?
> 
> Wrong version, please test in 2.0.3 version.


More errors - Save Page As (Web Page, complete):


Download Error

/.../sed_data/show_ads.js could not be saved, because the source file could not be read.



Download Error

/.../ga.js could not be saved, because the source file could not be read.




The treatment of saved webpages --- that has changed between SeaMonkey 1.1.xx and SeaMonkey 2.0.x.  I don't know what the code was, nor what it is now.  Worked great with version 1.1.xx, but not now.

Comment 6

[Philip Chee]

Without a specific page to test this on, this bug is effectively unreproducible. Mike please paste a URL in a comment here for a webpage where:

1. You get this problem consistently.
2. You get this problem even when starting SeaMonkey in safe mode (e.g. seamonkey.exe -safe-mode)

Comment 7

[Philip Chee]

User has sent me some email. I cannot reproduce on Win7.

Can you try the various solutions listed at:
http://kb.mozillazine.org/Source_file_could_not_be_read

It is possible that you or your ISP are having connectivity problems. Another possibility is that you are connecting to the internet via a firewall or proxy. Try by-passing these if you have any of these installed. For windows OS it might also be an anti-virus program

Comment 8

[Philip Chee]

Attachment: Screenshot 1 provided by reporter.

Comment 9

[Philip Chee]

Attachment: Screenshot 2

Comment 10

[Mike]

This is a SeaMonkey version 2.x.x and later, problem.

It is not a firewall problem.

It is not an IP address problem.

The problem is in the version 2.x.x code.

The problem WAS NOT(!) in the version 1.1.xx code.

Comment 11

[Mike]

As I wrote back on Nov. 20th, SeaMonkey 2.x.xx is ALTERING the name of the source, by incorrectly adding to the end of the name of the source, and so, the source, of course, cannot be found!

Comment 12

[Philip Chee]

OP emailed me to say that he fixed the errors by removing the following lines from his hosts file:

> 127.0.0.1     google-analytics.com
> 127.0.0.1     doubleclick.net
> 127.0.0.1     loomia.com
> 127.0.0.1     adbrite.com

> On the Mac, the "hosts" file is located here:
> /private/etc/hosts

> So SeaMonkey 2.0.x, for some reason in its newer code, stumbles over these
> references because the "hosts" file thwarted what SeaMonkey 2.0.x was trying
> to do, while SeaMonkey 1.1.xx did not stumble.