319

@omarfpg Is this actually even being worked on between Woo and Meta? Because it seems like a pretty hopeless dead-end with not one single provided update here or on the Github issue in over ONE YEAR and every Woo site now losing all their Instagram sales because of this.

I can confirm, this was a big annoying issue for us as well. Had to roll back to 1.9.7?to stop subscription renewals from being marked as completed.

Yes, please fix this issue!

Updating Elementor core to 3.6, or newer, causes this plugin to trigger a critical error that crashes the whole site.

Looks like this issue with spotify was actually caused by a blank pubdate tag for each episode. The feed still doesn’t validate because of the image tag, but Spotify restored our show now.

I’m not using a static homepage, but the settings for this plugin are not showing up for me on the customizer page either. Any help would be much appreciated, running WP 4.5.2.

Same problem here. With the latest update to Genesis 2.2.0 (Released: September 1) this plugin no longer works.

I had a similar issue starting this week where jetpack had the og:image tag in there but when published to facebook it was always grabbing the wrong one until I went into facebook debugger and re-scraped the post (super annoying to do this for every article every day).

From what i can see, jetpack is missing the og:image:width and og:image:height tags and facebook debugger now seems to throw up a warning if those tags are missing.

Until jetpack or facebook repairs the problem I found that installing the Open Graph Protocol Framework plugin fixes the issue since it includes the image width and height tags that jetpack does not.

Sent.

Broke again.

Clicked to connect to facebook and it gave me the same empty white modal window and disconnected me from wordpress.com … back the cycle where i’m getting the error:

Invalid request, please go back and try again.
Error Code: invalid_client
Error Message: The required “client_id” parameter is missing.

when i try and click “connect to wordpress.com” … just deactivated and re-activated Jetpack and i was able to connect / authorize, but still back to where I was at the start of the problem.

Alright i’ve disconnected and re-reconnected wordpress.com to jetpack. Won’t touch publicize yet, until you say it’s ok.

Each time publicize worked fine connecting to facebook, twitter, and google but both times it was trying to connect/disconnect from Tumblr that broke jetpack.

Ughh. I tried to connect tumblr again this morning and am back to where I started with my initial post, all the same errors. Could you please reset it on your end again? I’ll stay away from the tumblr connection.

Thanks! That fixed it.

You’re right! I’ve been doing it the dumb way forever now, this is perfect. Thanks!

This really needs to be built-in setting in the plugin, otherwise you have to remember to edit the code every time a new update is released, which is often.

Just checking in to see if there’s been any update on this? I would love it if I could simply type the [crp] shortcode and have it follow the plugin settings regarding limit etc.

I only want 2 posts to show up every time, but have to add [crp limit=”2″] instead of simply [crp] otherwise it ignores the plugin settings and defaults to 5 every time.