ilowelife

Hi Nick,

Yes, everything is working as expected with Pages. I should have mentioned that in my original post, as I had tested it, which is why I knew there was a specific problem with the custom post type.

With ACF Custom Post type with Hierarchy enabled, there seems to be a problem specifically with the detection of the Parent (has children) case.

I just created a simple test ACF with hierarchy, then created the same structure as you did. Each page has the the same 3 blocks with the same 3 visibility rules:

1. Show block A if page is Top Level (no parent)
2. Show block B if page is Parent (has children)
3. Show block C if page is Child (has parent)

The problem seems to be detection of the parent:

? On Page 1, the Top Level block appears

? On Page 2, the Child block appears, but not the parent block

? Page 3 displays the child block

? Page 4 displays the Top Level block

Thanks for looking into this. I love this plugin and your commitment to it.

Anyone figured this out?

Also a pro user. I contacted support and they said that it was a change on Instagram side and that if I couldn’t get it to work they would give me a refund.

I would prefer to just get it to work.

@scorchett3 I see that your page has instagram back in the feed. Did you do anything specific?

All back to normal on my end and I did nothing. I don’t think it had anything to do with the plugin.

I think it’s a problem with YouTube. I’m seeing the same thing, but if I go to https://developers.google.com/youtube/youtube_player_demo to test out an embed code, it doesn’t work either. At first I thought it was the plugin, but even local html tests are giving me a big empty space where there was once a video.

Interesting.

Yesterday, pre-plugin update, I had a very simple shortcode implementation:

[audio mp3="/wp-content/uploads/02-Ave-Maria.mp3"]

This worked fine in Chrome/FF/Safari Mac.

When I updated the plugin, those browsers began displaying the double version of the player.

I didn’t test in IE yet either.

I reverted back to the previous version and it’s all fine again.

Upgrading to this version caused a regression where the player displays both the flash and non-flash version simultaneously for mp3 audio. The recommended fix from a previous thread where this was happening — ensure that the file type is used in the shortcode for the source file link — does not solve the problem with this version.