Doodlebee

I’ve had W3TC do it to me before, when I accidentally set the admin to cache :). You know, ’cause I was good like that. I’ve also had Firefox do it to me quite often, which is why I swapped to using Chrome.

That’s another thing you can try – open the admin in a different browser. See if it’s still doing it.

In your CSS, you have your footer set to position:absolute. That’s a no-no. It takes it out of the flow of the rest of the site and absolutely positions it where you tell it to (or the closest relatively positioned container it’s inside of, whatever comes first.)

You also have the footer set as text-align:left.

Remove the absolute positioning and set the text to align center.

Do you have a caching plugin installed? You might just need to clear your cache.

There must be a n extra closing div somewhere in the middle. Like within a post, or in the sidebar. The validation will only see that there’s an extra one, and show you that it’s found one (which is usually the last one it finds, not the one you need to know about). Finding stuff like this takes time. I usually copy the source code and paste it in a text editor and just start picking it apart until I find the culprit.

What do you mean by this?

I mean that the href supplied in the anchor link is where all those links are going. If you want them to go somewhere else, you need to edit the URL for those links.

And yes, they ALL go where the links tell them to go. Contact page – everything.

Interesting.

I just openings your page again, and on initial page load, none of them worked. But reloading the page (or clicking the first link) they work fine.

Have you opened this puppy up in Chrome and used the developer tools? It appears that something is taking a long time to load, because in initial page load, the site is squashed, as if something is pushing the margin on the right to a huge size. When I reload it’s all fine. Bet it’s caching, and working fine after whatever it is loads.

I wonder what happens if you remove the form?

So you need a *development* version of the site so you can work on things without it affecting the live site. Is that correct? You don’t need both sites to be LIVE, you just want one where you can work on things until they get how you want them to be, and then copy these changes over to the live site? (Because managing two sites that are exactly the same will be a nightmare, not to mention bad for SEO)

If that’s the case, WordPress’ content isn’t maintained within the FILE SYSTEM. It’s in the databse. The files are not for the pages and themes, plugins, etc. but all actual content is in the databse. You can’t just copy the WordPress files to someplace else and expect it to work. You also have to make a copy of the database.

There’s several ways to do it, and the codex can walk you through some of it. But I use BackupBuddy myself. It makes it a lot easier/faster. It’s not free, though, but if you’re a developer and do this often, it’s well worth the cost.

Why? Is there another reason besides translation? Because if you’re doing it *solely* to have a “translated copy” of the site, you don’t need to do that. You just need a plugin for translations, and you can do it from within the site you’ve already got.