Re: FEBE 7.0beta7, CLEO 5.0beta2, and OPIE 3.0beta - bug rep

Chuck, see my responses inline.
If the errors aren't related to the problem I'm reporting I'm happy to ignore them. I don't see them unless I have the error console open.
Yes, they are GreaseMonkey scripts and it made sense to me that FEBE cannot back them up. As far as I know I have no control over their location. If FEBE cannot back them up I'm not too concerned - especially since it's not related to the problem in question.
I do have the Java Console checked in the Ignore list. Strangely, that dialog lists "Java Console-{6.0.22}" twice, instead of one 6.0.22 and one 6.0.17. I have disabled the 6.0.17 extension in the Addon Manager, FWIW.
Thanks for the link - I've removed that extension (which I had disabled, BTW). Removing it had no effect on the bug I'm reporting, however.
So, do you have any ideas how to determine what's actually wrong? I will do what I can to provide further information about the problem, as long as it doesn't require administrative access to my workstation (which I do not have). I will also try to recreate the problem at home, but I'm running FF5 on Windows 7 there so the conditions may be different.
cbaker_admin wrote:This is the first report I've seen describing the FEBE options window behavior. I'm not sure what is causing the problem, but ...
The "Error: attempt to run compile-and-go script on a cleared scope" error is a known Firefox bug. I have seen it occur in my installation several times but so far it doesn't seem to really effect anything that I can see.
If the errors aren't related to the problem I'm reporting I'm happy to ignore them. I don't see them unless I have the error console open.
The extensions that FEBE cannot get information about (i.e., RockmastersiGoogleSidebarCollapse{}.xpi, ctc.) are GreaseMonkey scripts, aren't they? These scripts are not true extensions and FEBE cannot back them up as such. Is it possible to have these scripts stored somewhere else than the profile/extensions directory? That way FEBE can back them up as a user-defined backup entry instead of attempting to rebuild them as normal, installable, extension xpis.
Yes, they are GreaseMonkey scripts and it made sense to me that FEBE cannot back them up. As far as I know I have no control over their location. If FEBE cannot back them up I'm not too concerned - especially since it's not related to the problem in question.
It looks like you have two versions of Java Console installed. These are proxy extensions and cannot be backed up as regular extensions. If they appear in FEBE Options > What to backup > Ignore list, you should have them checked off.
I do have the Java Console checked in the Ignore list. Strangely, that dialog lists "Java Console-{6.0.22}" twice, instead of one 6.0.22 and one 6.0.17. I have disabled the 6.0.17 extension in the Addon Manager, FWIW.
You have Microsoft .NET Framework Assistant installed. Do you really want or need it? See this article.
Thanks for the link - I've removed that extension (which I had disabled, BTW). Removing it had no effect on the bug I'm reporting, however.
So, do you have any ideas how to determine what's actually wrong? I will do what I can to provide further information about the problem, as long as it doesn't require administrative access to my workstation (which I do not have). I will also try to recreate the problem at home, but I'm running FF5 on Windows 7 there so the conditions may be different.