WeChat-Django

To use wechat_django.models.WeChatUser as your primary user model for Django authentication, you must prevent Django from attempting to update the last_login field, as WeChatUser does not contain this field.

Failure to do this will cause errors during the automatic update_last_login process triggered by the user_logged_in signal.

To fix this, disconnect the update_last_login signal in your AppConfig.ready() method. Once disconnected, you can use standard django.contrib.auth.login to authenticate users.

# In your app's apps.py
from django.contrib.auth.models import update_last_login
from django.contrib.auth.signals import user_logged_in
from django.apps import AppConfig

class YourAppConfig(AppConfig):
    name = 'your_app'

    def ready(self):
        # Prevent Django from trying to update last_login on WeChatUser
        user_logged_in.disconnect(update_last_login, dispatch_uid='update_last_login')

The '自动回复管理' (Auto-Reply Management) module allows you to manage how the system responds to incoming messages.

Synchronizing Replies

You can use the '同步' (Sync) action to import all auto-replies currently configured in the WeChat Official Account backend. Warning: Every time you re-sync, any auto-replies that were synced from WeChat but have not been edited in this system will be removed.

Editing Replies

Each auto-reply can be configured with:

• Enabled/Disabled status
• Log recording (whether to log the interaction)
• Reply Strategy

Rules

An auto-reply can contain one or more rules. When an incoming message matches any rule, the system executes the associated reply strategy. Note: Once a rule is matched, the system stops checking any remaining rules or other auto-replies for that message.

Reply Strategies and Execution

• 全部回复 (Reply All): Executes all configured replies in sequence.
• 随机回复 (Random Reply): Randomly selects and sends one of the configured replies.

Critical Constraints:

1. Uncertified Accounts: For uncertified accounts, 'Reply All' will execute all logic, but WeChat will only successfully deliver the last reply in the sequence.
2. Message Type Limits: Per WeChat regulations, for text, image, video, article, and location messages, you can only reply with a maximum of one article. To ensure articles are sent correctly, place the article reply as the last item in your reply sequence.

To use WeChat JS-SDK features (like sharing) in a web application, you must first include the official WeChat JS file and then include the configuration script provided by wechat-django to initialize wx.config with the correct signature and parameters.

1. Include the WeChat JS file

Add the official WeChat JS library to your HTML:

<script src="//res.wx.qq.com/open/js/jweixin-1.4.0.js"></script>

2. Include the wechat-django configuration script

You need to load the configuration generated by the package. The jsApiList parameter must include all JS interfaces you intend to use.

If using Django Templates: Use the wechat_django:jsconfig URL name. Pass the required interfaces via the jsApiList query parameter.

<script src="{% url 'wechat_django:jsconfig' 'debug' %}?jsApiList=onMenuShareTimeline,onMenuShareAppMessage&debug=1"></script>

If NOT using Django Templates (Static/Direct URL): Use the direct path pattern: /wechat/<yourappname>/wx.config.js. Replace <yourappname> with your actual Django app name.

<script src="/wechat/{{yourappname}}/wx.config.js?jsApiList=onMenuShareTimeline,onMenuShareAppMessage&debug=1"></script>

Parameters

• jsApiList: A comma-separated list of the JS interfaces you need (e.g., onMenuShareTimeline,onMenuShareAppMessage).
• debug: Set to 1 to enable debug mode. This will only function if settings.py has DEBUG = True.

<!-- Example for Django Templates -->
<script src="//res.wx.qq.com/open/js/jweixin-1.4.0.js"></script>
<script src="{% url 'wechat_django:jsconfig' 'debug' %}?jsApiList=onMenuShareTimeline,onMenuShareAppMessage&debug=1"></script>

If the default request client does not meet your requirements (e.g., you are interfacing with a third-party WeChat API instead of the official one), you can implement a custom client by subclassing WeChatClient and using a Django Model Proxy to inject it into WeChatApp.

Steps:

1. Define a custom client by inheriting from wechat_django.client.WeChatClient.
2. Create a proxy model for wechat_django.models.WeChatApp by setting proxy = True in the Meta class.
3. Override the _get_client method in your proxy model to return an instance of your custom client.
4. Use the proxy model to retrieve app instances instead of the original WeChatApp model.

from wechat_django.client import WeChatClient
from wechat_django.models import WeChatApp

# 1. Define custom client
class CustomWeChatClient(WeChatClient):
    def _fetch_access_token(self, url, params):
        return dict(
            access_token="1234567",
            expires_in=60*30
        )

# 2. Implement proxy model
class CustomWeChatApp(WeChatApp):
    class Meta:
        proxy = True

    def _get_client(self):
        return CustomWeChatClient(self)

# 3. Use proxy to get app instance
app = CustomWeChatApp.objects.get_by_name("111")