Bug 7810 - Google Embedded Viewer plugin doesn't fail properly wrt certain access settings
Google Embedded Viewer plugin doesn't fail properly wrt certain access settings
Status: ASSIGNED
Product: OJS
Classification: Unclassified
Component: User Interface
2.4.x
All All
: P3 normal
Assigned To: Matthew Crider
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-29 16:00 PDT by James MacGregor
Modified: 2012-09-25 13:38 PDT (History)
3 users (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2012-08-29 16:00:45 PDT
The Google Embedded Viewer plugin requires non-restricted access to PDFs in order to display content (because the PDFs are ingested by Google and subsequently displayed in a frame). If I choose either of the two Additional Site and Article Access Restrictions under Journal Setup Step 4.1, the embedded viewer can't display the PDF and instead displays the following: 

Sorry we were unable to find the document at the original source. Verify that the document still exists. You can also try to download the original document here.

... at the very least, the "here" link does link to the PDF source file, which any logged in user can download. But maybe there should be a check in the plugin itself to see/warn if those access restrictions are enabled. 

This also appears to be an issue when subscription protection is enabled and the PDF in question is protected -- I could probably get around this by "subscribing" the IP address or site of the Google Docs Viewer, but maybe this should be built in by the plugin. Of course, there's also the problem of letting Google scrape your subscription-protected content ... so maybe, again, the plugin should just throw a warning or not enable if any of these access restrictions are encountered.
Comment 1 James MacGregor 2012-08-29 16:20:05 PDT
The comments here probably apply equally to the Zoho Viewer plugin. Additionally, not sure if either of these plugins check to see if another Viewer plugin has been enabled, but they probably should.
Comment 2 Matthew Crider 2012-08-30 16:03:28 PDT
I think this is best resolved by adding new text for the plugin stating that articles must be open access for the viewers to work.  I wouldn't want to mess around with auto-subscribing google or anything like that -- I'm not sure what they do with the articles but if they are closed access I wouldn't want Google touching them.  Also, you can't change the error message that appears in the viewer itself (at least for the Google Viewer), but we could disable the plugin if articles are not open access (and use the standard embedded viewer).  I don't know if we want to do this this late in testing though...  Alec?
Comment 3 Alec Smecher 2012-08-30 16:15:54 PDT
The standard way around this is to use IP-based subscriptions to allow transparent access to those external services. I think this is a documentation issue more than anything else, but it's too late to add new text for 2.4.0.