That's possible. Unfortunately these Twitter transformers are a little at the mercy of the API and if it changes then it can cause problems. Last year I had a similar problem with the TweetSearcher that was partly an API issue and partly the fault of the transformer. I suggest you download the latest FME, (released at the start of the week) and add the transformer to your workspace again. It's possible that it has been tweaked already to react to the API, check the transformer version number if the new and old one:

 

 

http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Transformer_Version_Numbers.htm

 

---

Thanks for the reply Dave. Unfortunately hasn't solved the problem. Updated to 2014 build 14230. This is the error I get when I connect the transformer to a logger.

 

 

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Feature Type: `TwitterStatusFetcher_2_ERROR'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Attribute(32 bit unsigned integer): `_creation_instance' has value `0'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Attribute(encoded: utf-8) : `_tweet_search_result' has value `'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Attribute(string) : `fme_feature_type' has value `Creator'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Attribute(string) : `fme_geometry' has value `fme_undefined'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Attribute(string) : `fme_type' has value `fme_no_geom'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Coordinate System: `'

2014-01-16 13:39:36| 1.4| 0.0|INFORM|Geometry Type: IFMENull

 

 

Will keep an eye out to see if the transformer gets updated in any way from version 6.

 

Daragh

---

You'll be please to know I think your issue is fixed with the new core build that has just been made available after the official release!

 

 

See here the extract from the "what's new":

 

 

 =========================================================================== ========================== BUILD 14234  20140120 ========================== =========================================================================== Twitter: Fixed Twitter transformers to work with the revised Twitter API  (PR#50984 C86283 C86406 C86411)

---

That's possible. Unfortunately these Twitter transformers are a little at the mercy of the API and if it changes then it can cause problems. Last year I had a similar problem with the TweetSearcher that was partly an API issue and partly the fault of the transformer. I suggest you download the latest FME, (released at the start of the week) and add the transformer to your workspace again. It's possible that it has been tweaked already to react to the API, check the transformer version number if the new and old one:

 

 

http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Transformer_Version_Numbers.htm

 

You'll be please to know I think your issue is fixed with the new core build that has just been made available after the official release!

 

 

See here the extract from the "what's new":

 

 

 =========================================================================== ========================== BUILD 14234  20140120 ========================== =========================================================================== Twitter: Fixed Twitter transformers to work with the revised Twitter API  (PR#50984 C86283 C86406 C86411)

---