DeviceSupport "bug" in v2.x (pre-3.0 announcement)

  • ResolvedPlugin Author Aleksandar Uro?evi?

    (@urkekg)


    9 years, 6 months ago

    Dear users of YouTube Channel plugin,

    Today (May 6th) YouTube killed YouTube API v2 and all users of YouTube Channel received “DeviceSupport” video instead latest/random/whatever video from real channels/playlists/etc.

    I’m sorry to inform you that in next couple days I will not be able to finish and release new YouTube Channel v3.0 ported to YouTube API v3 (Work in Progress).

    If you can’t wait until then, you can try with version 3.0alpha2.

    IMPORTANT
    You’ll need to create YouTube Data API Key v3 and insert it to wp-config.php (I will not make available settings field to store this key in database). Learn more here https://developers.google.com/youtube/registering_an_application or simply watch this tutorial https://www.youtube.com/watch?v=8NlXV77QO8U

    Following YouTube tutorial, it’s best to you create Server Key and add IP of your server to allowed servers. If you don’t care, you can leave key unprotected and allowed for all IP’s (just make sure you don’t share that key with others, and that is why I wish to leave it in wp-config.php instead in database).

    Next, when you create API Key, copy it and edit wp-config.php file for your WordPress installation through FTP. Find line:

    /* That's all, stop editing! Happy blogging. */

    and insert above it:

    define('GOOGLE_API_KEY', 'YOUR_SERVER_API_KEY');

    just replace keyword YOUR_SERVER_API_KEY with your real API Key previously generated (surround API key to single quotes).

    Then update Widget settings and update Channel ID field (this is not legacy username but ID starting with UC – you can get it from page https://www.youtube.com/account_advanced.

    Thank you for patience.

    https://www.ads-software.com/plugins/youtube-channel/

Viewing 15 replies - 1 through 15 (of 23 total)
Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘DeviceSupport "bug" in v2.x (pre-3.0 announcement)’ is closed to new replies.