Hi,
it could be related to the new DB API bundled with 3.5.3. We are looking into this.
Camu
Indeed, it is related to the API. We’ll release an update asap.
Camu,
Thanks so much for the update! I look forward to the next release!
Thanks again for your time and help,
James.
Just posted version 2.3. Check it out!
Camu,
WOW, that was definitely quick!
Checking it out now! Once again, thanks very much!
James.
Camu,
I just updated to the version 2.3 and I am getting several errors like this, Warning: date() expects parameter 2 to be long, string given in /home/content/03/10004203/html/wp-includes/functions.php on line 105
The only difference in the errors is the line number at the very end. Any idea as to what this might mean?
Here’s the two shortcodes I just tried to use,
[slimstat f=’count’ w=’ip’ lf=’strtotime equals today’]
[slimstat f=’count’ w=’*’ lf=’strtotime equals today’]
I then removed the code where the w=’*’ and just left the other and the errors still remain. Also, both of the shortcodes comes back with 0 as the count too.
Any help to figure this out would be greatly appreciated.
James.
Sorry, I forgot to mention that we also updating WP SlimStat to address this problem. Contact us if you want to test it in advance:
http://support.getused.to.it/
Camu,
Thank you so much for your QUICK replies. I’ll contact support in just a few and I’ll bet back with ya as soon as I can to let you know what I find out.
Thanks very much for your help!
Have a good one,
James.
Camu,
Sorry for getting back with you so late. I’ve updated to the latest WP SlimStat 3.5.4 and both of the shortcodes mentioned above seem to work great now. Only issue I can see is that the two shortcodes make the page they are located on render much, much slower now. Other than that, everything seems to be working fine.
Thank you so much for your help on this!!
One more question if you don’t mind. In my case where I’ve updated to a beta release, would it be recommended to update again once the official release is ready? Or would I be okay to wait for the next release?
Thanks for your time and help,
James.
You may want to update to stable 3.5.4 anyway, as we also fixed other minor bugs after I sent you the beta.