Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues while loading some URLs. #11

Closed
cfviotti opened this issue Sep 26, 2014 · 4 comments
Closed

Issues while loading some URLs. #11

cfviotti opened this issue Sep 26, 2014 · 4 comments
Labels

Comments

@cfviotti
Copy link

We're using embedder on Portal Modelo (https://github.com/interlegis/portalmodelo) and when we load Flickr sets URLs, for example, we receive a collective.oembed "404 not found" error message in our log, though the link works ok on the browser. And this apparently happens only with URL from sets, but not single photos, these will work fine.
e.g:
http://www.flickr.com/photos/albionharrisonnaish/14436191205/in/set-72157642936095895 (Loads fine)
http://www.flickr.com/photos/albionharrisonnaish/sets/72157642936095895/ (Won't load)
Could this be sc.embedder using an old oembed version or anything like that?

Also, it won't work with HTTPS (which normally IS in the regular URL the user will copy from the address bar), collective.oembed says: "There are no endpoints available for [URL with https]". And by the way, this message is only displayed in our log. There is no cue on the front-end so the end user may understand what is happening.

Last but not least, we get a Plone ValueError: unknown url type, when we ommit HTTP:// or HTTPS:// from the url. Like this: http://pastebin.com/nLpQZVW3

I understand these problems might be slightly different, though I think it may be fine to open only one issue to address them. If not, I can open it separately too.

@hvelarde
Copy link
Member

please open one issue per problem found; that will make it easier to fix them.

@hvelarde
Copy link
Member

hvelarde commented Mar 9, 2015

@jeanferri, any news on this?

@cfviotti
Copy link
Author

@hvelarde, nothing new until now, I've opened separate tickets for each problem and simplified the description. Issue #18 and Issue #19

@hvelarde
Copy link
Member

all problems reported have now an individual issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants