Error: 401

This topic is: resolved

Tagged: ,

This topic contains 4 replies, has 3 voices, and was last updated by  Hans 8 years, 10 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • March 30, 2015 at 8:24 am #4071

    VivereSmart
    Participant

    Hi, first of all, excuse me for my English.

    I’ve done everything the video tutorial says. But when i try to authorize the plugin i see this error. Can you explain me why?

    error: 401

    March 31, 2015 at 1:29 pm #4075

    Evan Herman
    Keymaster
    Post count: 568

    Hi VivereSmart,

    That error generally means you’ve entered one of the URL’s incorrectly in the Google Developer Console.

    Take a look at the following thread explaining how to resolve the issue :

    http://stackoverflow.com/questions/17166848/invalid-client-in-google-oauth2

    You may also simply need to ensure that you’ve entered a product name into the consent screen. Without that, things won’t work properly.

    Thanks,
    Evan

    June 2, 2015 at 12:30 pm #4865

    Hans
    Participant
    Post count: 5

    The same problem here. The url I entered is http://blog.han.nl/vergrootjewereld/wp-admin/admin.php?page=youtube-for-wordpress which is ok. But when I click the Authorize Now button I see that /vergrootjewereld/ is missing in the url to google api thus the redirect is also wrong.

    A bug?

    June 2, 2015 at 12:51 pm #4869

    Evan Herman
    Keymaster
    Post count: 568

    Hi Hans,

    That is indeed a bug. I’ve had another user report a very similar issue. I believe that the issue is related to the redirect URI which actually gets dynamically generated based on the page you are authenticating from.

    I’m not sure how familiar you are with code, but if you open up class.youtube-for-wordpress.php, scroll down to line 1297 you’ll see where and how the URL is being generated.

    I don’t currently have access to the workaround I came up with to ensure the URL is correct when generated. When I can get access to that little snippet I will certainly add it here.

    In the meantime you can always hardcode the URL you know to be correct into the $redirect variable. So for example, you might replace it with something like:

    I am trying to find the time to loop back around to make some updates to this plugin, but am having a hard time finding some at the moment.

    Thanks, hopefully the following above snippet will help you get things up and running.

    Evan

    June 3, 2015 at 3:30 am #4896

    Hans
    Participant
    Post count: 5

    Ah that’s a pitty. Our developer do not want to install a plugin which has a bug. It is running on more then 60 blogs then with tens of plugins. It must be manageble for them.
    Do you have timeframe when this bug is solved? If not or it lasts to long I am afraid we have a show stopper and must search for another plugin

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.