1. Platform – Settings – Mail Settings – Message template, let the template content support traditional Chinese implementation (mail_msg_temlates: mail template Add template ID field (APP cloud communication SMS template): temp_id_app Add traditional fields (SMS traditional template content (cloud piece SMS template): content_zh_tw), as shown in Figure 1:

Add traditional fields (SMS traditional template content (cloud piece SMS template): content_en_tw

2. Added the function of the email template function, as shown in Figure 2;

Implementation of the function of adding email templates

3. Mail template data, as shown in Figure 3, 4, 5:
(1) Medical management pass mobile phone registration: 96255 (Hydratone communication) 93122 (APP)
[Namanage] You are registering a medical management account, the verification code {1}, please submit the verification code according to the page prompt within {2} minutes. Note: Cloud Communication SMS Template
[Namanty] You are registering a medical management account, the verification code #code#, please submit the verification code according to the page prompt within #minute# minutes. Note: Cloud piece SMS template

【{$site_name}】You are registering a medical account number, the verification code {$verify_code}, please submit the verification code according to the page prompt within {$minute} minutes. Note: The content of the template in the database
【{$site_name}】You are registering a medical account number, the verification code {$verify_code}, please submit the verification code according to the page prompt within {$minute} minutes. Note: The content of SMS traditional template in the database (cloud piece SMS template)

Figure 3: 96255 (Hydthene), cloud communication SMS template

Figure 4: (Hydthene), cloud piece SMS template

4. Platform – Settings – Region Settings, Editing Region, Editable International Regional Code Prefix (Area: Area Table Add Fields International Area Code Prefix: Area_Mobile), as shown in Figure 5:

Mainland China +86 0
Taiwan +886 32

Ali Cloud
ALTER TABLE `TRADE_AREA` add column `area_mobile` VARCHAR(5) Character set UTF8 COLLATE UTF8_GENERAL_CI NOT NULL commentInternational area code prefixafter `area_region`;

Editing area, editable international area code prefix (area: area table add field international area code prefix: area_mobile)

5. Trade.service.ygt.cm

http://trade.service.ygt.cm/area/get-area-mobile

http://trade.service.ygt.cm/area/get-area-mobile?area_id=32

6. Implement editable user mobile and area_id in ucenter, as shown in Figure 6:
(1) Add the international regional ID field in the user table: area_id, mobile and area_id are combined together with uniqueness
alter table `kcuc_members` add `area_id` int(11) unsigned not null default0commentCountry code IDafter `mobile`;
(2)http://kcuc.ygt.cm/Pass background, add and edit user mobile, support the selection of international region name and number prefix list
User Management – Add Users, Edit Users
(3) User management is arranged in reverse order based on user ID
(4) User management – search for users, support the selection of national area codes

Figure 6: Internationalization only supports mainland China and Taiwan for the time being

7. The user interface in the client of UCenter can display and edit the user’s mobile and area_id, as shown in Figure 7:
(1) Check the mobile address (UC_USER_CheckMobile)
(2) User registration (UC_USER_REGISTER), the mobile phone supports the selection of national area codes
(3) Get user data (UC_GET_USER)
(4) Update user information Based on user ID (UC_USER_UIDEdit), the mobile phone supports the selection of national area codes
(5) The API interface updates user information, and the mobile phone supports the national area code
(6) Business system – background – platform – member – member management – member management, new and edit members
alter table `trade_member` add `member_area_mobile` int(11) unsigned not null default0commentCountry code IDafter `member_email_bind`;
(7) Business system – background – mall – member – member management – new and edit members

Figure 7: The user interface in the client of UCenter can display and edit the user’s mobile and area_id

8. Mobile phone registration, the mobile phone supports the selection of national area codes
(1) Add the international regional ID field in the mobile phone SMS record table: log_area_mobile, log_area_mobile and log_phone are unique, as shown in Figure 8:
alter table `trade_sms_log` add `log_area_mobile` int(11) unsigned not null default0commentCountry code IDafter `log_id`;

Figure 8: Add international region ID fields to the mobile phone SMS record table

(2) Send SMS to support mainland China and Taiwan (based on cloud communication and cloud slices), as shown in Figure 9, 10, and 11:

Figure 9: Realize the command space and automatic loading of cloud slices, and call the service layer: get the national area code list

Figure 10: Selection of SMS sending service provider

Figure 11: Send template SMS, Ronglian Cloud; send a single SMS, cloud piece (smart matching)

(3) Realization of mobile phone registration, support internationalization

Figure 12: AJAX verification: whether it is an overseas mobile phone

Figure 13: Ajax verification: whether it is a Taiwanese mobile phone

Figure 14: Ajax verification: whether the phone has been registered

Figure 15: Ronglian Cloud SMS

Figure 16: SMS sent to Taiwan mobile phone number, traditional Chinese

9. The member list in the background of the shopnc, as shown in Figure 17:

Figure 17: Member list of shopnc background

1. To realize WeChat login in the WeChat client, the QR code scanning layer will pop up, which should be canceled and directly jump to the authorization page, as shown in Figure 1:

Implement WeChat login in the WeChat client, and pop up the QR code scanning layer

2. In the mobile browser, the QR code scanning layer will pop up, and an error will be reported after scanning, as shown in Figure 2:

In the mobile browser, the QR code scanning layer pops up, and an error is reported after scanning

3. Background – Platform – Members – Account Synchronization – WeChat public platform, as shown in Figure 3:
Execute SQL:
Insert into `trade_setting`(`name`, `value`) values (mp_weixin_isuse,1)
Insert into `trade_setting`(`name`, `value`) values (mp_weixin_appid,WX5C318E640E87F7E8)
Insert into `trade_setting`(`name`, `value`) values (mp_weixin_secret,1F436A3A0DBFDAC1C8E1C8F72D2FBEC)

Background – Platform – Members – Account Synchronization – WeChat Public Platform

4. Use Detector to detect the browser, the URL:http://detector.dmolsen.com/, it can automatically adapt to the new browser, version and device to use unique user agent characters for each browser, based on Modernizr, as shown in Figure 4:

Use Detector to detect the browser, the URL:http://detector.dmolsen.com/

5. Copy the directory lib/detector to core/framework/detector, as shown in Figure 5:

And set the directory: user-agents/core/, user-agents/extended/, config is writable;

Copy directory lib/detector to core/framework/detector

6. The rules are formulated as follows, the code in the controller and template file is shown in Figure 6 and 7:

(1) PC, Tablet: pop up the QR code scanning layer (here WeChat open platform, website application);

(2) Mobile browser: hide;

(3) Mobile client: directly jump to the authorization page (here WeChat public platform, service number);

36kr.com: The mobile terminal does not currently support WeChat login, please use the bound mobile phone or mailbox to log in.
Dianping.com: Hide WeChat login button (use this scheme);

code in controller file

code in template file

7. Under the Mobile client, the code to directly jump to the authorization page is shown in Figure 8:

Under the Mobile client, jump directly to the code of the authorization page

8. Under the Mobile client, jump directly to the page of the authorization page, as shown in Figure 9:

Under the Mobile client, jump directly to the page of the authorization page

9. Error when submitting SVN, as shown in Figure 10:

The working copy at

is too old(format 10) to work with client version1.8.10(R1615264)(Expects format 31).You need upgrade the working copy first.

The working copy at is too old(format 10) to work with client version1.8.10(R1615264)(Expects Format 31)

10. Delete all .svn directories under core/framework/detector to prevent svn conflicts, and the submission is successful, as shown in Figure 11 and 12:

Delete all .svn directories under core/framework/detector to prevent svn conflicts

SVN submission was successful

11. Under the Edge browser, the error is reported, as shown in Figure 13:

script16389: Unspecified error.

Under the Edge browser, an error is reported: script16389: Unspecified error.

12. Open the URL:http://detector.dmolsen.com/, I found that I also have this error, as shown in Figure 14:

Open URL:http://detector.dmolsen.com/, found this error too

13. The solution is based on $_SERVER[‘HTTP_USER_AGENT’], if it is IE10, IE11, Edge, then detector is not used to detect the browser, as shown in Figure 15:

Based on $_SERVER[‘HTTP_USER_AGENT’], if it is IE10, IE11, Edge, then detector is not used to detect the browser

1. The request code of $.getjson is shown in Figure 1.0

The request code of $.getJSON is shown in Figure 1.0

2. Check the network and find that in the response cookie, a new phpssssid is generated, as shown in Figure 1.1

Check the network and find that in the response cookie, a new phpssssid is generated, as shown in Figure 1.1

3. Add to the request address of $.getjson: &callback=?, which is equivalent to setting the request format to jsonp, as shown in Figure 1.2

Add to the request address of $.getJSON: &callback=?, which is equivalent to setting the request format to jsonp, as shown in Figure 1.2

4. Check the network and find that the request cookie has been consistent with the current URL, as shown in Figure 1.3

Check the network and find that the request cookie has been consistent with the current URL, as shown in Figure 1.3

5. The post request under $.ajax, the code is as shown in Figure 2.0

The POST request under $.ajax, the code is shown in Figure 2.0

6. Check the network and find that in the response cookie, a new phpssssid is generated, as shown in Figure 2.1

Check the network and find that in the response cookie, a new phpssssid is generated, as shown in Figure 2.1

7. js code implementation: datatype:jsonp,CrossDomain: true, as shown in Figure 2.2

JS code implementation: dataType:jsonp,CrossDomain: true, as shown in Figure 2.2

8. Check the network and find that the request cookie has been consistent with the current URL, but the POST request has been converted into a GET request, as shown in Figure 2.3

Looking at the network, it is found that the request cookie has been consistent with the current URL, but the POST request has been converted into a GET request, as shown in Figure 2.3

9. js code implementation: datatype:json,xhrfields:{withcredentials:true},crossDomain: true, as shown in Figure 2.4

JS code implementation: dataType:json,xhrfields:{withcredentials:true},crossDomain: true, as shown in Figure 2.4

10. PHP code implementation:
header(“access-control-allow-credentials: true”);
header(“access-control-allow-origin: ” . c(wap_site_url) . “”);

where c(wap_site_url) is the value of:http://mall.m.ygt.cm, as shown in Figure 2.5

PHP code implementation:
header(“access-control-allow-credentials: true”);
header(“access-control-allow-origin: ” . c(wap_site_url) . “”);
where c(wap_site_url) is the value of:http://mall.m.ygt.cm, as shown in Figure 2.5

11. Check the network and find that the request cookie has been consistent with the current URL, as shown in Figure 2.6

Check the network and find that the request cookie has been consistent with the current URL, as shown in Figure 2.6

12. The code implementation of document.cookie in js: domain=.ygt.cm; as shown in Figure 2.7

The code implementation of document.cookie in js: domain=.ygt.cm; as shown in Figure 2.7

13. The POST request under $.ajax, the code is as shown in Figure 3.0, and the format is jsonp; in fact, you can also use a processing scheme consistent with the post request under $.ajax, use the format json, and then set xhrfields