SillyDog701

by **RB2D2** » Sat 17 Oct, 2009 1:00 pm

I have SeaMonkey 1.1.18 installed and notice that the two buttons, Google Search and I'm Feeling Lucky, on the Google search page are missing. Anyone have an idea why?

They display in Firefox.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

by **Amrad** » Sat 17 Oct, 2009 5:22 pm

RB2D2 wrote:I have SeaMonkey 1.1.18 installed and notice that the two buttons, Google Search and I'm Feeling Lucky, on the Google search page are missing. Anyone have an idea why?

They display in Firefox.

I'm also using SeaMonkey 1.1.18 and the Google buttons display OK for me!

Regards,

Dave.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090825 Firefox/2.0.0.20 SeaMonkey/1.1.18

by **RB2D2** » Sat 17 Oct, 2009 7:52 pm

That is so strange. The buttons display in Firefox and Internet Explorer but not in Seamonkey or Opera. This is what I see in SM and O:

http://img4.imageshack.us/i/screenshot025jf.jpg/

:roll:

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

by **PaulD** » Sat 17 Oct, 2009 8:47 pm

This is an interesting question.
A comparison of the Page Sources under Firefox 3.0.14 and Netscape 7.2 (which renders OK) discloses significant differences, not only in the code for these buttons but also before and after them. (I don't have SeaMonkey.)

Since you are having a problem, and others have not reported it, there may be some setting in about:config that affects this. (But RB2D2's report is interesting.)
(Edit addition: Just noticed that RB2D2 also is NT 5.2. So this may be a Google bug.)

Is the Google 'Advanced Search' page OK?

Test by creating a new Profile and see what happens.

May be irrelevant: Your User Agent is NT 5.2. According to this (Mozilla) and this Microsoft document [ http://msdn.microsoft.com/en-us/library/ms537503(VS.85).aspx ], you are on either Server 2003 or XP x64.

Note: The BBCode translator here wrongly truncates the link before the left parenthesis of the VS.85 portion of the page address.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14

by **Amrad** » Sat 17 Oct, 2009 8:54 pm

PaulD wrote:Is the Google 'Advanced Search' page OK?

I've tried both the 'normal' and 'advanced' Google search pages and both display the buttons correctly in SeaMonkey 1.1.18.

Regards,

Dave.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090825 Firefox/2.0.0.20 SeaMonkey/1.1.18

by **RB2D2** » Sat 17 Oct, 2009 10:17 pm

PaulD, I changed profiles and now the buttons display. I'm running XP 64 bit

BTW, the buttons still do not display in Opera, I just updated it and that didn't help.

How can I fix my old profile?

:cry:

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

by **Antony** » Sun 18 Oct, 2009 2:57 am

With Safari, I don't see the two buttons. With Firefox and Camino, I can still see those two buttons.

UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3

by **PaulD** » Sun 18 Oct, 2009 6:02 pm

"How can I fix my old profile?"
Plan A
- If you must fix your old profile:
---- The following assumes that the problem lies ONLY in the prefs.js. If other files also are implicated then this won't suffice. Do all except the last step (testing) with SM closed.
-- Backup (copy elsewhere) the entire existing profile as a fallback safety.
-- Extract (copy to a scratch folder) your existing prefs.js, rename it to bad.js
-- Rename the existing prefs.js to prefsold.js.
-- Extract (copy to the scratch folder) your new/good prefs.js, rename it to good.js
-- In a Command Prompt, navigate to the scratch folder;
--- FC good.js bad.js > gb.js
---- Use an editor (Notepad is adequate) for the following. It will be easier if you print out all 3 of these files (bad.js, good.js, gb.js) and visually review them. Optionally, open multiple instances of Notepad and do your reviews on-screen.
-- After orienting yourself, modify (Copy/Paste, or whatever is easiest) bad.js so that the statements that are different match the 'good' statements. Allow for the fact that there are differences in files' paths.
-- Review any new/additional statements in good.js.
-- Copy bad.js to the existing Profile; rename it to prefs.js.
-- Test. If unsatisfactory, either go back to the scratch folder and make additional changes, or go to Plan B --- after deleting prefs.js (the modified bad.js) and renaming prefsold.js to prefs.js
-- If things go too awry, copy back the backup copy made at the beginning and start over.

Plan B
-- Use these instructions.

Plan C - When all through, remember to clear all temporary / scratch folders and files.

Final Observation: It is interesting that in Opera and Safari, and for at least one instance of SeaMonkey on XP x64, there is a problem. It is not clear if the problem is in Google or in the browsers. Or both.

Questions for RB2D2, Amrad, and Antony:
Your browsers that 'fail' here with Google - focusing on the profiles for the releases that you are on - were these profiles used with previous releases of the browsers, or were the profiles newly created after the latest release? And was Google 'OK' on the previous release, if you can recall, or did the subject buttons evaporate only with the new release?

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14

by **RB2D2** » Sun 18 Oct, 2009 8:17 pm

Questions for RB2D2, Amrad, and Antony:
Your browsers that 'fail' here with Google - focusing on the profiles for the releases that you are on - were these profiles used with previous releases of the browsers, or were the profiles newly created after the latest release? And was Google 'OK' on the previous release, if you can recall, or did the subject buttons evaporate only with the new release?

The Google buttons were displaying with the new release all along and just disappeared in the last couple days or so.

What I did was create a new Profile, delete all the content of the folder and pasted in the contents of the old Profile folder I had backed up a couple of weeks ago. Works perfect! There were only a few bookmarks missing (that I'm aware of) and I replaced those.

I'm good to go!

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

by **Amrad** » Sun 18 Oct, 2009 10:00 pm

PaulD wrote:Questions for RB2D2, Amrad, and Antony:
Your browsers that 'fail' here with Google...

My browser did not 'fail' with Google!

...- focusing on the profiles for the releases that you are on - were these profiles used with previous releases of the browsers, or were the profiles newly created after the latest release? And was Google 'OK' on the previous release, if you can recall, or did the subject buttons evaporate only with the new release?

My profile is the same one that I have used for all releases of SeaMonkey (and the Mozilla Suite) and I have never had a problem with the Google buttons not displaying!

Regards,

Dave.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090825 Like Firefox/2.0.0.20 SeaMonkey/1.1.18

by **PaulD** » Mon 19 Oct, 2009 11:09 am

Dave, Thank you. Where I was going with that question was to discern, if possible, if there was some problem with a profile that was a carry-over (from a previous install) rather than a new profile. You have an 'old' profile, with no problem; and now the Rose indicates that the profile / prefs.js 'spontaneously' corrupted.

I'm still curious as to what the prefs difference was that caused this. And what changed it.

Yet to be analyzed is why Opera and Safari exhibit this behavior.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14

by **RB2D2** » Mon 19 Oct, 2009 11:34 am

Only thing I can possibly think of might have caused it is I used CCleaner a few days ago and CCleaner has caused problems with Seamonkey for me before a long time ago. However I use CCleaner on a more or less regular bases and it hasn't caused any problems for me in months

Google site is still broken in Opera and I've enabled everything I can think of. If I check Show active frame border then all the links (everything in blue letters) disappear, the only things left on the page are the Google logo and the search slot. As I already mentioned I was running an older version of Opera day before yesterday and I installed the newest version and Google page remained broken.

http://img24.imageshack.us/i/screenshot022pg.jpg/

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18

by **Fulvio** » Mon 19 Oct, 2009 11:56 am

The buttons are there for Firefox and Seamonkey1.1.8 (I don't have Opera), but does it matter? I can't think of any good reason to opt for the feel lucky button, if a Search works.

UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14

SillyDog701

Google buttons missing

Google buttons missing

Re: Google buttons missing

Re: Google buttons missing

Re: Google buttons missing

Who is online