Hi Clay, It looks like a mix of circumstances have caused this problem.
When a link is added to the system, we first of all check if the website allows for embedding or not using a HEAD request. If the website doesn't allow for embedding, the UI will display a notification with the link to the website instead of trying to embed the actual website on the page. In this case, it looks like the HEAD request connection is not being closed properly for some reason, which causes an error to be reported and the UI to fall back to its default behaviour. We haven't figured out why exactly the connection isn't being closed, so I've created a GitHub ticket [1] to follow up on this. Once the content metadata widget is available, we will also have a place where you can consistently get hold of the URL. [1] https://github.com/oaeproject/Hilary/issues/667 Hope that helps, Nicolaas On 30 Sep 2013, at 13:13, Clay Fenlason <[email protected]> wrote: > I'm using the OAE for a small class at Georgia Tech, and it's working well > for the most part, but we're running into an issue I'm having a hard time > working out how to report: it seems part design, part technical limitation, > and maybe a bug is lurking in the background, I don't know. > > So instead of a rambling and mis-classified github issue, I thought I might > try to capture the overall UX frustration in a video here, and hope that it > will be useful. > > http://screencast.com/t/ugQCNgaCY > > It may be that the new content metadata widget solves these issues already, > but just wanted to note this while I was struggling with it. > > ~Clay > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
