TheLievense

It appears that this was a Tiktok issue as it has resolved itself today.

I pinged the developer on Twitter and he just updated the plugin to reflect that it is compatible with WP 6.2.2

I pinged the developer on Twitter and he just updated it to reflect that it is compatible with WP 6.2.2

Any update? It’s been 4 months since this was initially opened.

Nikel,

I sent the information months ago and haven’t heard from you. This seems to be an issue primarily with iPhone users. Is it possible Apple’s new privacy settings are interfering here?

Much appreciated!

Yes.

https://www.dropbox.com/s/a7gtktpvb5ikt3q/Screen%20Shot%202021-11-19%20at%203.04.38%20PM.png?dl=0

Would be great if a theme has either guttenberg block or theme file based templates that the plugin could control the visibility of this metabox.

• This reply was modified 3 years, 4 months ago by TheLievense.

Jumping in here Template absolutely is a core metabox PROVIDED that your theme supports / has defined multiple templates. They can be defined multiple ways

Guttenburg Templates:
https://themeisle.com/blog/wordpress-post-templates/#gutenberg

Via Global Templates:
https://developer.www.ads-software.com/themes/template-files-section/page-template-files/#creating-custom-page-templates-for-global-use

The latter is the approach taken by us via a single-fullwidth.php template defined in the theme like such:

<?php
/*

Template Name: Full-width
Template Post Type: post, page

*/

• This reply was modified 3 years, 4 months ago by TheLievense.

https://www.hercampus.com

Yes we have this option checked.

Also note that iFramely does properly render Reels so it is something that CAN be supported:

https://iframely.com/embed/https%3A%2F%2Fwww.instagram.com%2Freel%2FCTuakCmAhU5%2F

I JUST opened an issue in GitHub reporting exactly the same thing:

https://github.com/Ayesh/WordPress-oEmbed-Plus/issues

I seem to having an issue as well when using these two plugins together.

So not sure what functionality you guys need but it appears that ACF has a built in Taxonomy field now. I just did the following and my system is now working right:

1.) Update to ACF 4.1
2.) Edit the field and change field type from Text to Taxonomy (under Relational)
3.) Choose which taxonomy group I wanted to display
4.) Set the field selection method (in this case Select instead of checkbox)
5.) Save changes to custom field set
6.) Go into the post that was using this field set and simply click save (all of the previous values were already populated)

Then everything was working fine. Hope this helps with your issue.