On 7/17/2011 11:40 PM, David E. Ross wrote:
On 7/17/11 5:04 PM, Justin Wood (Callek) wrote:
On 7/17/2011 3:00 PM, David E. Ross wrote:
On 7/17/11 9:31 AM, Justin Wood (Callek) wrote:
On 7/17/2011 11:32 AM, David E. Ross wrote:
On 7/16/11 7:19 PM, Justin Wood (Callek) wrote:
On 7/16/2011 2:12 PM, David E. Ross wrote:
I have four profiles. For some reason, one of the profiles still has
SeaMonkey Default Theme 2.1. The other three have SeaMonkey Default
Theme 2.2.
How can I update the one profile? I cannot find any SeaMonkey Default
Theme at AMO.
It sounds like you may have following the instructions of one or two
people on this newsgroup back when we had an issue with the
theme/toolkit design in our early 2.1 releases (rc's) to which I tried
to contest as soon as I saw them.
Anyway, it sounds like you (or someone) manually installed that 2.1
version of our theme, which installed it into your profile. The best
solution I can offer is to "uninstall" the theme from the profile
manager (say, by switching to Modern first), THEN restart and you should
be able to switch back to the correct (2.2) version.
I followed your second paragraph and got SeaMonkey Default Theme 2.2.
But I can't enable it. In Add-ons Manager, neither Default nor Modern
show Enable or Disable buttons. When I go to the SeaMonkey menu bar and
select [View> Apply Theme> SeaMonkey Default Theme], that does not
stick.
I tried starting SeaMonkey in Safe Mode and then selecting [View> Apply
Theme> SeaMonkey Default Theme] from the menu bar. I got a dialogue
popup saying "These changes will take effect when you restart
SeaMonkey." I selected the Restart Now button on the popup.
I'm still stuck in the Modern theme, which I think is ugly. This is
worse than having the wrong version of Default.
Now a *guess*... start/run 2.1 (switch to default theme if you can).
then close and then start/run 2.2 again. Things *should* be ok.
Failing that I'll need help to diagnose/fix you.
I no longer had SM 2.1 installed.
I installed SM 2.1 from my own archive into a new location. When I
opened SM 2.1, it was using the Modern theme. At Add-ons Manager, I saw
both Default and Modern themes, both v.2.1. There was no Disable button
for Modern or Enable button for Default. I removed SM 2.1.
I then installed SM 2.1 over SM 2.2. The results were the same. I
removed SM 2.1.
Note: I have four profiles. This problem appears only in my "primary"
profile, the profile that I use the most.
When you *select* the Default (primary) theme you should have an enable
button for it, if you don't sounds quite odd. perhaps we can/should
check the error console for any messages that can shed some light here.
I have 4 information entries, 4 warnings, and 1 error. The information
entries are all from using the Preserve Download Modification Timestamp
extension. The 4 warnings are all from viewing a Web page that my
daughter is updating.
The error entry is as follows:
Error: [Exception... "Component returned failure code:
0x80520012 (NS_ERROR_FILE_NOT_FOUND)
[nsIStyleSheetService.loadAndRegisterSheet]" nsresult:
"0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
chrome://adblockplus-modules/content/ElemHide.jsm ::
<TOP_LEVEL> :: line 284" data: no]
Source File: chrome://adblockplus-modules/content/ElemHide.jsm
Line: 289
I believe this is related to the operation of AdBlock Plus while viewing
a Web page.
It appears that nothing in my error log relates to attempts to enable
the Default theme.
I actually enabled the Default theme. I edited the bottom of file
extensions.ini to change
[ThemeDirs]
Extension0=C:\SeaMonkey2\extensions
\[email protected]
to be
[ThemeDirs]
Extension0=C:\SeaMonkey2\extensions\{972ce4c6-7e08-4474-
a285-3208198ce6fd}.xpi
While this caused Default to replace Modern as the theme used by
SeaMonkey, it did not setup Enable or Disable buttons on the themes when
viewed from the Add-ons Manager. Furthermore, going to [View> Apply
Theme> SeaMonkey Default Theme] on the SeaMonkey Menu bar still does
not allow themes to be switched.
THAT sounds scary again. its probably related to some sort of hack you
did in your profile, it sounds like the current state of the theme is
out of sync with what the addon manager (and its data) expects,
[extensions.sqlite]
We're in the "let me guess" rather than even having an informed thought
so I'd rather not play guessing games for now...
But I would be willing to place money on a bet that its from something
that was done on your end manually rather than a real bug in the app (2.2)
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
