You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by a couple Plate users and I've been able to duplicate this issue on a local install.
Filed a new issue on the wp-calypso repo so waiting to see if anyone has any clues as to why this is happening: Automattic/wp-calypso#30837
Note that this Gutenberg block is for displaying a single instagram post.
In a nutshell, the embed is working on the Post or Page edit screen but does not show up on the front end.
There are no JS errors in the back end or on the front end page affecting this and additionally there were no PHP or Apache errors on my install so this is a bit of a mystery.
The text was updated successfully, but these errors were encountered:
While I'm normally super aggressive about fixing issues as soon as possible, the next two weeks are insane for me: 4 current projects under deadline and a baby due anytime(!).
If anyone wants to take a crack at this and figure out what script is not getting enqueued on the front end, I and all of the Plate users would be eternally grateful.
Otherwise, I will get to this as soon as I'm able (probably in 2–3 weeks).
This is fixed by removing the $content_width value in functions.php line 781. For now I've commented that out in Plate as it was only in there for Theme Check.
Solution: If you are using the Instagram Block, make sure the content_width function is commented out in functions.php line 780 (your line number may differ).
Reported by a couple Plate users and I've been able to duplicate this issue on a local install.
Filed a new issue on the
wp-calypso
repo so waiting to see if anyone has any clues as to why this is happening: Automattic/wp-calypso#30837Note that this Gutenberg block is for displaying a single instagram post.
In a nutshell, the embed is working on the Post or Page edit screen but does not show up on the front end.
There are no JS errors in the back end or on the front end page affecting this and additionally there were no PHP or Apache errors on my install so this is a bit of a mystery.
The text was updated successfully, but these errors were encountered: