While you provide a link to an export for the twitter oauth, there is no way to actually import it.

I suppose I could've created a module to set it up as a default export, but that's quite a bit of trouble to do. Also, it wouldn't have been effective, since the export doesn't include the necessary API keys.

The ultimate answer is that there probably needs to be some kind of wizard to handle the really common oauth providers. The simpler answer, for now, is to at least create an import link and provide instructions for getting the necessary twitter API key.

Comments

merlinofchaos’s picture

merlinofchaos commented

As I think on it, the actual proper way to do it is to have twitter_oauthconnect as a module that provides a default provider but only once the api key is configured. In addition, the provider object could be expanded a little bit so that the twitter connect module could provide a fancy graphic like the facebook connector you've got on github.

jlyon’s picture

jlyon commented

While I think the current method of forcing site builders to create a new profile makes sense in a lot of cases, I am currently testing migrations and building a profile with features, so I am rebuilding a site every couple weeks. After each rebuild, I had to reconfigure my FB oauthconnector: creating the fields, and configuring the profile. Eventually I dumped all of the oauthconnector-related sql and imported that after every site build. It would have been great if I could have included my fb profile (maybe everything up to the actual app keys) in one of the feature features.

Another issue I have run into, is that I cannot include connector-related permissions (Connect with Facebook) to features because the connections do not exist.

Is there any particular place in the code or reference you can recommend for looking at getting this import working? I'm assuming it just uses ctools export.

frans’s picture

frans commented

As I think on it, the actual proper way to do it is to have twitter_oauthconnect as a module that provides a default provider but only once the api key is configured

I do share that vision. in 7.x there are presets, but that is not the best solution... (patches welcome)

The exports are build with ctools. I don't have developer experience with ctools and the current implementation is the better-copy-paste work. Again patches welcome...

jlyon’s picture

jlyon commented

Thanks. I'll try to look into this in the next week or two.