mesw

Thanks! define(‘CMPLZ_DO_NOT_SCAN’, true); did the trick and made wp backend much faster.

I was long time logged in and browsed the wp admin but the cookie scan never stopped. The site has about 100 pages so if it scans 5 per page load it should have finished already. Any idea what causes this?

Now the site has been published in rilease.fi. Here is the full query monitor info:

GET

https://rilease.fi
?complianz_scan_token=1694093146
&complianz_id=home

200 OK-

• DNS Resolution Time: 0,0013
• Connection Time: 0,0014
• Transfer Start Time (TTFB): 1,9684
• Response Content Type: text/html; charset=UTF-8
• IP Address: 95.216.140.247

1. cmplz_cookie_admin->run_cookie_scan()
   wp-content/plugins/complianz-gdpr/cookie/class-cookie-admin.php:2280
2. do_action('admin_footer')
   wp-includes/plugin.php:517

Plugin: complianz-gdpr

Size: 24,0 kB

Timeout: 5

Time: 1,9736

I deactivated all the plugins except query monitor and switched to default theme. I also disable the automatic cookie scan.

I tried the scanning again and there is no an errors shown on the browser console when doing it.

The HTTP API call is still made on every wordpress backend page load. Now the exectution time is about 0.15 seconds which is considerably less than with the plugins on. But still its running on every page load. What should I do?

• This reply was modified 1 year, 5 months ago by mesw.

Hmm, ok. I tried switching post type with that plugin but it didn’t work for the translation either.

Hi,

I’m back to work from summer holiday. Still found anything what could cause this or is there something I could do to help with the issue?

The enhanced ecommerce has been now off for a while and the fatal errors are completely gone. So it is 100% sure that its some kind of plugin conflict. The payment gateway plugin support told that they have time to investigate this issue on the start of August.

What is weird I still haven’t managed to reproduce the issue on staging site. Well I haven’t tried it that many times but from my experience it should have already occured.

Hi,

I’m still beginner in debugging WordPress so I’m not sure if these images help at all. I configured remote xDebugging for the staging site because I couldn’t manage to debug the payment gateway redirection on localhost.

For some reason I haven’t managed to reproduce this issue on this staging site (at least for now) which is odd. I have tried it bit over 10 times. On production site about 1 out of 5 orders were failed because of this error even though I couldn’t reproduce it myself that often when testing.

• This reply was modified 3 years, 7 months ago by mesw.
• This reply was modified 3 years, 7 months ago by mesw.

Okey, I’ll try to dig in deeper.

PS. I’ve disabled enhanced ecommerce on production site to avoid failing orders. Now the testing should be done on this staging site where enhanced ecommerce is still activated.

• This reply was modified 3 years, 7 months ago by mesw.

Hmm, now it worked both on live and development environment without doing anything. Any idea what it could have been?