nfong

We figured out the problem. Here are the detail just in case this helps someone else..

We forgot to include this line:
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>
before:
<?php the_content(); ?>

Even without the line, Yoast intercedes and makes everything work!

The specific question is what API calls are there to the Yoast other than ones containing with: wpseo or yoast

It doesn’t copy any of them. Most are text, a couple are dates and numeric.

Clone your custom type posts and lose data.

We did check our post type on the: Enable for these post types

Simple Share Buttons Adder plugin is now adding this javascript that I tried to get away from!

<script type=’text/javascript’ src=’https://ws.sharethis.com/button/st_insights.js’></script&gt;

I edited my https://www.site.com links to https://www.site.com using this guide and all is good!

https://wpbeaches.com/updating-wordpress-mysql-database-after-moving-to-a-new-url/

We’ve isolated the issue to loading the featured image with http and not https.

Chrome has a little shield next to the star icon, to the right of the address bar. Click on the shield and allow Load Unsafe Scripts – Featured image appears.

Question is, how do we force wordpress to switch use https to load the featured image?

No

I have the problem with wordpress 4.4.1 and php 5.4.43. Yes we are using https. No on bitdefender (It was fine under 4.3.1) The featured image field in the admin shows a grid checkerboard gray square with the title of the featured image on top.

On Other site: 4.4.1 Under Php 5.6 it actually works better. I see the featured image on top of the checkerboard gray square. No https use on this site though.

Sam error, just changed where it is:

line 31

Php 5.4.37

Plugin could not be activated because it triggered a fatal error.

Parse error: syntax error, unexpected T_STRING in /xxxxx/wp-content/plugins/facebook-like-button/core.php on line 35

Juan,

You can contact me on my site at foodnut.com and we can work on this.

I just redownloaded it and tried it again. Same problem.

Switching back to 1.1.0 makes it work again.

Is it working now?

I updated from 1.10 to 1.1.1 on a test server and clicking on the Login button that we on our sitead it does nothing now!

Going back to 1.10 makes it work again.