User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:18.104.22.168) Gecko/20070222 SeaMonkey/1.1.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:22.214.171.124) Gecko/20070222 SeaMonkey/1.1.1 After upgrading to SeaMonkey 1.1.1 from v1.1, the bookmarks no longer work. All of the bookmarks and personal toolbars are still there and when I open the bookmark's properties, the information is still there and correct, but clicking on the bookmark doesn't do anything. I can copy the information from the bookmark's properties and paste it in the address window and then I can get to the site. Reproducible: Always Steps to Reproduce: 1. 2. 3. I don't know if this matters or not, but I'm running x64 XP. about:buildconfig Build platform target i586-pc-msvc Build tools Compiler Version Compiler flags $(CYGWIN_WRAPPER) cl 12.00.8804 -TC -nologo -W3 -Gy -Fd$(PDBFILE) $(CYGWIN_WRAPPER) cl 12.00.8804 -TP -nologo -W3 -Gy -Fd$(PDBFILE) Configure arguments --enable-application=suite --disable-tests --without-system-jpg --without-system-zlib --enable-extensions=default,tasks --enable-crypto --disable-debug --enable-optimize --enable-svg --enable-canvas
Do you see any error in the Error Console under Tools->Web Development->Error Console when clicking on a bookmark?
I get an error that says: Error: ns.getPref is not a function Source File: chrome://noscript/content/noscriptBM.js Line:31 I've also been getting the error when I move the cursor in this box by clicking with the mouse except the source file and line is different. Error: ns.getPref is not a function Source File: chrome://noscript/content/noscriptOverlay.js The 'j' at the end of the source files could be 'i'. I can't quite tell. In the error console, if I click on the second source file listed above, I also get the second error above on line 940 and 1043 and the first error on line 39. I did have a 3rd party program called No Script installed. It's listed on the Mozilla site. I saw the warning when installing the SeaMonkey upgrade that third party software would have to be re-installed. Will re-installing this program fix these problems? Maybe it wasn't totally un-installed.
Yes, you possible need to do that. Just install NoScript again and give feedback.
I re-Installed NoScript. I'm still getting a lot of errors. If I click on the NoScript icon at the bottom of the window, there are actually two sets of options shown - like it was installed twice. Before I re-installed NoScript, clicking on this icon did nothing, but the icon was still visible. In the error console, when I click on this icon, I get the error "Error: this_service has no properties, Source File: chrome://noscript/content/noscript.js, Line:39" Now when I click on a bookmark, I get the error "Error: too much recursion, Source File: Chrome://noscript/content/noscriptBM.js, Line: 4". Now, clicking the mouse cursor in different areas of this comment window doesn't cause a new error. ....Interesting. I opened a second window to try some things and now when I click on the NoScript icon, it seems to function normally (no second set of options) and appears to have remembered my old settings for which pages I will allow scripts on. Now when I click on a bookmark, I get the "too much recursion" error on line 31, same source file. If I actually click on the link to the source file, I get two more errors: "Error: redeclaration of const_noScript_flag, Source File: Chrome://noscript/content/noscriptOverlay.js, Line: 908", and "Error: document.getElementById("contentAreaContexMenu") has no properties, same source file, Line: 1043.
Ok, try renaming your chrome folder in your profile to chrome2 to get rid of this double options. See http://kb.mozillazine.org/Profile_folder#SeaMonkey for where your profile is. Note that Application Data is a hidden folder by default, so you possibly need to enable viewing of hidden files in Windows Explorer.
I renamed the Chrome folder to Chrome2 and now the bookmarks work and I no longer have two sets of options. Thanks for the help. I'll update if there are any more problems.
As there were not more comments, this seems to work for the reporter.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.