Conversation
…ment, which unfortunately is not compatible with version 3.x and needs to be completely reimplemented
…core functionality is now working as expected
…er, which was causing Slimstat from incorrectly identifying visits as coming from mobile devices, instead of bots
…ance tab, to better troubleshoot issues related to these files
…s behind a Cloudflare load balancer. Please update the IP Address Fix add-on as well.
…d the associated description to better reflect the underlying calculations.
…is older than 7.1
7f85bce to
91e360d
Compare
|
Hi there! Thank you for submitting this pull request. I like this idea, and the reason behind it is more than valid. Since this mod would increase the database size, I am thinking that it should be implemented as a switch in the settings, so that admins can enable/disable it as needed. I'm quite sure most of our users would not really need it on their blogs with just a few users. Would you be interested in submitting a modified pull request that implements this as a setting? |
|
Hey, thanks for the reply, yes I would gladly work on this PR. |
|
Terrific, thank you so much! |
|
Hi there, not sure if you're still working on this pull request. We're moving forward and implementing your feature in the next release. Take care, |
|
@slimstat That's an awesome news. Unfortunatly I didn't have time to finish my PR :( |
|
No worries, I understand! |
- Fix DB connection leak: close local pool in afterAll (CodeRabbit #1) - Remove unused setSlimstatOptionDb function (CodeRabbit #2) - Add limitation comment to setOption helper (CodeRabbit #3) - Add pr239-production-scenarios.spec.ts (8 tests) covering: B1: Cached page simulation (stale nonce → 403 proof) B2: sendBeacon payload nonce safety B3: Transport fallback chain (REST→AJAX) without nonce B4: GDPR consent + nonce interaction B5: Logged-in user nonce regression check
Hi,
CRM integration plugins in the wild rely mostly on the user Email. Since slimdata only stores username, It is difficult to reliably connect CRM data with slimstat data.
I've added Email filter and corresponding column in the database. I think this addition makes plugin more versatile and easy to use with CRM.
If site owner wishes to add email data retroactively (not fresh install), following query can populate new email column with data from wp_users table:
I didn't want to run this query during upgrade (with php), due to possibility of massive databases out there.