OEmbed for private slideshow

157 views
Skip to first unread message

Antonio Bertucci

unread,
Mar 27, 2012, 6:20:04 AM3/27/12
to slideshare...@googlegroups.com
Hi all! I'm working on a sample project using the SlideShare API in order to retrieve each slide of a slideshow and showing it via a custom player in Flex. My target is to retrieve each slide as an image, but it seems like oEmbed is not available for private slideshows. There is a different way to achieve the same result with private slideshows?

Antonio Bertucci

unread,
Mar 27, 2012, 8:43:46 AM3/27/12
to slideshare...@googlegroups.com
I would like to report also that since this morning I cannot use oEmbed API properly for new uploaded slideshows, even if they are public. I can retrieve the API response in XML/Json correctly, but it seems something changed in the url composition of each slide. I used to build each url like this:

$slide-image-baseurl + "-slide-" + $slide-nr + $slide-image-baseurl-suffix

but this pattern seems broken for new uploaded slideshows. Any hint?
Thanks in advance

Jai Pandya

unread,
Mar 29, 2012, 5:38:30 AM3/29/12
to Antonio Bertucci, slideshare...@googlegroups.com
Hello Antonio,

We made some major changes in our conversion stack a few days back,
which has resulted in broken base-url and suffix tags as you have
noticed. We are actively working on a fix for this and we'll report
back soon. It should be correct for older slideshows, the problem
arises for the slideshows uploaded after 23rd March.

-Jai Pandya,
SlideShare

> --
> You received this message because you are subscribed to the Google Groups
> "SlideShare Developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/slideshare-developers/-/yhfH8hHUY-8J.
>
> To post to this group, send email to slideshare...@googlegroups.com.
> To unsubscribe from this group, send email to
> slideshare-devel...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/slideshare-developers?hl=en.

Antonio Bertucci

unread,
Mar 29, 2012, 5:59:37 AM3/29/12
to slideshare...@googlegroups.com, Antonio Bertucci
Hello Jai,

first of all I want to thank you for the reply. I'll wait for an update here (do you have a rough timing estimation about that?).
Also I would like to know if the new oEmbed will be available for the private slideshows (even only for PRO acounts). It would be great :)

-Antonio

On Thursday, March 29, 2012 11:38:30 AM UTC+2, Jai Pandya wrote:
Hello Antonio,

We made some major changes in our conversion stack a few days back,
which has resulted in broken base-url and suffix tags as you have
noticed. We are actively working on a fix for this and we'll report
back soon. It should be correct for older slideshows, the problem
arises for the slideshows uploaded after 23rd March.

-Jai Pandya,
SlideShare

On Tue, Mar 27, 2012 at 6:13 PM, Antonio Bertucci <arc...@gmail.com> wrote:
> I would like to report also that since this morning I cannot use oEmbed API
> properly for new uploaded slideshows, even if they are public. I can
> retrieve the API response in XML/Json correctly, but it seems something
> changed in the url composition of each slide. I used to build each url like
> this:
>
> $slide-image-baseurl + "-slide-" + $slide-nr + $slide-image-baseurl-suffix
>
> but this pattern seems broken for new uploaded slideshows. Any hint?
> Thanks in advance
>
> --
> You received this message because you are subscribed to the Google Groups
> "SlideShare Developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/slideshare-developers/-/yhfH8hHUY-8J.
>

> To post to this group, send email to slideshare-developers@googlegroups.com.


> To unsubscribe from this group, send email to

Jai Pandya

unread,
Mar 29, 2012, 8:12:54 AM3/29/12
to Antonio Bertucci, slideshare...@googlegroups.com
It might take 2-3 more days to get the fix deployed. I'll update the
list accordingly.

About private slideshows, we don't plan to support it via oEmbed. It
falls in the last case of oEmbed specification, 2.3.5 [1]
Instead, I would advice you to use our API[2] as an authenticated user
to access private slideshow.

[1]: http://oembed.com
[2]: http://www.slideshare.net/developers/documentation

-Jai

>> > slideshare...@googlegroups.com.


>> > To unsubscribe from this group, send email to

>> > slideshare-devel...@googlegroups.com.


>> > For more options, visit this group at
>> > http://groups.google.com/group/slideshare-developers?hl=en.
>

> --
> You received this message because you are subscribed to the Google Groups
> "SlideShare Developers" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/slideshare-developers/-/oSAEkVfhi7oJ.
>
> To post to this group, send email to slideshare...@googlegroups.com.


> To unsubscribe from this group, send email to

> slideshare-devel...@googlegroups.com.

Jai Pandya

unread,
Apr 3, 2012, 1:09:54 AM4/3/12
to Antonio Bertucci, slideshare...@googlegroups.com
Hello Antonio,

Our sincere apologies for oEmbed API bug which caused your application to break. We worked on it, and the problem has been addressed now.

Going forward now, you'll find an additional field named as 'conversion-version' in the oEmbed API response. Here is what your updated application logic should be:

for i in total-slides do
  if conversion-version == 2  
    url_slide[i] = slide-image-baseurl + i + slide-image-baseurl-suffix
  else
    url_slide[i] = slide-image-baseurl + '-slide-' + i + slide-image-baseurl-suffix
end

We are soon going to update all the slideshows to the version 2 in a time frame around a month. Then you'll be able to do away with the else part of the application logic. I'll update the group with new changes.

-Jai Pandya,
SlideShare Engineer
Reply all
Reply to author
Forward
0 new messages