[Project_owners] Re: extensions/{GUID} folder erased on install

Brian Kennelly mozdev at bkennelly.net
Sun Jan 1 11:07:15 EST 2006


The logical problem is that, by the time the new release can check for 
the existence of the files, they will have been deleted by the brain 
dead installation code. 

It is just one of many missteps made in the extension manager in Mozilla 
Lite.


Eric H. Jung wrote:
> Carl,
>
> In your next release, check for the existence of the file in the
> profile directory. If it's there, simply move it up one level. Why so
> much anger? Only a few lines of code and your users will respect you
> once again... :)
>
> --- Carl <carlpny at yahoo.com> wrote:
>
>   
>> Alright. I'm glad at least I know that I'm not going
>> crazy.  I based my code off an existing (working)
>> extension, which is also broken now, so I had no idea
>> it wasn't "recommended practice" to store data in this
>> location.  
>>
>> I realize I'm venting in the wrong place, but if
>> you've already made the design choice to allow for
>> non-volatile data to be stored in these directories,
>> it is pretty irresponsible to come up with this
>> blatant hack, screw up many people's code and make us
>> look like the fools for it to our own users.
>>
>> If anyone else feels like venting, it might help make
>> me feel better :-)
>>
>> Carl
>>
>>
>> --- project_owners-request at mozdev.org wrote:
>>
>>     
>>> Date: Sun, 01 Jan 2006 12:26:40 +0800
>>> From: Philip Chee <philip.chee at gmail.com>
>>> Subject: Re: [Project_owners] extensions/{GUID}
>>> folder erased on
>>> 	install
>>> To: project_owners at mozdev.org
>>> Message-ID: <dp7lkj$nrr$1 at mozdev.mozdev.org>
>>> Content-Type: text/plain; charset=ISO-8859-1
>>>
>>> On Sat, 31 Dec 2005 16:17:35 -0800 (PST), Carl
>>> wrote:
>>>       
>>>> Fellow Mozdev Project Gods and Godesses,
>>>>         
>>>> I asked this a while ago and didn't get any
>>>>         
>>> answers.  This is a serious problem for me.
>>>       
>>>> The extensions/{GUID} folder is cleared out when
>>>>         
>>> my extension is installed.
>>>       
>>>> This only happens in Firefox 1.5.
>>>>         
>>> I believe that this was done by design during the
>>> rewrite of the
>>> EM/xpinstall code for Firefox 1.5. The extension
>>> installation procedure is
>>> now staged with a fallback at each stage and
>>> significantly more error
>>> checking. The reason that all files in the
>>> extensions/{GUID} directory are
>>> deleted was that some extensions would leave behind
>>> old files in those
>>> directories that they shouldn't. When a newer
>>> version of the extension was
>>> installed, older versions of these files were picked
>>> up causing mysterious
>>> problems and js errors in these extensions. It was
>>> believed that a clean
>>> slate would eliminate these hard to diagnose
>>> problems.
>>>
>>>       
>>>> Am I just going to have to ignore the fact that i
>>>>         
>>> worked hard to make my
>>>       
>>>> extension's settings/data upwards compatible?
>>>>         
>>> Firefox anhilates these files.
>>>
>>>       
>>>> Does anyone know if it is possible that i am just
>>>>         
>>> doing something wrong? 
>>>
>>> Yes, you should have put your persistent data in the
>>> profile or
>>> profile/chrome directory. Mnheny, Launchy, CTB and
>>> most other extensions
>>> that I have investigated do it this way.
>>>
>>>       
>>>> Is there at least anyone else that has this
>>>>         
>>> problem and is angry about it?
>>>
>>> No. It's just you not following recommended
>>> practices.
>>>
>>>       
>>>> Thanks,
>>>> Carl Nygaard
>>>>         
>>> Phil
>>> -- 
>>> Philip Chee <philip at aleytys.pc.my>,
>>> <philip.chee at gmail.com>
>>> http://flashblock.mozdev.org/
>>> Guard us from the she-wolf and the wolf, and guard
>>> us from the thief,
>>> oh Night, and so be good for us to pass.
>>> [ ]Don't take life too seriously, you won't get out
>>> alive.
>>> * TagZilla 0.059
>>>
>>> ------------------------------
>>>
>>> Message: 7
>>> Date: Sat, 31 Dec 2005 22:50:10 -0800
>>> From: Jonathan Yaniv <yaniv.jonathan at gmail.com>
>>> Subject: Re: [Project_owners] two-input prompt
>>> To: Mozdev Project Owners List
>>> <project_owners at mozdev.org>
>>> Message-ID:
>>>
>>>
>>>       
>> <1d557dc50512312250n59415575l7a658a0906a34e7f at mail.gmail.com>
>>     
>>> Content-Type: text/plain; charset="windows-1252"
>>>
>>> hmm interesting
>>>
>>> If you can change the passwd char values not to be
>>> ***** maybe like XXXXX
>>> that would be cool
>>>
>>> Extention anyone??
>>>
>>> On 12/31/05, Eric H. Jung <grimholtz at yahoo.com>
>>> wrote:
>>>       
>>>> Sure, as long as the second input doesn't *have*
>>>>         
>>> to be a password field
>>>       
>>>> (hidden by ****)
>>>>
>>>> --- Didier Ernotte <didier at ernotte.com> wrote:
>>>>
>>>>         
>>>>> Like prompt for User/password ?
>>>>>
>>>>> --- "Eric H. Jung" <grimholtz at yahoo.com> wrote:
>>>>>
>>>>>           
>>>>>> Hi,
>>>>>>
>>>>>> I remember seeing a XUL file in the Firefox
>>>>>>             
>>> source which permitted
>>>       
>>>>>> prompting of two arbitrary items (through
>>>>>>             
>>> <textbox/> elements). The
>>>       
>>>>>> text on the dialog was configurable through
>>>>>>             
>>> openDialog()
>>>       
>>>>> parameters.
>>>>>           
>>>>>> Now I'm trying to find that XUL and am having
>>>>>>             
>>> a difficult time.
>>>       
>>>>>> Anyone
>>>>>> know the file? I want to get rid of equivalent
>>>>>>             
>>> code in my
>>>       
>>>>> extension.
>>>>>           
>>>>>> Thanks,
>>>>>> Eric Jung
>>>>>>
>>>>>>
>>>>>>
>>>>>> __________________________________________
>>>>>> Yahoo! DSL � Something to write home about.
>>>>>> Just $16.99/mo. or less.
>>>>>> dsl.yahoo.com
>>>>>>
>>>>>>
>>>>>>             
>>> _______________________________________________
>>>       
>>>>>> Project_owners mailing list
>>>>>> Project_owners at mozdev.org
>>>>>>
>>>>>>             
>>> http://mozdev.org/mailman/listinfo/project_owners
>>>       
>>>>> _______________________________________________
>>>>> Project_owners mailing list
>>>>> Project_owners at mozdev.org
>>>>>
>>>>>           
>>> http://mozdev.org/mailman/listinfo/project_owners
>>>       
>>>>
>>>>
>>>> __________________________________________
>>>> Yahoo! DSL � Something to write home about.
>>>> Just $16.99/mo. or less.
>>>> dsl.yahoo.com
>>>>
>>>> _______________________________________________
>>>> Project_owners mailing list
>>>> Project_owners at mozdev.org
>>>> http://mozdev.org/mailman/listinfo/project_owners
>>>>
>>>>         
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL:
>>>
>>>       
> http://mozdev.org/pipermail/project_owners/attachments/20051231/bf1a65c6/attachment-0001.htm
>   
>>> ------------------------------
>>>
>>> Message: 8
>>> Date: Sat, 31 Dec 2005 22:50:57 -0800
>>> From: Jonathan Yaniv <yaniv.jonathan at gmail.com>
>>> Subject: Re: [Project_owners] extensions/{GUID}
>>> folder erased on
>>> 	install
>>> To: Mozdev Project Owners List
>>> <project_owners at mozdev.org>
>>> Message-ID:
>>>
>>>
>>>       
>> <1d557dc50512312250i763e48depce302e400c132b33 at mail.gmail.com>
>>     
>>> Content-Type: text/plain; charset="iso-8859-1"
>>>
>>> Happened to me as well
>>>
>>> On 12/31/05, Philip Chee <philip.chee at gmail.com>
>>> wrote:
>>>       
>>>> On Sat, 31 Dec 2005 16:17:35 -0800 (PST), Carl
>>>>         
>>> wrote:
>>>       
>>>>> Fellow Mozdev Project Gods and Godesses,
>>>>>           
>>>>> I asked this a while ago and didn't get any
>>>>>           
>>> answers.  This is a serious
>>>       
>>>> problem for me.
>>>>         
>>>>> The extensions/{GUID} folder is cleared out when
>>>>>           
>>> my extension is
>>>       
>>>> installed.
>>>>         
>>>>> This only happens in Firefox 1.5.
>>>>>           
>>>> I believe that this was done by design during the
>>>>         
>>> rewrite of the
>>>       
>>>> EM/xpinstall code for Firefox 1.5. The extension
>>>>         
>>> installation procedure is
>>>       
>>>> now staged with a fallback at each stage and
>>>>         
>>> significantly more error
>>>       
>>>> checking. The reason that all files in the
>>>>         
>>> extensions/{GUID} directory are
>>>       
>>>> deleted was that some extensions would leave
>>>>         
>>> behind old files in those
>>>       
>>>> directories that they shouldn't. When a newer
>>>>         
>>> version of the extension was
>>>       
>>>> installed, older versions of these files were
>>>>         
>>> picked up causing mysterious
>>>       
>>>> problems and js errors in these extensions. It was
>>>>         
>>> believed that a clean
>>>       
>>>> slate would eliminate these hard to diagnose
>>>>         
>>> problems.
>>>       
>>>>> Am I just going to have to ignore the fact that
>>>>>           
>>> i worked hard to make my
>>>       
>>>>> extension's settings/data upwards compatible?
>>>>>           
>>> Firefox anhilates these
>>>       
>>>> files.
>>>>
>>>>         
>>>>> Does anyone know if it is possible that i am
>>>>>           
>>> just doing something wrong?
>>>       
>>>> Yes, you should have put your persistent data in
>>>>         
>>> the profile or
>>>       
>>>> profile/chrome directory. Mnheny, Launchy, CTB and
>>>>         
>>> most other extensions
>>>       
>>>> that I have investigated do it this way.
>>>>
>>>>         
>>>>> Is there at least anyone else that has this
>>>>>           
>>> problem and is angry about
>>>       
>>>> it?
>>>>
>>>> No. It's just you not following recommended
>>>>         
>>> practices.
>>>       
>>>>> Thanks,
>>>>> Carl Nygaard
>>>>>           
>>>> Phil
>>>>         




More information about the Project_owners mailing list