With the new rules and API version 3 changes YouTube is requiring all users that want to view videos outside of YouTubes website to register and create a Project to access the API. The good news is this process is fairly simple.
In order for you to get the YouTube feed working you need an API Key. Here is the process to obtain that.
- Go to https://developers.google.com/ and log in or create an account, if necessary.
- After logging in go to this link https://console.developers.google.com/project and click on the blue CREATE PROJECT button as depicted in the photo below. Wait a moment as google prepares your project.
- Fill in whatever Project Name you want.
- Then, in the top left corner, click GoogleAPIs link three line hamburger, click the API "APIs & Services" tab and then click "Library". Next, click the link option called "YouTube Data API." It's under YouTube API's. You can see it highlighted in the photo below, bottom left.
- Now click on the "ENABLE" button.
- Next click on the blue 'Go to Credentials' button to the right.
- Choose the select option YouTube Data API v3 for the first select option and Web server(e.g. node js. Tomcat) for the second selection. Then choose Public data. Now click the blue button, "What credentials do I need?".
- Almost done, wait for google to create your new project and you should see the screen below where you can copy your API Key.
- Back in your WordPress dashboard, go to (1) FT Social > "Add New Feed", click (2) YouTube, name your feed, then click (3) Settings, and (4) paste your API Key in our YouTube API Key box as depicted below, then click (5) update. It may take a few seconds for Google to validate the API Key, after which you should see a green "Valid" after the YouTube Access Token, then you can click the green, "Create YouTube Feed" bar and create your YouTube feed.
VERY IMPORTANT: If you get an error notice the best thing to do we have found in the trials here is to absolutely delete the Public API access. Then add it again.
That's it, you're done!
Videos not working?
Trouble Shooting Tip for a non-listed registry provider while attempting to verify your website at Google. It turns out that the DNS CNAME entry for Google is required in some instances (when choosing "Other" from their registry provider list). It's possible the old CNAME will block the new CNAME from working if you do not do this.