Install
Works with Drupal: 7.xUsing Composer to manage Drupal site dependencies
Downloads
Download tar.gz
14.75 KB
MD5: 6a53713cb9c22b308ce7df453bcefb37
SHA-1: cd3e47f1739ceabd826ba0de317f27dda5b806ed
SHA-256: 5c2dfc1eb3a12094d710b5e522bc1e06182a8793bd064365eeea6df0f5cdb763
Download zip
17.18 KB
MD5: 188e9e1621d90e6558b3ee419d764c7b
SHA-1: 615607c3a1e4baa4317e18d626e7d90f98cc1ba1
SHA-256: bce25e2a4825cb2d60d90c1f537aa5030b3087bb7fedfa0dd1cc6afb7bf991d0
Release notes
With the Twitter API v1 going away (see #1933164: Twitter API v1 is going away on May 7) Twitter Block 1.x will no longer function after June 11, 2013.
The initial release of Twitter Block 2.x which utilizes Embedded Timelines instead of the deprecated and soon to be shut-down Twitter API v1.
Unfortunately, due to a number of factors including:
- The embedded timelines API requires that each timeline have a unique ID. These IDs can only be generated by manually creating embedded timelines by visiting your widgets settings page on twitter.com.
- The "type" of Embedded Timeline is now tied to the Widget ID (it must be specified when creating a new Embedded Timline) and is not simply a parameter passed to the API.
- The Block module's lack of standard or update versions of functions to programatically create or update custom blocks.
- The fact that not even a single configuration option is shared between the old Twitter v1 search and REST APIs and the new Embedded Timelines API.
There is no way to provide an automatic upgrade path from Twitter Block 1.x.
Upgrading to Twitter Block 2.x will remove all of your existing Twitter Block blocks. You must manually recreate your blocks using the new process required by Embedded Timelines.