eread

Right. I’d taken “caches” to mean “browser caches”.

I guess with my suggestion of using a browser debugger, if the browser is chocking on a long CSS file, it will probably tell you.

Firefox have a different web page rendering engine than Safari. It might be poorly performing rendering code on Firefox’s part. Chrome and Safari have a lot more in common – you’ll probably find this doesn’t happen in Chrome either.

DionDesigns makes an important point. I assume you are just developing internally on a private network, or that the WordPress instance is just internal.

You wouldn’t try and host from your own network. External providers do it much better and more securely.

That said, determine what your machine’s IP address is by:

1. Locating the Command Prompt – e.g. you can search for “cmd” in Windows 10.
2. Running the command ‘ipconfig’.
3. Finding the appropriate IP address from the list that is given.

The appropriate one will be an address on your local network.

I’ve seen it occasionally with browsers (for many different types of websites) where they seem to finish loading the page without apply any CSS. The fix (for me) is usually to reload the page.

Next time it happens, press F12 in Firefox. This will bring up Firefox’s development tools and it should show any errors that are being encountered.

Is it possible that the CSS is on a different server that timesout from time to time?

It could be a Firefox bug causing an intermittent failure. You are using the latest Firefox?

It’s helpful to look at the code as being in a grid, with each character occupying a specific row and column.

In your specific case, it just means that the errors are caused by the text on the given line that runs from column 1 (the left-most column) to column 4 (a column that runs four characters in from the left).

If you look at that closing “p tag” that is highlighted in your validator, here is how each character sits in each column:

“<” – column 1
“/” – column 2
“p” – column 3
“>” – column 4

Does that help?

Other computers on the network can’t use the host name “localhost”. That is just how a computer refers to itself.

If you can establish what your network IP address or host name is, it should be a matter of replacing “localhost” with the appropriate IP address or host name in those links above when accessing WordPress from other computers on the network.

If you aren’t sure how to establish what you IP address or host name is, reply back with what operating system XAMPP is installed on and we can give you some commands.

Hi,

There is definitely a problem there. Bring up the site in IE, Chrome, and Firefox and press the F12 key. That will bring up a debugger.

You’ll be able to see there that, as you scroll through the page, errors start getting thrown. That might help you progress further.

A couple of things:

1. As a workaround, are you able to try a different browser?
2. Have a look at this topic in Codex. It appears that after Ticket 27373, you are getting a specific error that isn’t about cookies being enabled or disabled, but something else.

Try some of the things mentioned in that third link, and see how you go.

Can your hosting service provide the logs (though a dashboard, perhaps) for the various services you are relying on? Should provide an insight into which step is failing.

Hi,

There are at least two possibilities (and possibly more):

1. Your browser having trouble rendering content that it is being sent.
2. The server is serving up a blank page.

What might be helpful is if you turn on your browser’s development tools while at the blank admin page and see if you can see any obvious errors. Pressing F12 in most browsers invokes the development tools, and the browser might show an error.

If everything looks ok there, check to see if the browser is being served up a blank page. If you view the source of the admin page from within the browser, and find nothing or very little there, then there isn’t much the browser can do to display what you expect. In that case, you’ll need to have a look at server logs to determine why a blank page is being sent to the browser instead of the proper admin page.