为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

how do i get rid of "read plusone.google.com

  • 6 个回答
  • 4 人有此问题
  • 2 次查看
  • 最后回复者为 johnpen

more options

more and more websites are not fully loading because of the line "read plusone.google.com" repeatedly

more and more websites are not fully loading because of the line "read plusone.google.com" repeatedly

所有回复 (6)

more options

Sounds like those sites embed the Google +1 button, but that the script which displays the button isn't loading as quickly as it should.

When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.

1. Bypass Firefox's Cache

Use Ctrl+Shift+r to reload the page fresh from the server. Any difference? If not...

2. Clear Firefox's Cache Completely

orange Firefox button or Tools menu > Options > Advanced

On the Network mini-tab > Cached Web Content : "Clear Now"

3. If needed, remove your google.com cookies in this dialog

While viewing a page on google.com, right-click and choose View Page Info > Security > "View Cookies"

Then try reloading the page. Does that help?

more options

Thanks For your solution, but it didn't work. I have encountered another three websites that do this - the problem is with Firefox and not with websites. As i said - it only started with the update from Firefox 13 and has continued since then. Perhaps the silence from Mozilla is too deafening for us all to hear an answer.

more options

There are a few potential issues here with Firefox's handling of the Google plus one script. Your efforts so far have ruled out two common issues: inconsistent cached files and cookie-based customization of the script.

Next we should consider whether something in your configuration is blocking the script from loading fully or running to completion. These potential blocks include your add-ons, any proxy servers you may use, and possible external software or settings specific to the plusone.google.com domain.

A standard diagnostic for interference by add-ons is to try Firefox's Safe Mode.

First, I recommend backing up your Firefox settings in case something goes wrong. See Back up and restore information in Firefox profiles. (You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder.)

Next, restart Firefox in Firefox's Safe Mode (Diagnose Firefox issues using Troubleshoot Mode) using

Help > Restart with Add-ons Disabled

In the Safe Mode dialog, click "Start in Safe Mode." Does the +1 script work any better? If not, could you try disabling all nonessential plugins here:

orange Firefox button or classic Tools menu > Add-ons > Plugins category

Any change?

Of course, if you never care to use the +1 button, you could consider blocking it.

Regarding the deafening silence, as far as I can tell, you haven't posted this question before, and neither has anyone else in recent months. Hopefully we can figure it out so this thread can assist others.

more options

Seem to have solved the problem - I am using an add-on NoScript and will move on from there Thanks

more options

hello, if the problem started with firefox 13 it might be an issue with the spdy protocol which was introduced with this version and is used by google on some of it's secure pages. as an alternative you could also try the following:

enter about:config into the location bar & search for preferences starting with network.http. - if any of those entries is set to a custom value (=displayed in bold) right-click and reset it to the default value. if this doesn't resolve the issue or all preferences already were on default, you could try disabling spdy altogether by toggling network.http.spdy.enabled (.v2, .v3) to false.

more options

Hi madperson Thanks for the suggestions but i still cannot get the web pages to refresh. I have downloaded the add-on Noscript - its a bit fiddly to use at first but it works

Thanks john