Hi
I am having same problem with Vimeo as described in other posts but could not find a solution
I have set up the setting including Vimeo API "Consumer Key" & Vimeo API "Consumer Secret"
But still I don't see any videos. I get the message "No matching videos"
I try to read private videos which appears in my user profile (they are of course allowed to be played outside of Vimeo) by using my user id in the "Videos uploaded by this Vimeo user"
Any instructions will be helpful
Vimeo No matching videos
Started by David Rashty1359656628, Sep 13 2012 10:20 AM
7 replies to this topic
#1
Posted 13 September 2012 - 10:20 AM
#2
Posted 13 September 2012 - 02:19 PM
Hi,
There is a feature request for allowing TubePress to work with private Vimeo videos (that is, Vimeo videos that have any access restrictions applied to them). Please star that issue to vote for the idea and track updates. Features with the most votes will be implemented before others.
For the time being, unfortunately, the only workaround is to make your videos fully public.
Does that answer your question?
There is a feature request for allowing TubePress to work with private Vimeo videos (that is, Vimeo videos that have any access restrictions applied to them). Please star that issue to vote for the idea and track updates. Features with the most votes will be implemented before others.
For the time being, unfortunately, the only workaround is to make your videos fully public.
Does that answer your question?
#3
Posted 14 September 2012 - 02:32 AM
It does answer my questions but not the need itself
In the road map it says that this will be fixed on version 2.5
Any idea when this is going to be published. Also can you explain in technical language what is needed to patch this issue, maybe we can do it without our developers
In the road map it says that this will be fixed on version 2.5
Any idea when this is going to be published. Also can you explain in technical language what is needed to patch this issue, maybe we can do it without our developers
#4
Posted 17 September 2012 - 10:02 AM
I have one of my developers working on the issue now. No release estimation yet, but it's in the upcoming pipeline. One caveat is that it's unclear to me if accessing these private videos over the Vimeo API is even possible something that my developer is researching. So there's a small chance that this ticket will simply never be fixed.
If you wanted to point your developers in the right direction, I would suggest they take a look at VimeoUrlBuilderCommand, which is responsible for assembling the URL when TubePress contacts Vimeo. I would appreciate hearing any feedback if they find anything interesting!
Sorry that I can't be of more help at the moment..
What else can we do for you?
If you wanted to point your developers in the right direction, I would suggest they take a look at VimeoUrlBuilderCommand, which is responsible for assembling the URL when TubePress contacts Vimeo. I would appreciate hearing any feedback if they find anything interesting!
Sorry that I can't be of more help at the moment..
What else can we do for you?
#5
Posted 18 September 2012 - 05:15 AM
Private video should appear - this is taken from Vimeo FAQ ()
Why aren't my private videos appearing in the API?
You may be using the Simple API which only provides public data. You'll need to use the Advanced API to access private videos, you can create an application here: developer.vimeo.com/apps
Why aren't my private videos appearing in the API?
You may be using the Simple API which only provides public data. You'll need to use the Advanced API to access private videos, you can create an application here: developer.vimeo.com/apps
#6
Posted 18 September 2012 - 11:15 AM
That's a good lead! TubePress is using the "Advanced API", so there must be something else that we're missing. I'll continue to experiment and see what I can find.
#7
Posted 19 October 2012 - 04:32 AM
We managed to fix the issue - we added some code to
Feed.class.php (path: sys/classes/org/tubepress/api/const/options/names/) – added two new fields: Access Token and Access Token Secret
DefaultOptionDescriptorReference.class.php (path: sys/classes/org/tubepress/impl/options/) – descriptors for above two fields
FeedTab.class.php (path: sys/classes/org/tubepress/impl/options/ui/tabs/) – added inputs to “Feed” tab in settings panel
VimeoUrlBuilderCommand.class.php (path: sys/classes/org/tubepress/impl/feed/urlbuilding/) – make use of access token and access token secret in oauth.
We also handled support in cases of https sites
VimeoUrlBuilderCommand.class.php (path: sys/classes/org/tubepreee/impl/feed/urlbuilding/) – change in line 82: const URL_BASE = 'https://vimeo.com/api/rest/v2'; (change from http to https)
CurlTransport.class.php (path: sys/classes/org/tubepress/impl/http/transports/) – change in line 163: CURLOPT_SSL_VERIFYPEER => false (disable verification, vimeo ssl cert is not accepted by cURL)
Let me know how to send you the code changes (email will be best)
Feed.class.php (path: sys/classes/org/tubepress/api/const/options/names/) – added two new fields: Access Token and Access Token Secret
DefaultOptionDescriptorReference.class.php (path: sys/classes/org/tubepress/impl/options/) – descriptors for above two fields
FeedTab.class.php (path: sys/classes/org/tubepress/impl/options/ui/tabs/) – added inputs to “Feed” tab in settings panel
VimeoUrlBuilderCommand.class.php (path: sys/classes/org/tubepress/impl/feed/urlbuilding/) – make use of access token and access token secret in oauth.
We also handled support in cases of https sites
VimeoUrlBuilderCommand.class.php (path: sys/classes/org/tubepreee/impl/feed/urlbuilding/) – change in line 82: const URL_BASE = 'https://vimeo.com/api/rest/v2'; (change from http to https)
CurlTransport.class.php (path: sys/classes/org/tubepress/impl/http/transports/) – change in line 163: CURLOPT_SSL_VERIFYPEER => false (disable verification, vimeo ssl cert is not accepted by cURL)
Let me know how to send you the code changes (email will be best)
#8
Posted 19 October 2012 - 05:42 PM
Excellent! I'll pass this info on to my developer right away. I'll also send you a private message with my email so that you can share your changes.
Thank you!
Thank you!