[LRA-203] Google Drive Quick Links App does not function after initial local setup Created: 14/Oct/14  Updated: 18/Mar/15  Resolved: 18/Mar/15

Status: Closed
Project: Liferay Apps
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major
Reporter: mcalvo Assignee: Andres Lizano [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I'm attempting to set up the Google Drive Quick Links App on a local development machine.
After going through the setup instructions here: http://wiki.rivetlogic.com/display/LRA/Google+Drive+Quick+Links

I go back to the portlet places on one of my pages and do not see any responsiveness from the portlet when clicking on the 'select file' button.
Also, I do not see any errors appearing in the server logs.

 Comments   
Comment by keller [ 22/Oct/14 ]
I tried leveraging a public URL that resolved to 127.0.0.1 instead for my OAuth client ID generation, but did not see any changes in the app behavior.
Comment by potte [ 07/Nov/14 ]
I am facing the same problem currently. Also, by inspecting the network traffic with firebug, a 404 error is thrown when clicking on the "select file" button.
Comment by mcalvo [ 13/Mar/15 ]
Hi Andres, please check if you can reproduce the issue in the latest versions of Liferay CE and EE. I think at this moment they are: CE ga 3 and EE sp10:
http://www.liferay.com/downloads/liferay-portal/available-releases

Get the code from here:
https://github.com/rivetlogic/liferay-google-drive-quick-links

The documentation of this app is here, it explains how to setup it:
http://wiki.rivetlogic.com/display/LRA/Google+Drive+Quick+Links

Here are the best practices we follow when developing these apps:
http://wiki.rivetlogic.com/display/HRPORTAL/Development+ready+checklist
http://wiki.rivetlogic.com/display/HRPORTAL/Liferay+UI+and+Javascript+Good+Practices/Liferay+UI+and+Javascript+Good+Practices
Comment by mcalvo [ 18/Mar/15 ]
Andres fixed it by upgrading to the latest version of the api.js file.
Generated at Sat Feb 10 05:49:20 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.