Hi Steve,
I’m looking into it. Could you send me your website URL so that I can run some tests to see if the tracker is working as expected?
Thanks,
Jason
Hi again,
I’m going to release a quick bugfix for the shortcode issue in a few minutes. See if solves the other problem as well.
Thanks,
Jason
-
This reply was modified 6 years, 8 months ago by
Jason Crouse.
Hi Jason,
Requested url is:
https://www.midlandsmaidens.com/statistics/
…ignore all the test searches at the top, that’s just me testing a new search box.
Can you check your web server error log? It looks like there’s a 500 error message being caused by one of the plugins. Maybe a conflict?
Well I’ve been pulling plugins in and out for most of the morning, so that might be the reason – Ill get the error logs checked though.
Just been through the whole error log, and then got my host to have a look through it as well, and we could find no 500 errors.
I don’t see the tracking code anywhere on that page’s source code.
On the Statistics page you mean?
The Statistics page uses shortcodes rather than widgets.
All I see is an error message: “The site is experiencing technical difficulties.”
Yes, which it was doing earlier this morning as I was messing around in cpanel with some code.
It was all resolved at around 7am.
Right, just got back from my host, and also from WP Rocket.
I took my website back a couple of days from a snapshot, which meant that four plugins, including Slimstat, needed to be updated.
So I thought I’d do this the technical way, and see what happened as all four plugins were updated singly.
Blog2Social was fine, cleared caches, and loaded it up on Firefox – no problem.
As was Relevanssi, which I would have thought would have been where the problem laid due to me swapping code about, but again loaded perfectly on Chrome and Firefox.
Then it came to the new version of Slimstat, which uploaded nicely, but then crashed the website on Firefox – so THAT was where the 500 error was coming from!
Tried uploading WP Rocket, which I was having blazing rows with due to it not regenerating critical css, and it uploaded perfectly and is regenerating the critical css as I write this.
The problem therefore is with Slimstat.
Have deactivated and deleted Slimstat now at the suggestion of my host, as we’ve just wasted a full day of business due to the website having changed colour from black to white – as pointed out by my host – and the 500 server errors as pointed out by WP Rocket.
Thanks for the experience anyway!
In case you’re still interested, if you’re using any of our add-ons, please make sure you’re running the latest version, as we’ve updated some references in our code that might break older versions of the add-ons.
Best,
Jason
