James DiGioia

Thanks for the issue. I’ll take a closer look at this as I’m working on the new Gutenblock. I don’t use the Gist integration a ton myself, so it’s possible something changed or broke here.

Different branches are feasible. You can use a filter. Documented here: https://github.com/mAAdhaTTah/wordpress-github-sync/wiki/Customizing-WordPress-GitHub-Sync-with-Filters#wpghs_sync_branch

This is fixed too. Thanks!

Works perfectly, and seems to have addressed the memory issues I was having as well. Thanks!

Yeah, ignore the request to make them run side by side. I’m going to go with this one, cuz it’ll be easier to integrate into the FE.

On the JSON-LD side, it would be awesome if we could get that as just an object rather than an array with several nested. Don’t know if there is a reason it’s an array, as I believe it should only be output once, but I could be wrong about that.

Will close this for now. I do have another suggestion I will open another thread for.

Honestly, I may not run both. I added that one at the time cuz it was the first one I found. I then started to look for something to add the JSON-LD and found this plugin. If this is more actively maintained, I might just switch but will need to look into it more.

My apologies–I thought Yoast itself added this data but I forgot I added this plugin: https://github.com/niels-garve/yoast-to-rest-api

You need to create the repo. This link: https://github.com/SorianoTech/Post_Blog 404s.

You can use the functions found here: https://github.com/mAAdhaTTah/wordpress-github-sync/blob/master/helpers.php – Getting it to appear on the header is specific to your theme.

You changed the GitHub hostname. It should be: https://api.github.com – only change this if you’re using GitHub Enterprise.

Any errors in the browser console when you do this? What browser / OS are you using?

Bizarre. Maybe needed a flush of the rewrite rules? That happens on plugin activation.

No, WPGHS is for syncing your WordPress content, not the assets of the site itself.

• This reply was modified 6 years, 8 months ago by James DiGioia.

If you’re using a company account, that’s probably an enterprise account, which would mean you need to update the API url in the settings.

Looking over the code, this may be a bug in WPGHS. Let me look into this a little deeper, but it appears we’re not handling all of the meta correctly on our side.