TheGremlyn

Fantastic, thanks!

That fixed it, thanks!

I’m using W3TC, and I see a spot in the settings to add user agents to ignore, but I’m not sure what I should be adding. Is there a list of the user agent strings Jetpack recognises available somewhere?

Brilliant, exactly what I needed!

Ah-hah! I had wrongly assumed that it would be added for me simply by enabling threaded replies on the site, but no apparently there needs to be a little snippet to include comment-reply.js before calling wp_head(). Seems to be working now, thanks for your patience!

Hrm, that wasn’t showing up in FireBug for me, but does in Chrome. Seems to stem from jQuery being called after Boostrap. That error no longer exists, but my issue, unfortunately, still does.

The comments section in my theme is based on and still very similar to TwentyEleven’s. A few stylistic changes are really all that exist. The issue seems to be in the Javascript, with whatever is supposed to define addComment. Maybe there is an element missing I’m unaware of, but from what I can see I have all the elements that TwentyEleven does.

Javascript has .childNodes that you might use: https://www.w3schools.com/dom/prop_element_childnodes.asp

But it might be easier going through jQuery with something like .children(): https://api.jquery.com/children/

Happy to help!

Looks like your theme is trying to do some of the SEO work in titling the pages. Change it so that it looks like this:
<title><?php wp_title('|'); ?></title>

Then see if your titles show up properly. If you ever update the theme, you will likely have to redo this, so write it down somewhere ??

Check the theme’s header.php and report back what you see between the <title> tags.

I had a similar issue with the theme I am currently building, but had the blog’s name shown twice. It ended up being that I had set the theme to output the information, but I believe that WordPress SEO catches one of the functions (the_title(), IIRC) and puts a filter on it to display the specified title format in the plugin.

I was helping mlgrippi with this earlier, and it looks like the the ‘CSS Classes’ that you can input on the custom menu items apply to the
li element, not the link element directly.

My assumption is that the javascript is looking for the href of the link for the element with the class=”lbpModal”, but since the custom menu applies this to the li element, there obviously isn’t one.

A potential fix could be to have the script travel down to a child element to find the href.