• Promising plugin. But…
    I purchased the add-ons. But the Custom DB did not work, despite following the setup steps.
    Also, once users are blacklisted, then I could not remove them. Could change the settings, save, and was confirmed saved without the blacklisting. But then the usernames appeared again.
    Same problem for the link with the Custom DB.
    Was incompatible with Mashshare and with the LiveView of Wordfence.
    Ended-up crashing SQL Services on the VPS due to php overload, forcing a 20min downtime for reboot.
    Careful: their website mention that they do not refund any purchase (even if they could actually revoke the license keys).
    Pure loss of time and money…

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jason Crouse

    (@coolmann)

    Officially we don’t refund purchases because otherwise people could buy the plugin and then ask for a refund just for no reason. Revoking the license will not make the add-on unusable: licenses are used to get updates, not to make the plugin work. However, if there are clear reasons for requesting a refund (server incompatibility or demonstrated conflicts with other plugins), please contact our support team and we’ll be more than happy to work with you to find a solution (refund or fix).

    It would be interesting to understand what “did not work” means, when you say that about our Custom DB add-on. Could you be a little more specific? This add-on is already compatible with Slimstat 4, even if we are about to release an update that introduces some code optimizations, and points the update checker to the new repository on wp-slimstat.com. We would be happy to fix any issues you noticed.

    As for the settings not saving, I’ll talk to the developer. Are you using Firefox with AdBlock? We’re told that could be an issue indeed.

    As for LiveView, what was the problem exactly? Is there anything we can do to fix that? As you can understand, it’s impossible to test the compatibility of our plugin against the other 30 THOUSAND plugins available in the repository, so we rely on our users to help us troubleshoot these issues. And as you can see, we’re usually quite responsive in fixing issues that can be addressed on our end.

    Regarding the SQL service crashing, how many records are in your slimstat table? We use a cheap shared hosting provider as our test environment, and with 780 THOUSAND records we haven’t had any problems so far. Some of our users have 4 MILLION rows in their table, on a dedicated VPS environment, and reports are as fast and responsive as it gets. Maybe optimizing your MySQL server could help?

    Anyway, not sure if you are willing to help us or not, but thank you for your feedback.

    Plugin Author Jason Crouse

    (@coolmann)

    Anyone home?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Crashed SQL’ is closed to new replies.