Vimeo video

[Matej]

We are testing a newer version of Concerto (2.3.0), but cannot add a Vimeo video. When trying to add a Vimeo video to a feed, I get a message: "401 authorization required". Video in question is public, viewable to anyone and embeding enabled: https://vimeo.com/141767663

Any suggestions?

Matej

[Marvin Frederickson]

This is a result of the video_info gem not being configured with your vimeo api access token.  Unfortunately there is no way to configure it in the current version.  However, I've already made the changes to accommodate this here https://github.com/concerto/concerto-remote-video/pull/32 and it's just waiting for August's approval.  You will have to obtain that access token from vimeo, and you'll probably want one for youtube also.

[Saša Friedrich]

Marvin thanks for help so far! Here's what we done:
- Installed Concerto server (VM image on Xen)
- Manually applied your changes to code (precompile assets also)
- Created "Vimeo App" and obtained personal access token

Result:
- I can set access token (for Vimeo and Youtube) in Concerto Settings
- I can add Vimeo Video content
- I can see video playing when viewing item (http://my_url/feeds/feed_id/submissions/item_id)

BUT...  When I try to preview screen, the screen is blank
In java console (Chrome) I can see:

Uncaught ReferenceError: Polymer is not defined(anonymous function)
@ concerto-remote-video-8ef77eedc11760fb5575a77e5b55733f.html:44

Uncaught ReferenceError: ConcertoBehaviors is not defined(anonymous function)
@ concerto-remote-video-8ef77eedc11760fb5575a77e5b55733f.html:44

No content available for field 1
No content available for field 1


Any suggestion?

Marvin Frederickson je 16. 10. 2015 ob 21:20 napisal:

This is a result of the video_info gem not being configured with your vimeo api access token.  Unfortunately there is no way to configure it in the current version.  However, I've already made the changes to accommodate this here https://github.com/concerto/concerto-remote-video/pull/32 and it's just waiting for August's approval.  You will have to obtain that access token from vimeo, and you'll probably want one for youtube also.

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-s...@googlegroups.com.
To post to this group, send email to concerto-dig...@googlegroups.com.
Visit this group at http://groups.google.com/group/concerto-digital-signage.
For more options, visit https://groups.google.com/d/optout.

[Marvin Frederickson]

I believe that there are some crucial fixes that have been made to the concerto-frontend that have not yet been released to the vm image yet.

Using the latest build of concerto and it's plugins, I am able to view vimeo content on a frontend screen running chrome with no problems.

[Saša Friedrich]

Yes, that did the trick! I updated Concerto Frontend plugin and then I had to precompile assets (application.js was missing). Now everything works fine.

Marvin... Thanks again for all your help!

BR

Marvin Frederickson je 20. 10. 2015 ob 18:35 napisal:

I believe that there are some crucial fixes that have been made to the concerto-frontend that have not yet been released to the vm image yet.

Using the latest build of concerto and it's plugins, I am able to view vimeo content on a frontend screen running chrome with no problems.