Replied to Chopping Ancestors from WordPress oEmbedded Tweets by Alan Levine (CogDogBlog)

After a few rounds of swinging the code axe, I am cautiously optimistic I have an answer. Be warned. What follows involves code modifications to your theme’s functions.php and for older posts, some clearing of stuff in your database. Now that there are maybe three readers left (Hi Tom!), here we go.

This is another great deep dive Alan. I have not quite got to the stage of carving things out in the backend, but have started down the road of a Child theme thanks to your help. I am interested in adding your solution at that level. It really bugs me how the default oEmbed bakes in the parent post.

P.S. Am I the third reader or a lucky forth?

Via collect.readwriterespond.com

Replied to Chris Aldrich (Chris Aldrich | BoffoSocko)

I’ve switched over to David Shanske’s IndieWeb-friendly fork of the TwentySixteen Theme tonight. Liking it a lot so far. Can’t wait to see what little surprises I run across under the hood and how we can potentially make it better for the community.

Really interested Chris in what David Shanske’s theme might have to offer. Having spent some time lately trying to get my head around the ‘motor under the hood’, I am wondering about the difference between David’s approach to fork the 2016 theme, compared to your approach of creating a child. Is there simply fors and againsts for both? Or is one more ideal? Just wondering as per usual.