Yeah – that’s just an oversight. 3.0.3 actually included compatibility for 4.4, which is currently in beta.
I’ll fix it in the next release.
Cool, thanks. Am testing it now, really nice work 🙂
I read about the plugin in a Slack Room, and someone mentioned it causes a drain on the server resources.
Is that a concern?
No.
There’s in no change to front-end page load at all. Back end page load is technically impacted, but only when there’s a database change happening and even then it’s only one database call, so imperceptible.
Perhaps they were referring to records stored in your database. You can change the purge frequency to suit your needs, but realistically, this isn’t a problem unless you have an extremely busy site. Edge case sort of thing.
Let me know if you have any other questions. 🙂
Great, that makes sense. I’ve been trying to stress test it a bit, and been monitoring the actions via Chrome Dev and Cacti.
Very little impact from what I can see, and our site is pretty niche so don’t expect any really heavy traffic.
I really like this tool so far. In our case we just want to be able to keep track of clients who have access to a library behind a login, and I’m thinking we might be able to integrate the Stream events into our Mixpanel tracking.
I’ll be sure to leave a proper review once I’ve had a chance to understand it fully.
Thanks again, this really is a very useful tool.
