STONE5572

Camu,

Thanks for getting back with me so quickly. It’s really strange. The plugin hasn’t worked in several days now but late last night it started working again and today it’s working just as it should. If it happens again I’ll be sure to look at the apache errors and get back with you on it.

Once again, thanks so much for the plugin!!
James.

Jacob,

Thank you so much for your help and for taking the time to explain different things along the way. I really appreciate that!

Yea, I noticed the lock had changed back to green last night. I guess my server needed a bit more time to reflect the update than what I was giving it.

Once again, thank you for your time and help,

Have a great day,
James.

Jacob,

I’m sorry to have to bother you again, but I wanted to ask a question. I’m noticing that the wppa.min.js file has returned with the v5.3.1 update. Would it be recommended to delete this file again or just leave it as it is.

The reason I am asking is because now I don’t have the green lock beside my https url. Not it’s the yellow warning lock instead.

https://www.grocerycomping.com

Please let me know what you think.

Have a good one,
James.

Jacob,

Hi there. I just updated to v5.3.1 and the error remains. Actually it’s not even coming up as an error but just a warning. Everything seems to be working just fine too, so I’m really not going to worry to much about it right now unless it moves over to becoming an error instead of just a warning.

Thanks so much for your help on this.

Have a great day,
James.

Jacob,

I apologize for not getting back with you sooner. So far I’ve updated to v5.3.0. I am still using WP v3.8.3 as I haven’t updated to v3.9 yet. I fixed the /* mistake I had in the wppa.js file and I’ve re-added the code from above. I also deleted the wppa.min.js file too. I am still seeing the error in the Console section of the Inspect Element tool. It’s really not hurting anything on my site at the moment, so I’m going to leave it this way in case you want to have another look.

Once again, thank you so very much for your time and help,
James.

Jacob,

Hi there. I just tried the above code and after clearing my cache and looking at Google’s Inspect Element these are the errors I’m seeing now:

Uncaught SyntaxError: Unexpected token function wppa.js:3115
Uncaught ReferenceError: wppaTickImg is not defined wppa-init.en.js:65
Uncaught ReferenceError: wppaAutoColumnWidth is not defined (index):170
Uncaught ReferenceError: wppaAutoColumnWidth is not defined (index):216
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.

Please do let me know what you think about this as I have no clue what these errors means.

Also, the autocolumnwidth errors were not there before. They just started with the above code that I added.

I’ll leave it like this, and I do believe that the plugin should be in debug mode if you want to take a look. Here’s the page of the site with the errors, https://www.grocerycomping.com/photos

If you have any more I ideas, please do let me know.
Have a great day,
James.

Jacob,

Sorry it took so long to get back with you. I would be happy to test it out. My only question would be do I replace the whole code or just the part of it? Please remember that I’m that tech savvy yet, plus I don’t want to make a mistake I can’t fix either..

Just let me know if I need to replace the whole function in my file with the one above or just part of it.

Once again, I appreciate the help on this too!
Have a great day,
James.

Jacob,

Thank you so much for your quick reply. I’ve changed the code in wppa.js as you mentioned and I deleted the wppa.min.js file too. The error is still popping up when I use Google’s Inspect Element and click on the Console tab. But, what I was essentially trying to do has been accomplished somehow. I am now getting the green lock beside my url address which is what I was going for. I’m still unsure about the error, but at least I’m not getting the yellow lock or red slash through my https which was looking horrible to my visitors/customers.

I’m not sure how to test the lightbox function, but all photos and widgets seem to be working just fine still.

Thank you so very much for your time and help!!

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.

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,

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.

Camu,

WOW, that was definitely quick!

Checking it out now! Once again, thanks very much!

James.

Camu,

Thanks so much for the update! I look forward to the next release!

Thanks again for your time and help,
James.

gsownsby,

I’m happy I could be of some assistance. I used Google’s inspect element feature to find the code. It’s a pretty neat tool; I just have a lot more to learn about using it.

Thanks for letting me know I was able to actually help!
Have a good one,
James.

Camu,

Hi there!!
I just set the number of days to 20 for right now. As soon as the daily purge kicks in, I’ll reset it to a more appropriate number.

On the other hand, I would be happy to test out new beta version, as long you could walk me through the install, if it’s a manual one. I haven’t actually performed a manual install of anything yet and it would be a fine time to learn right quick!!

Just let me know what I need to do to get started.
Thanks,
James.