Skip to content

Releases: Eric-Guo/wechat

v0.7.10

18 Apr 00:15
Compare
Choose a tag to compare
  • allow wechat_config_js even user not declare wechat_api at controller for #104

v0.7.9

12 Apr 14:05
Compare
Choose a tag to compare
  • wechat_oauth2 support public account now.
  • Refresh and store state on jsapi ticket, using it on oauth2_url to more secure.
  • Remove extra sending payload in message template send json
  • Allow setting oauth2_cookie_duration in config

v0.7.8

31 Mar 05:53
Compare
Choose a tag to compare
  • New wechat_api, similar to wechat_responder, but without messange handle DSL, support web page only wechat application
  • New media_uploadimg API.
  • New file type of Message.
  • Improved multi account support per different controller.

v0.7.7

18 Mar 12:32
Compare
Choose a tag to compare
  • New wechat_oauth2, only support enterprise account still.
  • fix 'skip_before_action :verify_authenticity_token' bug for v5.0.0.beta3 by @vkill #97
  • Support Rails 3.2 again after support Rails 5.0, by @guange2015 #96

v0.7.6

05 Mar 15:35
Compare
Choose a tag to compare
  • Support wechat public account conditional menu. #95

v0.7.5

21 Feb 15:04
Compare
Choose a tag to compare
  • New wechat_config_js to simplify the Wechat jsapi config.
  • Support sent shortvideo.

v0.7.4

24 Jan 03:26
Compare
Choose a tag to compare
  • Add Redis store token/ticket support, close #76, #60
  • Rails 5 support without deprecate warning or other not necessory call. #82

v0.7.3

24 Jan 03:27
Compare
Choose a tag to compare
  • Allow transfer_customer_service to specific account.
  • New customservice_getonlinekflist API.
  • session support class WechatSession no need table_exists? methods exist.

v0.7.2

24 Jan 03:27
Compare
Choose a tag to compare
  • Optional session support by @zfben #81, #88, #91
  • Replace after_wechat_response with Rails Nofications facility, by @zfben, original issue is #79
  • New user_batchget API. #89
  • Support Rails 3.2 again after support Rails 5.0. by @guange2015 #87
  • Fetch setting from RAILS_ENV first, then fetch default. by @kikyous #85
  • Warning not support on :scan with regular expression, reason see #84

v0.6.10

24 Jan 03:28
Compare
Choose a tag to compare
  • Support Rails 3.2 again after support Rails 5.0. by @guange2015 #87
  • Fetch setting from RAILS_ENV first, then fetch default. by @kikyous #85
  • Warning not support on :scan with regular expression. by @kikyous #84