WPIntell

Source evidence

Testing killed my site

EngageBay WooCommerce Addon · support · 2019-12-09T02:13:00+00:00

mixedsentiment
highseverity
0.95relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 25 rows with source links

24.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
steveni1963 resolved
Hi, This plugin kills my site and prevents access to wp-admin. I have tried it while deactivating other plugins and the same occurs whenever it is activated. Only way to restore site whe it is activated is to rename the folder. Server environment: WooCommerce version: 3.8.1 WordPress version: 5.3 WordPress multisite: – WordPress memory limit: 512 MB Server info: Apache PHP version: 7.3.12 PHP post max size: 64 MB PHP time limit: 300 PHP max input vars: 6000 cURL version: 7.67.0, OpenSSL/1.0.2t SUHOSIN installed: – MySQL version: 5.5.5-10.3.20-MariaDB Max upload size: 64 MB I found out that placing your tracking code on my site also killed it. Will keep looking…. I created a single page with your tracking code and noted 2 things: If not logged in to wp-admin there didn’t seem to be a problem When logged in to admin it failed and it then became impossible to access wp-admin from that browser. If I cleaned out the cache (browser) it logged out wp-admin and worked again. So issue on my site seems to be a clash when logged in as admin. I assume this would also affect users logging in so can’t risk the loss of business until I work this out. Seems to be theme related Found it was due to ModSecurity logging use as an attempted exploit. When this resolved other errors and issues discovered as per my other posts

Comments

4 shown
steveni1963 2019-12-09T03:20:00+00:00

I found out that placing your tracking code on my site also killed it. Will keep looking….

steveni1963 2019-12-09T06:01:00+00:00

I created a single page with your tracking code and noted 2 things: If not logged in to wp-admin there didn’t seem to be a problem When logged in to admin it failed and it then became impossible to access wp-admin from that browser. If I cleaned out the cache (browser) it logged out wp-admin and worked again. So issue on my site seems to be a clash when logged in as admin. I assume this would also affect users logging in so can’t risk the loss of business until I work this out.

steveni1963 2019-12-09T14:18:00+00:00

Seems to be theme related

steveni1963 2019-12-13T04:16:00+00:00

Found it was due to ModSecurity logging use as an attempted exploit. When this resolved other errors and issues discovered as per my other posts