Gary Allman

That’s odd. I found that using the <!–more–> tag had exactly the reverse effect, So I had to go through a bunch of recent posts removing the more tag. When I did, continue reading re-appeared. (Baskerville 1.15)

Checking Further if the <!–more–> tag is inserted near the start of the post the ‘Continue reading’ link does not appear. If the <!–more–> tag is put in further from the start the prompt appears – but not where the more tag is inserted.

Seem to be a bit of a problem. Leaving the <!–more–> tag out seems to give the best results – for me anyway.

This seems to be a problem with the latest (1.16) version of Baskerville.

I upgraded to 1.16 today and had to promptly roll back as it threw out all my 100% width images shifting them to right and cutting off the right side of the image.

Checking the HTML I found a forced element style of width 1300(ish) pixels on the wrapping <div id=”Attachment_9999″…> which seems to be the cause of the problem, but I’ve not had time to check on it. I’ll need to set up a Sandbox site to test further.

Reverting to 1.15 fixed the problem. If you can lay hands on 1.15 it might fix the problem for you too.

Same problem. Occurs when editing old posts. doesn’t appear to stop the site running.

Fatal error: Internal Zend error - Missing class information for in /home/content/23/8252523/html/breakfastinamerica/wp-content/plugins/google-analytics-for-wordpress/admin/api-libs/googleanalytics/class-api-googleanalytics.php on line 5

@leejosepho Excellent summary, thanks. I should have been making notes as I went through the latest code to see if there were more. The header change is one I may transfer over to my child themes – I’ll have to take a closer look.

It would be very nice to have software release documentation that highlighted what theme users need to look out for. I still haven’t had time to go back and undo some of the CSS changes that were made in 1.2.

At least 1.3 doesn’t seem to break anything – though the Yoast SEO plugins threw a few exceptions when I installed the theme update. I need to go back and check the source code output to the browser to ensure they are operating as expected.

We’ve got a support ticket open with the jetpack team. They are aware of the problem and dealing with it.

They have confirmed (and we have also by experimentation) that all the people on the database get their updates regardless of the numbers counted and showing in the list. So, it’s not cleared up, but they are working on it.

@produceonparade download and check your csv file.

We downloaded ours and all the contacts are there – there’s a counting problem.

There is a difference of 20 between the of number people in the CSV list and the count *and* the list of people that is displayed.

Ditto. One of our sites https://www.thebluebottletree.com ‘lost’ 20 subscribers overnight. There were no posts made (so we couldn’t have offended anyone). Anyone else? Any ideas?

WP 3.6 & jetpack 2.4.2

Excellent – that’s what I’ve done with my sites, and this was going to be my next suggestion.

(BTW You can mark this thread as resolved if you are happy with the solution).

Just checking in – @chaplaindoug did you find a solution, or are you still looking for one?

@paul, ah, I was not aware of the earlier questions in other forums. As you say the plug-in provider needs to address the ’empty black [space]’ issue in the slider.

The css clear property specifies on which sides of an element where other floating elements are not allowed.

In your case clear:left; would probably work equally well, as the floating element is to the left, but it is safer to clear both sides in case one page has a long, right floated sidebar.

Taking a moment to think on this, the problem can probably be solved by a properly placed clearing div <div style="clear:both;"></div> or adding
`clear:both;’ to #colophon

You have a full width content immediately above the footer on the front page which is why you are not seeing the problem there.

I’ll be interested to hear what fixes it.

I did a bit of poking around, the problem seems to be with the #colophon css or the css of one of the preceding divs. Adding display: inline-block; Moved it to the right place, but it’s left justified – needs centering with `margin-left:auto; margin-right:auto;’ you may need to add width and also rules for dealing with responsive changes as the view-port size changes.

Hope that helps.

I recommend using your browser’s development tools to run through the HTML, that’s the Firebug plug-in in Firefox, or [ctrl]+[shift]+[i] in chrome. Step through the HTML in the panel and it highlights on the page giving you an idea of where the problem might be.

Your page <footer>:

<footer id="colophon" role="contentinfo">

(not to be mixed up with the post footer)is sitting outside the #page div, checking a standard twenty twelve post page, the page footer HTML is inside it.

It looks very much like you may have accidentally inserted some code in the wrong place…

@chaplaindoug, if I understand you correctly, what you wanted to do is a standard feature within WordPress without any code changes at all. So I’m probably misunderstanding something…

However, here’s how to achieve this effect without code:

• Create a page to act as your home page.
• Create a another page, doesn’t matter what goes on it as the content will be ignored.

From the dashboard, settings-> Reading, Select ‘A static page’ as your home page, selecting the first page you created above to be the home page. Then select the second page you created above to be your posts page.

You can limit the number of posts by Adjusting the ‘Blog posts to show at most’ which is the next field in the settings form.

Add a link to the blog posts page in your menu and you are done. You’ll get a page of recent posts, and a home page you can style however you want.

The above might be an easier route if you don’t want to mess with code.

This website I created: https://www.ionahighlandtours.com/ uses Twenty Twelve and the above technique. The Blog posts are listed on the ‘Tour Blog’ page from the menu. By using ‘More’ the site owner can control how much text appears on the Blog Posts page. Nice and simple.