Alexandre Froger

Hello @academyofmine ,
I am sorry to get back to you so late. There is now an updated version of the plugin, if you are stilling willing to try, please let me know how it goes.
If there are any issues, could you please let me know the exact error message (wether it shows english or chinese)?

Regarding auto renew, WeChat does not support automatic recurring payment. There is one case of this in WeChat ecosystem, and it’s Tencent’s own TV service – it is not open to third party for integration.

Best,
Alex

Hello @lijitimit !
Thank you for reaching out, and apologies for replying so late.
First of all, because it has to communicate with Tencent’s servers, WP Weixin cannot be tested on localhost – it has to be tied to a domain name with an ICP as per China’s cybersecurity law.

Regarding your specific QR code issue, I am not sure how to reproduce: QRcode::png() is a method found in /wp-content/plugins/wp-weixin/lib/phpqrcode/phpqrcode.php. It is included in /wp-content/plugins/wp-weixin/wp-weixin.php *only in case the class* QRcode *does not exist*. Could there be that another plugin is already registering this class name without using namespaces, therefor creating a conflict?

Hi @rccardeployed !

To be able to login with WeChat, the plugin needs to communicate with WeChat API from time to time, and therefore depends on the latency of the communication between your server and Tencent’s servers form time to time (not all the time, caches are in place).

If you could direct me to which area, which case, or which request in particular is slow, I may be able to provide more help. In the meantime, I have tested the WP Weixin plugins with the amazing Query Monitor plugin, and have not noticed any slow query, slow third party call, or duplicate hook and query calls.

Please don’t hesitate to provide more concrete details and I’ll see what I can do to help!

Re: website should be hosted with a certified provider (i.e. Chinese): this is because if the website gathers any data from CHinese nationals, it is required by law to be hosted on the Popular Republic of China’s territory.

Hi @betsykleeverb !

The ICP license is actually a requirement from WeChat: any website communicating with the OA needs to be certified. And as a general rule, according to the cyber-security law of the PRC, the domain name’s registrar should be certified (i.e. Chinese) and the website should be hosted with a certified provider (i.e. Chinese).

I understand it can be quite a pain – this is not a requirement of this plugin in particular, though.

Hi @vmalyshev !

The ICP license is actually a requirement from WeChat: any website communicating with the OA needs to be certified. And as a general rule, according to the cyber-security law of the PRC, the domain name’s registrar should be certified (i.e. Chinese) and the website should be hosted with a certified provider (i.e. Chinese).

I understand it can be quite a pain – this is not a requirement of this plugin in particular, though.

Hello!

This error occurs when either the request to your update server has timed out (20 seconds – empty response), or the server returned an error.
Please install Query Monitor plugin on both the client and the server to find more information and troubleshoot more efficiently.

Hi Vitali!

I see there is an error code when trying to authenticate – although I did not make the message explicit, this error actually corresponds to:

40164 如非白名单IP调用 This account is using an IP white list. Only IP addresses listed on the WeChat backend can get this account’s WeChat access token.

You can add your server’s IP to the white list in https://mp.weixin.qq.com, at the same place where you’ve setup the token and found your App ID etc.

Hello @thevisas / Vitali!

Thank you for your question, and the details.
Could you please try the following, in order:
– clear the permalinks by visiting /wp-admin/options-permalink.php and try again
– deactivate the W3TC caching plugin, clear the permalinks, and try again
– reactivate W3TC caching plugin and try again

… to try and pinpoint the issue? After that, if there are issues still occurring, I will follow up with you.

Best regards,
Alexandre Froger

• This reply was modified 6 years, 1 month ago by Alexandre Froger.

No update in 2 months – Mark as resolved

Hi @vladmo1 !
The plugin does not integrate this feature yet – for more details why, and the feasibility, you can see this support question.

I wonder if the statement “If the file (‘example.jpg’) exists then redirect to /pvtmed/example.jpg and return a 403” is accurate – it was my understanding it was more like “If the file (‘example.jpg’) exists then redirect to /pvtmed/example.jpg or return a 403”.

From the doc:

But if these directives are put inside the “/download/” location, the last flag should be replaced by break, or otherwise nginx will make 10 cycles and return the 500 error:

location /download/ {
    rewrite ^(/download/.*)/media/(.*)\..*$ $1/mp3/$2.mp3 break;
    rewrite ^(/download/.*)/audio/(.*)\..*$ $1/mp3/$2.ra  break;
    return  403;
}

and:

break
stops processing the current set of ngx_http_rewrite_module directives

Again, I could very much be pulling that out of thin air given how unfamiliar I am with this server configuration’s syntax – on the other hand, the question is getting pretty much out of scope for me ??

• This reply was modified 6 years, 2 months ago by Alexandre Froger.

Hi @jhob !
Glad to know there is positive progress.

Regarding the NGINX issue, it seems it’s definitely the way to go: adding a folder specific rule with a location block in the configuration file.
Inspired from the official documentation, I think you can try the following:

location /wp-content/pvtmed-uploads/ {
    if (-f $request_filename){
        rewrite ^(.*)$ https://www.mysite.com/pvtmed/$1 break;
        return  403;
    }
}

I am way more familiar with Apache than NGINX, so I may be mistaken here.

• This reply was modified 6 years, 2 months ago by Alexandre Froger.
• This reply was modified 6 years, 2 months ago by Alexandre Froger.
• This reply was modified 6 years, 2 months ago by Alexandre Froger.
• This reply was modified 6 years, 2 months ago by Alexandre Froger.

Hi @jhob !
I think I have pinpointed why the URL is not generated properly.

Indeed, when building the private URL of an attachment, the code is stripping the value of the global ABSPATH – which in your case is not found in the original URL (/var/www/vhosts/mysite.com/httpdocs/wp does not exist in the string /var/www/vhosts/mysite.com/httpdocs/) and uses the site_url option (which in your case includes the /wp/ fragment).

For administrators like you (who are using a non-classic WordPress files tree) to fix that, I’ve added 2 filters in version 1.2 that should be useful:
– apply_filters( 'pvtmed_private_upload_url', $private_upload_url ): for you to fix the media’s URL
– apply_filters( 'pvtmed_htaccess_rules', $htaccess_rules ): for you to fix the rewrite rules

In your functions registered to these filters, you can tweak the returned values with str_replace and adapt them to your specific WordPress files tree. These filters are guaranteed to be called if they are registered in a plugins_loaded action with a priority of 9 or less (other actions such as init with high priority, in other words low value, may be used with caution, after studying the code base).
You will also have to remove the .htaccess file in the pvtmed-uploads directory after the functions are in place – it will be recreated automatically.

Hello Alex,

I’ll contact you on WeChat shortly – also, the most convenient if not WeChat is issues on GitHub ;).

Speak soon!