Needs work
Project:
Drupal for Facebook
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Jun 2012 at 01:44 UTC
Updated:
20 Mar 2013 at 04:05 UTC
Jump to comment: Most recent file
Comments
Comment #1
decipheredPatch (sponsored by Realityloop Pty Ltd) attached.
Comment #2
oadaeh commentedBased on Deciphered's comments and lack of comments from Dave Cohen, I'm curious as to the reality of modifying this module to work w/Features and/or CTools exportables.
Comment #3
Dave Cohen commentedI appreciate the patch contribution. I'm not a user of features or exportables. If your post had said, "I tried the patch. It does the job. No bad side effects whatsoever." That might be enough to get it pushed to git.
In short, it needs review but I'm not the best guy to review it. I apologize for not saying so sooner.
Comment #4
oadaeh commentedI tried the patch earlier today. It does not apply cleanly, as it is several months old.
I manually applied the changes, and it mostly worked, but there is one aspect that does not.
If I have time, I will attempt to correct the one thing and submit an updated patch, although based on @Deciphered's initial statements, I'm sure there will be lots more needing to be done for full integration.
Mostly Dave, after nine-and-a-half months with no word, I wanted to know if movement on this was at all likely.
Comment #5
Dave Cohen commentedI'm not likely to drive it, nor to resist it.
Not sure it will ever work as desired. The basics of app configuration, the apikey and secret, really shouldn't be copied from one site to another.
The 4.x branch of this module is cleaner, and should remain cleaner. It might be easier there to export the parts that really should be exportable. Things like access tokens, app ids, secrets... I just don't think those are meant to be exported.