-
[Facebook::RailsUtil] Some methods are renamed. For example,
rc_facebook_write_rg_fbs
is renamed torc_facebook_write_fbs
. All renamed methods are considered private, so we're not listing them here. -
[Facebook::RailsUtil]
rc_facebook_storage_key
is changed to:"rc_facebook_#{rc_facebook.app_id}"
, your users might need to login again in order to save the access_token into the new place.
-
[Github] Fixed usage of Oauth2Query.
-
[Facebook] Now we're using POST in
authorize!
to exchange the access_token with the code instead of GET. If we're using GET, we would run into a risk where a user might use the code to get other people's access_token via the cache. Using POST would prevent this because POSTs are not cached. -
[Facebook::RailsUtil] Fixed a serious bug. The bug would jump up if you're using :write_session or :write_cookies or :write_handler along with :auto_authorize, for example:
rc_facebook_setup(:auto_authorize => true, :write_session => true)
The problem is that Facebook::RailsUtil is not removing the invalid access_token stored in session or cookie, and yet it is considered authorized, making redirecting to Facebook and redirecting back doesn't update the access_token.rc_facebook_cleanup
is introduced to remove all invalid access_tokens, which would get called once the user is redirected to Facebook, fixing this bug.
-
[Facebook] Now we use
default_data
to get the default data, instead of relyingDefaults
middleware. -
[Facebook] Protected methods are changed to private.
-
[Flurry]
app_info
now accepts opts. -
[Flurry]
event_metrics
is renamed toevent_summary
-
[Flurry]
event_metrics
is now the API for accessing 'eventMetrics/Event' -
[Flurry] If you didn't pass dates, now default to for 7 days.
-
[Flurry] Instead of overriding
query
, definingdefault_query
-
[Linkedin+Twitter] Removed
Defaults
middleware because now we're using the data fromOauth1Client
instead. -
[Linkedin+Twitter] Removed
oauth_token
,oauth_token=
,oauth_token_secret
, andoauth_token_secret=
because we're using them fromOauth1Client
instead. -
[Linkedin+Twitter] Removed
set_token
because it's handled inOauth1Client
now. -
[Twitter::RailsUtil] Now
rc_twitter_setup
accepts options likerc_facebook_setup
:auto_authorize
,ensure_authorized
,write_session
,write_cookies
,write_handler
, andcheck_handler
. -
[Mixi] Removed
Defaults
middleware in favor ofdefault_data
. -
[Facebook+Github+Mixi+Twitter] Added a
me
method for accessing current user information.
- [Facebook::RailsUtil] Fixed a missed change which should be made.
- [Flurry] renamed
api_key
toapiKey
to better match the original name from flurry. Also renamedaccess_code
toapiAccessCode
. - [Facebook::RailsUtil] Some
module_function
s are changed to controller's private methods. You aren't using it if you don't know what does this mean.
- Added
rib-rest-core
command line tool, extracted from rest-core. - [RailsUtilUtil] Introduced this to ease the pain writing RailsUtil for various clients.
- [Bing] Added Bing client and its RailsUtil.
- [Github] Added RailsUtil for Github client.
- [Linkedin] Added RailsUtil for Linkedin client.
- [Mixi] Added RailsUtil for Mixi client.
- [Twitter] Added RailsUtil for Twitter client.
- [Mixi] Fixed
RC::Mixi.new(:access_token => 'access_token')
which is not working before.
-
[Mixi]
RC::Mixi#authorize!
now works likeRC::Facebook#authorize!
That is now we pass code like this:mixi.authorize!(:code => code)
-
RestCore::Config
andRestCore::RailsUtilUtil
are now moved to rest-more
- Extracted from rest-core 0.4.0
- [Facebook] Added
RC::Facebook#parse_fbsr!
which can parse Facebook's new cookie. Also,RC::Facebook#parse_cookies!
would look for that too. - [Facebook] Fixed that parsing an invalid signed_request would raise an error. From now on it would simply ignore it and wipe out the data.
- [Flurry] Some minor updates.