Twitter REST API 1.1

(Tom Chadwin) #1

Hello all

 

Has anyone managed to incorporate a call to the Twitter API 1.1? 1.0 is being discontinued at some stage, I believe. Never having used any of the REST assets, let alone the oAuth side of things, I'm struggling.

 

Thanks

 

Tom

(Tom Chadwin) #2

Anyone? I've resorted to using the vile JS widget instead unless I can crack this.

 

Thanks

 

Tom

(Nic Hubbard) #3

You say you are trying to use the REST Resource asset?

(Tom Chadwin) #4

Yes, with an associated REST resource oAuth asset.

(Tom Chadwin) #5

Has anyone got this to work?

 

Tom

(Nic Hubbard) #6

Has anyone got this to work?

 

Tom

 

I have never personally used the REST Resource asset, but if you could explain how you are trying to set it up I could try to replicate the issue and see if I can get something working.

(Nic Hubbard) #7

Has anyone got this to work?

 

Tom

 

Tom, did you get this working yet? 

 

I just realized there is an example of this in the Manuals: http://manuals.matrix.squizsuite.net/web-services/chapters/rest-resource-assets#Example

(Anthony) #8

Our site's twitter feed disappeared the other week too, when twitter turned off 1.0. I tried following the instruction in the manual page but couldnt get it to work... close... but not close enough!

 

It was step 3 that I got stuck on... visitng the URL brought up the Twitter login screen but when going back into Squiz it had never captured the token details so where it says

"the token details will be displayed in the Access Token field. Enable the Store Access Token field and click Commit"

 

was not possible.  Annoyingly, my Twitter account showed it had generated the token, and were the field in Squiz to be visible / editable I could have pasted them across. I pressed on with the other steps but of course the only return I ever got was something like "not authorised". I even deleted my Twitter "app" and creatd it all over again just to be sure.

 

I'm on version 4.4.2 so I just guessed the necessary OAuth stuff wasnt sufficiently mature in that version. I've made a note to return to it later in the year after I get Squiz upgraded, in the meanwhile I embedded the Twitter Widget (which actually I think looks OK as long as you configure some of the options to resize it, hide the headers, colour the links etc.

(Tbaatar) #9

I also get the same issue for step 3 as the token is empty.

 

The two legged approach works however it is OAuth 1.0.