Support » Plugin: Slimstat Analytics » Clobbered my sites again…

  • Resolved crzyhrse

    (@crzyhrse)


    The latest update clobbered our sites again… Three times now this has happened with recent Slimstat updates… Possibly it is a conflict with WP 4.0.1, or it is again something directly in the last update, don’t know, both pretty close together…

    You don’t seem to be checking these things out very well before/when doing an update…

    Here is the error that shows on all pages when Slimstat is active… Only this on the pages, no content…

    Fatal error: Unsupported operand types in /home/purelig2/public_html/purelightalchemy/wp-content/plugins/wp-slimstat/wp-slimstat.php on line 725

    The thing is, every time this happens all caches on all sites, both on the server and at Cloudflare have to be purged, and then reloaded, site by site, page by page…

    If this continues we will have to let Slimstat go…

    Regards…

    https://wordpress.org/plugins/wp-slimstat/

Viewing 15 replies - 1 through 15 (of 41 total)
  • Additional info…

    Just one site seems affected, another site so far seems unaffected with the latest slimstat… Fortunately three other sites haven’t had slimstat reactivated since the last update issue, and no inclination to update/reactivate until this is resolved…

    So maybe who knows… Both the affected and unaffected ( so far) sites are running WP 4.0.1… Mostly same plugins, a few different ones…

    The error is calling it slimstat though, and no other plugin or other issues are showing up, so don’t feel any inclination to look for a plugin conflict either, considering past slimstat update issues and the specifics of the error…

    Plugin Author Jason Crouse

    (@coolmann)

    What version of PHP are you using?

    5.4.35

    My server also uses Litespeed rather than Apache…

    Plugin Author Jason Crouse

    (@coolmann)

    Can you make sure you’ve all the plugin’s files? Especially the ones in the “databases” folder:

    https://plugins.trac.wordpress.org/browser/wp-slimstat/trunk

    It looks like one of the files is corrupted. Not sure why that happened, though. Maybe security restrictions on your server?

    Thanks,
    Camu

    All the files are there in Slimstat’s database folder on the server… Server security is unlikely changed in recent days… ? What would be different in the database files from this version to the last that could cause this…?

    I could upload a new database folder with the files, replace what is there, but how would that affect my slimstat settings and existing stats, etc…? And would doing that create other issues that you know about…?

    I could also just revert the slimstat version number back, and update again…?

    What would you advise, if I want to try activating slimstat again, and see what happens…?

    Regards…

    Plugin Author Jason Crouse

    (@coolmann)

    Those files DO NOT store your pageviews, they are used to translate the USER AGENT string sent by your visitors’ browsers into something more user friendly. The line of code mentioned in the error here above is related to the function that scans those files to find a match, that’s why I’m assuming there must be an issue with one of the files.

    What I can do is to add some redundant checks to our code to make sure all the files have the expected format, in case they get corrupted during the installation process. These files were updated in version 3.8.3 (see changelog). Downloading them again might solve the issue.

    Thank you.

    When will you add the redundant checks to the code…? I may want to just wait until that happens… ?

    Plugin Author Jason Crouse

    (@coolmann)

    3.8.4, which we plan to release in about 10 days. However please note that if your file is corrupted, pageviews might not be properly registered.

    Not sure what you are saying… Slimstat is not presently activated… If I wait until 3.8.4, and update without slimstat activated, then activate it, are you saying there could still be issues…?

    Plugin Author Jason Crouse

    (@coolmann)

    If your server is preventing WP from saving those files correctly, your users’ visits may be skewed even with the fix in place.

    I looked at the data files, and see that they are huge and complex, way beyond me even imagining what is going on there… I don’t do code except at some very very very (emphasize very) elementary levels, css and html a bit, and php snippets from others when it is clear where they go and what they are for…

    I appreciate what slimstat does, which is a lot, and all the ways it is very helpful and pretty cool actually, and really appreciate you (and perhaps there are others) for making it available for free…

    I can also understand your seeing it as a possible server issue… I am though a little cautious about that, because of two recent previous issues where slimstat clobbered our sites, all of them not just one, in a similar way, and it was clearly in your own words even slimstat with incomplete files that did it… And how the error this once time again is clearly identifying slimstat…

    You seem to be suggesting that the server because of security reasons could be rewriting code in a file, changing it, or something similar…

    Some considerations…

    I don’t know enough to know if a server could or would rewrite or alter code in a file that is uploaded… All the data files are there… They are filled to the brim with code, I don’t know if I have ever seen such huge, long .php files…

    I would think though that a server for security reasons might block a file with a suspicious string of code in it, but not actually change it… And, I don’t know…

    If it were a server security issue I would think that it would also be happening on our other site that has slimstat currently active and updated… So far it isn’t…

    We use a whole lot of plugins, being very, very careful about which, and have never had an issue similar to this with any of them… I’ve never had one not update/install in an incomplete or corrupted way like you are suggesting, at least that I know of, I.E., no issues that bring up errors like slimstat has on three update occasions now…

    So as said, hard for me at this point to believe it is merely a server issue…

    You also say that slimstat won’t be giving accurate results if the files are being changed… If that were the case there would be no point in using it…

    All this leaves mostly unknowns… You are the expert here, I am not even at a novice level with any of this… I am also imagining, because of what slimstat does, that you know servers…

    No conclusions, just kind of the terrain as I seem to see it at the moment… The thing is, the issue occurred, and I’m still here… But it needs to be your knowledge and experience that resolves things… If you don’t have the motivation, maybe because it is not widespread or whatever, then this goes nowhere… In which case I’ll let it go, and move on…

    Kind regards…

    Plugin Author Jason Crouse

    (@coolmann)

    Crazyhorse, as you have seen already, motivation is not the issue. My team and I are genuinely motivated to improve Slimstat as much as we can, and we really welcome feedback from users like you.

    I was not trying to find an excuse to not address the issue, believe me. But since no one else has complained about this issue (and we’ve had already about 10,000 download of 3.8.3), I was thinking that it could be something on your end and not on our end.

    The last time this happened, in was an issue with the SVN server on WordPress.org, which we promptly addressed, if I remember correctly.

    Anyway, we’re trying to reproduce the issue and please rest assured that it will be solved in 3.8.4.

    Best regards,
    Camu

    Hi Camu,

    Thanks for this… I was wondering if you all might like it best if I just moved on…

    The people at my hosting service are totally amazingly great, and I am going to ask them if they might look in on this…

    Maybe something helpful will come of that… We’ll see…

    Kind regards…

    Plugin Author Jason Crouse

    (@coolmann)

    Added the extra check in 3.8.4.

    Hi Camu,

    You changed this thread to resolved when it doesn’t seem to be… You have said the issue could still be there even with the extra check, and that the stats could be thrown off, therefore not useful… And you haven’t said what the checks do… Might there still be issues in an update that could clobber a site even with the checks…?

    And I’d like to see if my hosting folks have anything to offer on this subject before it is “resolved,” since you have so strongly suggested that the issue was/is caused by the server and possible security issues changing code in files…

    Isn’t this reasonable…? Unless you just want the problem to disappear rather than truly get resolved…

    Kind regards…

Viewing 15 replies - 1 through 15 (of 41 total)
  • The topic ‘Clobbered my sites again…’ is closed to new replies.