nicecms

Update seems to be working so far.

Will it be okay to use the Disable XML-RPC plugin with the updated version of Heartbeat?

I edited my reply above just after you replied to it. Thanks for your help. I’ll be sure to submit a review.

It’s working at least in part. I see your visit in the log and others but the log is missing visits from other ip’s that are unlikely to be bots and that visited “/wp-json/…”, which I assume means they were on the page for 45 secs and triggered the popup. If they triggered the popup then I’d think they’d be tracked in Client Mode however they’ve set their script blocking browser extension options.

Googlebot started appearing in logs so I added a list of googlebot ip ranges to the Exclusions list (https://evert.meulie.net/faqwd/googlebot-ip-ranges/).

• This reply was modified 5 years, 7 months ago by nicecms.
• This reply was modified 5 years, 7 months ago by nicecms.
• This reply was modified 5 years, 7 months ago by nicecms.

Just to clarify, did you make sure the cache was cleared after you disabled the Preload option?

Yes, I think so, and the timestamp you saw would make sense since I disabled the preload option earlier today.

I just used the WPFC button to clear the cache and I see that the timestamp of the home page now reflects that.

The fact that only my own visits appear in the log doesn’t make sense to me:

My own visits appear in log with WP Fastest Cache both enabled and disabled.

• This reply was modified 5 years, 7 months ago by nicecms.

Ok, the option to not track bots is off, and Preload is disabled in WP FC, but still visitors aren’t showing up in the Slimstat access log, though they’re in the Wordfence log. Many of the Wordfence log entries appear don’t have a “/” Page Visited entry, but only a “/wp-json/…” Page Visited. That’s from Popup Maker’s popup window that appears after 45 secs. Could there be a conflict between Popup Maker and Slimstat?

I’ll try disabling Preload Cache, which is enabled by default in WP FC. Should that fix the issue?

The thread you refer to says, “Yes, the most recent version of Slimstat has the issue fixed, because WPFC would appear as a “bot” so there were some hangsup. All sorted now.”

Thanks

• This reply was modified 5 years, 7 months ago by nicecms.

Thanks Jason. It’s EARN.

• This reply was modified 5 years, 7 months ago by nicecms.

Any update? Pro user of WP Fastest Cache, seeing no data in Slimstat with WP FC caching enabled.

Yes, they have different IP’s.

Apparently at least the Live Traffic entries with “Browser: Mobile Safari UIWebView” don’t include any “arrived from” info, whereas the website log entries include: “https://m.facebook.com” “Mozilla/5.0. (iPhone;

> P.S. The misspelling of the word “referrer” as “referer” has a nice story that can be found here.

:)) I never heard of that before.

Our inability to view more than 50 entries is apparently caused by a conflict with the plugin IP Geo Block.

Disabling IP Geo Block using the Health Check plugin allows more than 50 entries to be seen. However, inserting “define(‘CONCATENATE_SCRIPTS’, false);” into wp-config.php didn’t help.

The console error with IP Geo Block enabled includes:
Uncaught TypeError: Cannot read property ‘toLowerCase’ of undefined
at HTMLFormElement.<anonymous> (authenticate.min.js?ver=3.0.10.3:6)
at HTMLDocument.dispatch (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-menu&ver=36aefcf1612711477f21055260eeabd2:3)

Thanks for the info that allowed me to resolve this issue.

Same problem here after I (needlessly) increased “Amount of Live Traffic data to store (number of rows)” from 2M. I set it back to 2M, but still can only see 50 rows. Before increasing the number of rows, I could scroll down continuously.

Most visits are from facebook’s ios app, like the first two shown here: https://drive.google.com/open?id=1DFOX8KMA9C2G2yGd0rR8Jf1AoKFVc2iF

Perhaps wordfence uses a “FB” parameter in the “Browser” string to correctly identify these as from facebook. If so, that’s very helpful, but it’d helpful to know how the referrer search works.

BTW, referrer should have 3 r’s in the dropdown menu. ?? Thanks for wordfence!

It turns out that we’d modified the php when we first implemented customizr, and forgot to port the modified php when we updated customizr to fix the missing menu items. Sorry for the confusion. Thanks for fixing the missing menu items issue.

While updating to either 3.5.2 or 3.5.4 restores all the menu items, our further problem is:
> Updating to Customizr 3.5.2 restores the menu items, but all our customizr settings and images are lost.

This still happens when updating from 3.4.21 directly to 3.5.4:
> (images at https://goo.gl/Dywe40)

Thank you for your reply.