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

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

详细了解

Site preview function not working

  • 6 个回答
  • 0 人有此问题
  • 7 次查看
  • 最后回复者为 RandyGibbons

The preview function (loading a preview web page) in Wordpress is now generating an 'Oops that page not found error.' A relatively recent problem. My Enhanced Tracking Protection is set to Standard, but I get the same problem when set to Strict. I do not have this problem with Chrome or Microsoft Edge.

The preview function (loading a preview web page) in Wordpress is now generating an 'Oops that page not found error.' A relatively recent problem. My Enhanced Tracking Protection is set to Standard, but I get the same problem when set to Strict. I do not have this problem with Chrome or Microsoft Edge.

所有回复 (6)

Did you compare the URL that Firefox tries to open with the URL that works in other browsers to see if there is a difference?

The URL is the same. What does that signify?

(NB: I forgot to note that the same problem occurs when I do this in a private window in Firefox.)

Do you have to authenticate to be able to access the page (i.e. a session ID cookie needs to be send) ?

You can check for issues with Total Cookie Protection.

Messing around (so to speak) with the Wordpress help folks, we were able to fix the problem. We did this by exercising the WP function for creating a new post from an existing one. Cookie-wise, the new post starts with a clean slate. Our imperfect diagnosis: the introduction of Firefox's 'cookie protection' features somehow corrupted the underlying cookies that the Wordpress generate-preview function uses, and no fiddling with the settings for the 'cookie protection' features was able to fix the problem. Anyway, problem fixed, and thanks for your help.

Did you try disabling Tracking Protection for the site?

Yes, for the record, (that is, I tried disabling Tracking Protection for that site), but it didn't fix the problem.