From ammofreak at eastlink.ca Sun Feb 1 16:26:37 2009 From: ammofreak at eastlink.ca (Derek Lloyd) Date: Sun, 01 Feb 2009 20:26:37 -0400 Subject: [Maf] posting Message-ID: <1233534397.4761.0.camel@derek-laptop> Hi: sending e-mail address in order to post on mozdev. Have a good day..... From pgaga at auracom.com Sun Feb 1 18:01:25 2009 From: pgaga at auracom.com (Philip Griffin-Allwood) Date: Sun, 01 Feb 2009 22:01:25 -0400 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: Sunday 01 February 2009 > Can you please try the save again and post the exact error message text, > as well as the copy of any other message appearing in the Error Console > after the save failed? > > Please try with the browser's standard save system, not the other > save components for the moment. I tried and here are the popup and error logs. I tired changing the temp folder variable and the errors were the same. Phil POPup: z:\tmp\maftemp\1233531637365_238\index.com%20-%20Passage%C2%A0Lookup:% 20John%203:16 could not be saved, because an unknown error occurred. Try saving to a different location. Error Console: Warning: Error in parsing value for property 'font'. Declaration dropped. Source File: http://www.biblegateway.com/includes/css/default.css Line: 7 Warning: Error in parsing value for property 'font'. Declaration dropped. Source File: http://www.biblegateway.com/includes/css/default.css Line: 7 Warning: Error in parsing value for property 'font'. Declaration dropped. Source File: http://www.biblegateway.com/includes/css/default.css Line: 7 Error: syntax error Source File: http://isapi60.wxbug.com/WxAlertISAPI/WxAlertIsapi.cgi?GetAlert60&Magic=160&ZipCode= Line: 1, Column: 1 Source Code: 160|86400| Error: syntax error Source File: http://isapi60.wxbug.com/WxAlertISAPI/WxAlertIsapi.cgi?GetAlert60&Magic=160&ZipCode= Line: 1, Column: 1 Source Code: 160|86400| From paolo.01.prg at amadzone.org Tue Feb 3 10:09:19 2009 From: paolo.01.prg at amadzone.org (Paolo Amadini) Date: Tue, 03 Feb 2009 19:09:19 +0100 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: <4988884F.2080102@amadzone.org> Philip Griffin-Allwood wrote: > Sunday 01 February 2009 > >> Can you please try the save again and post the exact error message text, >> as well as the copy of any other message appearing in the Error Console >> after the save failed? >> >> Please try with the browser's standard save system, not the other >> save components for the moment. > > I tried and here are the popup and error logs. I tired changing the > temp folder variable and the errors were the same. > > Phil > > POPup: > > z:\tmp\maftemp\1233531637365_238\index.com%20-%20Passage%C2%A0Lookup:% > 20John%203:16 could not be saved, because an unknown error occurred. > > Try saving to a different location. That's interesting. The file name in the message should have been something like "z:\tmp\maftemp\1233531637365_238\index.html". Do you have any other extension installed whose purpose is to let you save using the title of the page instead of the file name? I tested MAF only with the one named "Title Save", which is compatible, but similar extensions are likely to conflict with the save process of MAF. Please try to temporarily disable any such extension, or other extensions that you think may be the source of the conflict; if the problem disappears, let me know which extension caused it, and maybe I'll be able to make compatibility fixes in the next version of MAF. Thanks, Paolo From pgaga at auracom.com Tue Feb 3 20:21:10 2009 From: pgaga at auracom.com (Philip Griffin-Allwood) Date: Wed, 04 Feb 2009 00:21:10 -0400 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: Tuesday 03 February 2009 > Do you have any other extension installed whose purpose is to let you > save using the title of the page instead of the file name? I tested > MAF only with the one named "Title Save", which is compatible, but > similar extensions are likely to conflict with the save process of MAF. I have tested and cannot think of anything. For compatibility with ePDF I tried something a few years back. I thought it was Title Save, but it might have been File Title. Since I have updated my profile from Phoenix 0.2, there might be a setting artifact. My SaveAs gives the page title. > Please try to temporarily disable any such extension, or other > extensions that you think may be the source of the conflict; if the > problem disappears, let me know which extension caused it, and maybe > I'll be able to make compatibility fixes in the next version of MAF. I turned everything off but MAFF and still had the same result. I will try later with a clean profile. It is also possible that this is due to something specific to the OS/2 build. Phil From pgaga at auracom.com Thu Feb 5 15:02:00 2009 From: pgaga at auracom.com (Philip Griffin-Allwood) Date: Thu, 05 Feb 2009 19:02:00 -0400 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: Thursday 05 February 2009 > It is also possible that this is due to something specific to the OS/2 > build. I tested with a clean FF 3.0.6 install and clean profile except for MAFF 9. Same problem. Phil From paolo.01.prg at amadzone.org Fri Feb 6 11:38:16 2009 From: paolo.01.prg at amadzone.org (Paolo Amadini) Date: Fri, 06 Feb 2009 20:38:16 +0100 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: <498C91A8.2010806@amadzone.org> Philip Griffin-Allwood wrote: > Thursday 05 February 2009 > >> It is also possible that this is due to something specific to the OS/2 >> build. > > I tested with a clean FF 3.0.6 install and clean profile except for MAFF > 9. Same problem. I studied the browser's save code and found a convolute code path that may lead the browser to consider part of the page title as the default file extension to use (technically, this may happen if the URL has no file leaf name and the browser can't get the MIME information for the document's content type from the system). Even though I couldn't reproduce that condition on my system, I made a modification in the latest build to try and work around the problem. Please download MAF 0.9.1.0 from... http://downloads.mozdev.org/maf/maf-0.9.1.0-fx.xpi ...and let me know if that's it! This build also introduces better download error handling and reporting, and now only a single entry is created in the download manager when multiple tabs are saved. Regards, Paolo From grifwood at glinx.com Fri Feb 6 19:41:44 2009 From: grifwood at glinx.com (Philip Griffin-Allwood) Date: Fri, 06 Feb 2009 23:41:44 -0400 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: Friday, February 06, 2009 > I studied the browser's save code and found a convolute code path that > may lead the browser to consider part of the page title as the default > file extension to use (technically, this may happen if the URL has no > file leaf name and the browser can't get the MIME information for the > document's content type from the system). > > Even though I couldn't reproduce that condition on my system, I made a > modification in the latest build to try and work around the problem. I think OS/2 generated the issue and with earlier MAFF builds, it was only on OS X that the problem caused problems when the file was opened. > Please download MAF 0.9.1.0 from... > > http://downloads.mozdev.org/maf/maf-0.9.1.0-fx.xpi > > ...and let me know if that's it! Great timing this was my day for the none tab archive build. I built the archive under OS/2 and then tested opening it under WinXP, Win7beta, OS/2, OS X, and Ubuntu Linux. It opened properly. Initially I thought it was only working with save complete and not with standard save system. But then I notice that I had Title Save extension turned on. It was in conflict with the the standard save system. I turned it off and saving happened properly. > This build also introduces better download error handling and reporting, > and now only a single entry is created in the download manager when > multiple tabs are saved. So far it appears to work as advertised and desired. Phil From paolo.01.prg at amadzone.org Sat Feb 7 00:14:04 2009 From: paolo.01.prg at amadzone.org (Paolo Amadini) Date: Sat, 07 Feb 2009 09:14:04 +0100 Subject: [Maf] Maff 9 In-Reply-To: References: <20090126024355.GFMD1658.simmts5-srv.bellnexxia.net@simip10-ac.srvr.bell.ca> Message-ID: <498D42CC.7000800@amadzone.org> Philip Griffin-Allwood wrote: > So far it appears to work as advertised and desired. I'm glad to know that the new build works on all the platforms. Thank you very much for your testing efforts, they are very helpful! Best regards, Paolo From paolo.01.prg at amadzone.org Mon Feb 9 06:53:29 2009 From: paolo.01.prg at amadzone.org (Paolo Amadini) Date: Mon, 09 Feb 2009 15:53:29 +0100 Subject: [Maf] [ANN] MAF 0.9.1 released Message-ID: <49904369.4070404@amadzone.org> Hello, Mozilla Archive Format version 0.9.1 is now officially available for download at or through the Firefox Add-Ons website . Changes from 0.9.0 to 0.9.1: * Change: Now only one entry is created in the Download Manager for each save operation, even if multiple tabs are saved at once. * Change: Improved download error handling and reporting. * Change: More accurate download progress indication when archiving a single page using the browser's standard save system. * Fix: The Download Manager window could be restored incorrectly after a save operation was started. * Fix: MAF could create archives containing incorrect file names in particular conditions. This case was more common on OS/2. Regards, Paolo Amadini