thevisas

Thank you for your response.
The plugin is active and operational. The GDRP code in functions.php also appear to be operational:
//Registration Form GDRP
function add_gdpr_checkbox_to_tml_register_form() {
tml_add_form_field( ‘register’, ‘accept_terms’, array(
‘type’ => ‘checkbox’,
‘label’ => ‘By registering I agree with the storage and handling of my data by The Visas of OZ. Privacy policy‘,
‘value’ => ‘1’,
‘checked’ => tml_get_request_value( ‘accept_terms’, ‘post’ ),
‘priority’ => 30,
) );
}
add_action( ‘init’, ‘add_gdpr_checkbox_to_tml_register_form’ );
function validate_gdpr_checkbox_on_registration( $errors ) {
if ( ! tml_get_request_value( ‘accept_terms’, ‘post’ ) ) {
$errors->add( ‘accept_terms’, ‘ERROR: Please, tick the checkbox.’ );
}
return $errors;
}
add_filter( ‘registration_errors’, ‘validate_gdpr_checkbox_on_registration’ );
function save_gdpr_checkbox_on_registration( $user_id ) {
if ( tml_get_request_value( ‘accept_terms’, ‘post’ ) ) {
update_user_meta( $user_id, ‘accepted_terms’, 1 );
}
}
add_action( ‘user_register’, ‘save_gdpr_checkbox_on_registration’ );

Despite TML working, we were randomly receiving wordpress emails re technical issues as per previous message.

Have reinstalled TML plugin and we’ll let you know if wordpress continues to experience technical errors.

As for issues related to access to ../wp-admin/index.php, it does not seem to be TML related as when TML was disabled prior to reinstall the issues were still present.

Regards, Vitali.

Hi Alexandre,

I have tried authentication with and without populating IP whitelist on https://mp.weixin.qq.com.
But the error message remains the same.
At the moment IP whitelist has 4 addresses.
First IP is a shared server address on Site Ground as shown in cPanel. The last 2 addresses are Cloudflare IPs. The second is added just in case as it can be seen as a first IP in email headers.
Previously, I had only the first IP configured, but addition of others did not make any difference.
Cloudflare should not at fault here as an API call comes from the actual server rather than Cloudflare.
Not sure if there is any debug in plugin. I have tried online API debugging tool in WeChat. If my own IP is not in whitelist I get the same error, but after adding my external IP to the whitelist I was able to get a token using this tool. But I am not sure if WeChat keeps any logs of IPs that are trying to access its API, so I can check which IP maybe failing.

Finally, using trial and error method and a bit of luck I have managed to get it working by adding account name servers(as shown in cPanel) IP addresses to the list. Not sure why it makes a difference except maybe that SiteGround is using these servers as outgoing proxies.

Thank you again for your help.

Kind regards, Vitali.

Hi Alexandre,

Thank you for your prompt response. After clearing permalink and clearing caches in SG Optimizer and W3TC, weixin responder is working and it is now registered in https://mp.weixin.qq.com.

However, authentication is still failing both when using WeChat or standard browser.

So far, I have tried to disabled both caching plugins and clearing permalink. But the error message remains the same as before.

Standard browser authentication can be tested at the following address https://www.thevisasofoz.com/wp-login.php.

Thank you again for looking into the issue.

Regard,
Vitali.

Hi,

Thank you for your reply.

I was in fact just testing this. It seems that FA4.3 is still required in admin part, so I left it as is in admin.php.

But it can be safely commented out in button.php for the front-end, provided that FA4.7 is already installed.

I understand that plugin update will overwrite any modifications.

Thanks again for your support.

Regards, Vitali.

Hi,

Thank you for your reply.
The plugin has been working and the current call can be closed.

However, regarding FA4.3 could you please clarify the following.
In the FAQ section of your website https://buttonizer.pro/faq/ one of the questions (My icons are not showing in my floating buttons?) refers to FA4.7.

As I mentioned before FA4.7 is already part of the theme used on the website.

So the question is whether Buttonizer can use FA4.7 that is already part of the theme and not download FA4.3 from maxcdn.bootstrapcdn.com .

Regards, Vitali.

Hi,

Thank you again for looking into the issue.

The script is added by the theme. In theme admin there is an option to add tracking codes and that is where it was added before.

After the script was removed and caches cleared, the buttonizer started working straight away. However, after adding the script back this morning, the problem can no longer be reproduced and buttonizer continues to work.

I am not sure whether the sequence of events has anything to do with it, but for now everything is working. If possible, I’d like to keep this request open for 1-2 days and do further testing. If it continues to work, I will close this request.

On another note, could you please advise if the plugin can work with Font Awesome v4.7 that is already part of the theme. If it does work with 4.7, is it possible to disable downloading of 4.3 files by the plugin.

Thank you again for your help.

Regards, Vitali.

Hi,

Thank you for your reply.

The script is a kind of tracking script and is placed in the footer template of the theme.

It is used to submit pages (when they are accessed) to the Baidu search engine. The reason for using this script is because Baidu does not work well with sitemaps over HTTPS.

Regards, Vitali.

Hi,

The workaround has ben found. It appears that the Buttonizer plugin has a conflict with Baidu script. After removing this script all buttons are working.

It would be appreciated if you can advise what, if anything, can to be done in order to have the plugin working with the Baidu script. Script code is below.
<script>
(function(){
var bp = document.createElement(‘script’);
var curProtocol = window.location.protocol.split(‘:’)[0];
if (curProtocol === ‘https’) {
bp.src = ‘https://zz.bdstatic.com/linksubmit/push.js&#8217;;
}
else {
bp.src = ‘https://push.zhanzhang.baidu.com/push.js&#8217;;
}
var s = document.getElementsByTagName(“script”)[0];
s.parentNode.insertBefore(bp, s);
})();

Regards, Vitali.

Hi Nicola,
Tested update from version 2.3.9 to 2.3.11 and the issue is no longer present.
Thank you.

Hi Nicola,
The previous version of the plugin was 2.3.9 and WordPress 5.0.3.
The update was done on local replica of the production site.
Thank you.
Regards, Vitali.

Certainly, I’d be happy to test.
Thank you.

Thanks Ravan,

When logging this case, I was sure that multi-page PDFs were working on IOS prior to plugin/Wordpress updates.

But after the last round of tests I am not so sure any more.
Sorry to have bothered you with this.

Hopefully, one day Apple will fix the issue.

Regards, Vitali.

Hi Ravan,

PDF can be opened in an iFrame without lightbox, but on IOS it displays 1 page only.

Now I am no at all sure what is the cause of the issue.

I have copied site to a local dev with wordpress v 4.7.4 and the issue is still present.
Have tried plugin v 1.8 and 1.8.5 on IOS 11.4.1 and 11.2.5, but the results are the same – pdf is only displaying the first page both in lightbox or iframe.

Regards,
Vitali.

Hi Ravan,

I have not changed devices recently and iPhone/iPad are on IOS 11.4.1.
I have tested on older iPhone with IOS 11.2.5 and the issue is still present.
In my view, if it is not related to plugin update, it is more likely to be related to WordPress 4.9.8 update rather than IOS update.
IOS 11.2.5 was certainly working before.
Regards, Vitali.

Hi Ravan,

I have tried versions 1.8.5 and 1.8 and unfortunately the issue is still present.
Perhaps, there were some changes in WordPress 4.9.8 that have contributed to this.

Regards,
Vitali