There is no "view" switch for the Connector block, just a "list", which means that it cannot be seen.

I have (perhaps successfully) added a twitter oauth provider, but can't figure out what methods I could use, etc.

Great looking code, but not documented!

Peace
glass.dimly

Comments

glass.dimly’s picture

Component: Code » Documentation

voxpelli

Great module, like I said. We are in need of an abstracted API.

The most important thing for an API to be usable is documentation. So I'd love to see some documentation so that your module can become used. If I can get this module working with Twitter, I will create a blog entry over at echodittolabs.com, which will include a tutorial.

But I need comments on the code, first!

Peace,
glassdimly

voxpelli’s picture

The block works as far as I know - if it didn't then I wouldn't have been able to test the code at all.

Regarding Twitter - check out this example export: http://gist.github.com/545469

I know the documentation is lacking.

yivich’s picture

I am having the same problem, I've added the block to a region but nothing appears where it should be. I tried several regions but it never shows up.

Update/correction: I can see the block when I'm not logged in, but if I am logged in (regardless of whether I've made a connection to the outside resource or not), the block isn't visible. Perhaps you intended it to work this way?

voxpelli’s picture

@yivich: Currently the Connector module can only manage one connection per user - I'm working on extending it to work with multiple connectors the way that Twitter.module currently handles that. Due to Connector only handling one connection the block is only useful to log in people and therefor it only makes sense to view the block for non-logged in users.