Andrew Mills

> Maybe I’m missing something, but let me know if I’m misinterpreting your advice.

Forgive me, I should have been more clear in my wording.

Based on your response to Ipstenu’s question (i.e. you’ve tried activating the TwentyTwelve theme and the menu toggle still does not work), I do not believe the issue lies in your child theme. I believe there is something unique in your parent TwentyTwelve theme.

I’m not suggesting we compare your child theme against your parent theme. I’m suggesting we compare the TwentyTwelve parent theme you have in your possession against a freshly downloaded copy of the TwentyTwelve theme from www.remarpro.com.

> This is stumpifying!

I agree. But I think we’re getting closer to pinpointing the cause.

Your response to Ipstenu’s question suggests the issue is specific to your copy of the TwentyTwelve theme. Otherwise the Vanilla Twenty Twelve test would have worked.

If you have access to a tool that lets you compare two directories (e.g. the diff command), I’d suggest downloading a fresh copy of the TwentyTwelve theme and trying to isolate the difference.

TwentyTwelve adds navigation.js in the functions.php file, with a wp_enqueue_script call. It specifically sets the in_footer attribute to true, to cause navigation.js to load in the footer.

By any chance, have you loaded navigation.js elsewhere, prior to the functions.php in the parent theme being executed? I ask because if the script is loaded elsewhere, that might keep wp_enqueue_script from loading the navigation.js file, depending upon how it was loaded.

Or, less likely, have you overridden any functions in TwentyTwelve’s functions.php by making them pluggable functions in your child theme’s functions.php?

Okay, did some digging/debugging with Chrome’s Inspect Element tool on the Wisconsin site. Think I might have a potential clue, but not a complete solution just yet.

When your site’s page is first loading, it invokes the navigation.js that we mentioned earlier, but line 7:

var nav = document.getElementByID( 'site-navigation' ), button, menu;

. . . returns a null value for nav. Since nav is null, lines 8 and 9 cause the function to return immediately without assigning anything to the button or menu variables.

And since no button object exists/gets created, the button.onClick event handler never gets created. So you can click that menu button all you like, there’s just nothing on the other end listening for it.

(Interestingly enough, when I perform the same debugging against a copy of the same site found in Internet Archive from 7/31, the navigation.js works fine, setting a value for nav, button and menu, as well as tying the event handler function to the onClick event of the button object.)

In english, I’m saying I think navigation.js is firing TOO early . . . before the navigation menu has been rendered. Something has changed between 7/31 and now that is causing that particular javascript to be executed before the page has finished loading completely, instead of after. I’m hoping this gives you a Eureka moment, because without knowing more about the difference between TwentyTwelve and your child theme, I can only offer conjecture about what might be causing it.

If it is the javascript, it would be in TwentyTwelve’s /js/navigation.js file. I am assuming no modifications have been made to this file?

I can only think of two possibilities:

1) an id or class attribute in the menu HTML has been either renamed or removed, so the JavaScript is no longer able to grab the DOM object it once did.

2) the JavaScript needs to be inside the child theme to work properly (but I don’t believe this is true, because when I create a generic Twenty Twelve child theme and try to replicate the problem, everything seems to work properly.)

In your theme’s stylesheet (style.css), near line 440, you have an entry for a div id called #access. The width attribute has been set to 50%. If you comment out this width attribute, or remove it, your website’s navigation will extend out to a straight line.

It looks like it is accomplished by a shortcode. Check out the FAQ on the link, the “How do you insert the player within a blog post?” question.

There are a number of podcast plugin solutions to choose from, but based on a quick scan, I’d say this one looks the most polished and promising.

Just a hunch, mind you, but I think you managed to move it successfully. ??

(Cool site, by the way– like the color and style of it.)

If you consider this thread resolved, could you please do me a favor and mark it as such? Thanks!

My guess would be the first option, “Force Rewrite Titles.”

Just curious, but since you don’t like the “Page Name > Site Name” format, what is your preference?

Any luck with disabling the plugins?

> I was very hesitant to wipe the root folder clean with FTP

Actually, the concern I had was you moving the contents of the a1bestservice folder into the root. But you will see what I mean when you read the directions, I think.

I think you’ve answered your own question (the first one, I mean). It’s showing “About >> Name Of The Website” in Google’s search results because that is what the title attribute of your home page happens to be.

The second question (how to change that?) is more complicated, because I don’t know all the plugins/theme you are using. I’m guessing you probably have an SEO plugin activated? If so, there are probably some settings in there that control what is shown in the browser tab.

I’m not an SEO expert, but I think PageName – Website Name (or some variant like that) is a pretty standard formula for page titles, so you might want to leave that alone unless someone who knows SEO is telling you to change it to something else specific.

From what I recall, and it’s been a while, you create an account and then can add sites to your account. But you have to prove you have access to those sites by adding a TXT record to the DNS or uploading a text file with a random code/filename to the site.

Once you’ve added the site to GWT, it will tell you the “health” of the site, let you know if Googlebot is running into problems that prevent it from scanning the site, etc. Make sense?

> I have an FTP client and if I log into that and just take out what’s in the root directory, then copy everything from the a1bestservice folder, will that do the job?

No, do NOT do that.

Here, read this: “Giving WordPress Its Own Directory“, specifically the “Using a pre-existing subdirectory install” section.