mw128

Same here. I will have to deactivate and activate when making a backup as suggested above

We have been noticing the same thing lately, in the past 2 or 3 weeks it’s been happening a lot more often, on more than one site. The permalinks are somehow defaulting to the post number rather than picking up the title. It seems like some kind of timing problem. Sometimes it works as expected and picks up the title, sometimes it doesn’t. Our authors are trying to get used to remembering to check and manually edit the permalink before publishing, but it’s easy to forget. I don’t know if it might have something to do with the Yoast SEO upgrade. That’s the only thing I can think of that changed for us. This started happening before we upgraded to 4.4.

Thanks

I had the same problem. I didn’t expect this plugin to do anything to my blog’s feed– I thought it was only for displaying other feeds! It seems solved now that I commented out the functions but I’ll have to do that after each update ??

I deactivated Yoast SEO and now the RSS feed is fine. I’ll look around for another SEO plugin. I would have gotten rid of NextGen but couldn’t do without it in this case because the client had been using it for years and accumulated many photo albums that were scattered throughout the site- too much work to un-do.

i am having the same problem. NextGen, Yoast SEO and WP Canvas theme. Looking at the /feed page in browser gives:

This page contains the following errors:
error on line 3 at column 1: Extra content at the end of the document

Tried Ivan’s and Michael Ecklund’s fixes and neither made any difference.

In feed reader I get a message “The feed could not be loaded because the content is not in a known feed format.”

This is really a problem for my client because they have a MailChimp campaign that depends on the RSS feed and the emails have stopped working.

I’m sure it probably could but it would take some thinking / troubleshooting and right now I don’t have time. Anyway hoping that Jetpack will do it for us. Or maybe a third party will come out with a Top Posts & Pages of their own that’s even better.

You’re welcome! The only problem is that until they add this functionality, you’ll have to keep re-doing this code every time you update Jetpack.

@roland: The same code applies to pages too. You have to get the postID of the page. Go to the Dashboard–>Pages and hover your mouse over the name of the page. Then look at the status bar in your browser (in mine it’s at the bottom of the window) and you will see the postID there.

You can go into /jetpack/modules/widgets/top-posts.php , look for the line towards the end of the file around line 275 that starts “if ( ‘publish’ !=

and replace with some code that excludes by post ids:

if ( 'publish' != $post->post_status || !empty( $post->post_password ) || empty( $post->ID ) || $post_id=='13849' || $post_id=='2568' || $post_id=='7231' )
				continue;

I agree– the Pinterest button, when set to “Icon + Text”, works perfectly but when set to “Official Buttons” it pre-selects one image. This is frustrating– they should use the same code, don’t you think so?

I had the same problem. What a pain!!!

I am having this problem too. I’m not sure when it started. I didn’t notice it until a user pointed it out. The first symptom was that the shortcode displayed on the page, instead of the flash file. Then I edited the page and regenerated the code using the Kimili icon in the visual editor, and it started to work again, but there is still a fragment of code showing at the top left of the page, on all pages that have the Kimili code. it is:

…” />

I am using a WooTheme, The Station, with some modifications.

I tried this and it worked: first, in the WP Admin under Settings–>Reading, under BuddyPress Protection you turn on (check) the setting to Exclude Blog Pages from protection. Then, in private-buddypress.php on line 146, you change it to:

// No login required if blog pages are excluded
if ( true == $this->options->exclude->blogpages && bp_is_blog_page() && !is_page(106))
return false;

Where 106 is the page id of whatever page you want to be private. I think you can also use an array

!is_page(array(42,'about-me','Contact'))

though I didn’t try that yet.

Kind of a backwards way, but it’s a way of protecting some pages and not others.

Ok it worked– I re-saved the csv using Numbers instead of Excel and it worked great…must have been something to do with my Mac. Thanks I’m happy with how it works now! You may delete my previous posts ??