Ayesh Karunaratne

The resulting HTML content are cached at WordPress, so it’s unlikely the plugin made different API calls for AMP and standard page view.

Do you see any errors in browser console log? What do you see when the post is published? It is possible that Instagram has rate limited your IP address. They often rate-limit browsers specially after they stopped showing content without logging in. This is different from the APP rate limit, which is set to 5 million per day per.

• This reply was modified 4 years, 1 month ago by Ayesh Karunaratne.

Yes, Pinky promise ??
In fact, this plugin only provides APIs for embedded for WordPress to pick up. Not the other way around.

You are right, it’s probably the latter.

SELECT * FROM wp_postmeta WHERE (meta_value LIKE '%fb-root%') OR (meta_value LIKE '%instagram-media%') 

Here is another more fine-grained query. They are the output HTML from oEmbed APIs. If you see positive results, they are very likely from Facebook/Instagram embeds.

It should automatically “heal”.
The plugin intentionally overrides WordPress’s legacy API for Facebook and Instagram, so when the plugin is present, it will use the new APIs to fetch embed content.

You don’t need to remove content; the plugin automatically provides the replacement APIs so the embeds are fetched without having to do anything further.

Hi @carlgross
WordPress caches the oEmbed requests permanently unless the post is updated or deleted. This plugin will only be effective if you add or update content with Facebook/Instagram embeds.

You can search for existing Facebook-related content with a query like this:

SELECT * FROM wp_postmeta WHERE (meta_value LIKE '%facebook%') OR (meta_value LIKE '%instagram%')

If you see any positive results, that means you have content with those embeds.

This plugin works with the classic editor as well. WordPress internally uses same APIs to fetch embed content. I will update the readme file to make it more clear in the next release.

• This reply was modified 4 years, 1 month ago by Ayesh Karunaratne.
• This reply was modified 4 years, 1 month ago by Ayesh Karunaratne.

Thanks for the feedback – I just cut v1.4 release with this feature.

define('OEMBED_PLUS_HIDE_ADMIN_UI', true);

Snippet above in wp-config.php (or anywhere else for that matter) should hide the admin UI. It hides the UI even if the API key and secret are not set in the wp-config.php file, which makes it a toggle to hide the form after setting the API key from the UI.

Let me know if this would work. I will release a new version with this change, and some code cleanup baked in.

Thanks for the feedback and the suggestions, @madtownlems.

I think it will be more straight forward if there was another PHP constant that can be defined in the wp-config.php file, for example, OEMBED_PLUS_HIDE_ADMIN_FORM, that will make the plugin not add the setting form at all if set to true. This way, the site administrators who manage the wp-config.php can decide if the plugin should be completely silent.

Hi @mikefalls – as a temporary workaround, you can remove the plugin directory and your site should be back right up.
It requires PHP 7.3, is your site on PHP 7.3 or later?

Hi @mamarce – I have just cut a new release 1.2, that has this feature.
See https://dev/phpwatch/public/articles/wordpress-facebook-instagram-oembed#wp-config

That’s a good idea, thank you.
I would have preferred a PHP constant or even an environment var approach too, but I suppose I was trying to make it a bit more user friendly.

Adding the constant check and selectively disabling the settings form wouldn’t be too much of work, I will make changes and release a new version soon.

Hi @dabiathlet – Yes it is compatible with Classic Editor as well. It uses same oEmbed APIs.

You can remove the plugin files by deleting the directory. I will investigate and push an update with fixes, of which there are a few with similar reports.

Version 1.4 of the plugin has a wp-config option to explicitly set SameSite=None.

@adam320 What’s the browser version you are using? I believe Chrome 80+ assumes samesite=Lax now.