Hi djmceltic,
sorry for the inconvenience. Version 1.3.6 of the Custom DB add-on requires Slimstat 4.3.6 or greater, and it breaks compatibility with previous versions. As soon as you update the main plugin, everything will start working as expected.
Thank you for your business!
Jason
OK so best practices are to update main version first? All good after updating the main plugin.
Just some feedback for your plugin too:
First it is awesome that it tracks so many things and has tons of flexibility. We have a large corporate internal site and we track a ton of things. It was fairly easy for us to track and to set up things without causing latency.
The actual only issues we had were when we tried to do some of the more advanced things like displaying things on the admin dashboard and stuff like that – just trying it out for fun. For some of the stuff – even without us messing with default settings – it caused admin to crawl to 20 second page loads. Some things turned on caused memory leaks and crashes. This is us trying this stuff out about 6 months ago. We never needed this stuff so we simply turned it off.
I rate pretty hard and I give your plugin a solid 9 out of 10 (10 out of 10 for just performance). I have to take a point off because some of the advanced features like slim_events stuff I have a hard time finding good doc/tutorials to send to my staff. One of my experienced devs or me can figure things out but its not “easy”. A suggestion would be allow your users to add things to your knowledge base -like examples once someone on your team OKs it.
Hi djmceltic,
you make a very good point about investing in simplifying the plugin’s accessibility level (in terms of how easy it is to extend it). Thank you for your rating (you may want to also make it official on this page – https://wordpress.org/support/view/plugin-reviews/wp-slimstat ). Your feedback means a lot to us.
Performance measurements vary based on many factors: server configuration (including optimizations for MySQL), number of plugins running in your enviroment, size of your dataset and of course Slimstat settings. According to our internal tests, it’s quite rare to have such a big difference though. Some settings, like converting IP addresses into domain names, will rely on server features, so again it depends on how quickly your DNS can resolve those entries.
Also, being a self-contained product, Slimstat uses more memory than the average plugin or SAAS analytics tool, since it has to load the browser UA database, the MaxMind geolocation database and other data structures into memory. Our production environment (our main website) is configured to use a PHP memory limit of 96 MB and it uses optimized MySQL config files. For being hosted on a shared host, it’s performance is more than reasonable.
Last but not least, we are a small team working on an open source product that, like every other WP plugin out there, is quite hard to monetize to a point where we can spend enough time to take it to the next level. We’ve started a knowledge base and tried to add more information as questions from users prompt us to clarify certain things. However if you have any specific ideas in mind, please feel free to point them out, and we’ll see to add them to the knowledge base.
Best,
Jason.
