Active
Project:
Droogle
Version:
7.x-4.0-beta15
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
25 Feb 2012 at 21:23 UTC
Updated:
17 Feb 2016 at 06:41 UTC
Jump to comment: Most recent
Comments
Comment #1
barnettech commentedYou can either have 2 cck fields for OG or 1. If you just have 1 cck field, it is for the username. So for the group content type, just add a cck field called google_username for the machine name. Add this to the droogle settings page, then configure the cck field. Then you can either have a 2nd cck field for google_password and then for each organic group you can configure a separate password, or you can not use a cck field for the google_password if you opt for a universal password for all organic groups. For example at Babson we don't use a different password for each organic group. We have google for education and we have admin status and just set the same password for each google account associated with each organic group -- then in the droogle admin pages we just put in the universal google groups password.
I hope this helps explain how you might choose to use this module.
Comment #2
barnettech commentedLet me know if you still have questions on this.
Comment #4
aruhdom commentedHi,
Cannot get Droogle to work with organic groups for D7. The new client id and client secret is not being authenticated..as the global droogle refresh token is taken into consideration and authentication fails.. How to do it now?... For every client id and client secret should there be a 3rd field refresh token and all these 3 fields should override the global settings?
Comment #5
aruhdom commentedI have added two fields to group content types, and for a particular group filled them with a different client id and secret. But I get the same file list everywhere. I dont think the new client id and secret is overriding the global fields.Please help to integrate droogle for OG.