Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Site preview function not working

more options

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.

All Replies (6)

more options

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?

more options

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.)

more options

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.

more options

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.

more options

Did you try disabling Tracking Protection for the site?

more options

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