• Overview

    The YouTube module allows users to import videos from and display it on the profile.

    The imported video information is stored in a datastore that can then be used to populate lists in other locations around the site.
  • screenshot of importing multiple YouTube videos to your profile
  • Imported YouTube videos display on your Profile

    After you have imported videos from youtube, they will be displayed on your profile and can be accessed as a regular video.

    Each youtube video has its own details page where users can hold conversations in the comments area or tag the videos if the tags module is working.

    They can be listed anywhere on the site with help from the {jrCore_list} or {jrSeamless_list} functions.
  • screenshot of the youtube videos appearing on the profile after they have been imported
  • Connecting to the YouTube version 3 API

    In May 2015, version 2 of the YouTube API stopped working and YouTube required that all web sites change their systems to use the new version 3 API.

    The API is the method that the YouTube module uses to retrieve data from YouTube.

    Starting with version 1.2.0 of the YouTube module, additional steps will be needed to get the module working correctly with the version 3 API.

    Outlined are the steps you will need to take to get a valid YouTube version 3 API Key.
  • Create a Google Developers Account

    If you don't have one already you will need to create a new Google account.

    Official Docs: "Create a Google Account"
  • Create a Project in the Google Developers Console.

    Next, we need to load the Google Developer Console:

    Log in with your Google Developer account, and click the "Create Project" button in the header.
  • Screenshot of the button to create a new project at google developers console
  • Screenshot of the dialog to create a project
  • Screenshot of the enable api's and services button
  • This will create a new Google project for your website - we need this to get a YouTube API Key.

    On the next screen, click on the YouTube Data API option under "YouTube".
  • After your new app is created, select YouTube Data API v3 option
  • Click on the "ENABLE" button
  • Your YouTube version 3 API Key
  • screenshot of the CREATE button
  • screenshot of the api key
  • Copy the YouTube API Key in to the Global Config

    In your Jamroom Admin Control Panel, locate the YouTube modules GLOBAL CONFIG tab and paste the key you just got into there.
  • screenshot of the GLOBAL CONFIG tab on the YouTube module.
  • Your YouTube module will now work as it did before, but will be running on the newer v3 YouTube API.
  • Quota Config

    In the Quota Config tab in the ACP there are some settings for the YouTube module.

    The settings in this area effect profiles in the particular quotas.
    allowed on profile indicates whether the YouTube tab will appear on profiles in this quota. Its the ON/OFF for profiles to use the module.

    YouTube Search turns on/off whether the multiple videos import will be available to the profile owners when the user the 'Create' feature of the module. If this is turned on profile owners will be able to search youtube and mass import videos.

    sync with channel puts an extra field in the profile settings page which accepts a youtube username. If the owner of the profile puts in their youtube username, then any videos in their channel will be imported into their profile. This is checked for new videos on a daily basis.

    Videos added to the profile via this method, then deleted from the profile will be re-added when the daily sync is performed. So if there are videos that came in from a youtube channel that you didn't want on the profile, delete them and they will stay deleted.

    This feature is only setup to sync up to 10,000 profiles, so if you have more than that talk to the jamroom staff. We're not expecting a number so big to be synced on a daily basis and would need to rethink how its done. Google has a limit on the amount of daily API operations that can be performed.
  • screenshot of Quota Config section of the youtube module
  • screenshot of the YouTube Search banner in the create form
  • screenshot of the youtube username input area in the profile section
08 May 2015 04:54:36AM @derrickhand300:
Thanks- that was painless
08 May 2015 11:47:17AM @strumelia:
Thanks for the great and clear instructions! Somehow I managed to stumble my way through before I saw this though. =8-\ l o l
19 Aug 2015 07:49:37AM @isleander:
I managed to sort this out, but the instructions are entirely different in my Safari browser and do not look like that shown above.
19 Aug 2015 07:56:11AM @paul:
What is different? Is it our end, or Google's key creation process?
19 Aug 2015 08:01:11AM @isleander:
I managed to sort it out .. thanks..
Clay Gordon
07 Sep 2015 02:54:30PM @claygordon:
I get a notice by the project name with the following text:

"This key has no referrer restrictions, so other applications might be able to use this key and consume quota. Add restrictions before using this key in production."

Is this something I have to worry about? Your instructions explicitly say NOT to enter in any referrer restrictions.

07 Sep 2015 06:27:27PM @michael:
@claygordon, you can add restrictions if you like, just try it out and if it works keep that. I would expect that if you don't share your key that you receive that the restrictions being blank would not be an issue.
12 Nov 2016 09:36:15AM @soaringeagle:
this documentation needs to be updated the api part does not match whats on the google all so i am hoping i came close after hours and hours of trying.. and it didnt work
12 Nov 2016 09:54:05AM @brian:
Hopefully you didn't actually spend hours configuring the module - it only requires one piece of information, and that is the Google V3 API Key, which this documentation covers. There's nothing you need to do on the YouTube end.

If you have issues with the MODULE config (not your YouTube account) make sure and post to the support forum.