JPecsenyicki

It’s my friend’s site, so it’s his decision whether to change hosts or not.

But clones of his site were working well on 2 other hosts. No problems with Wordfence pathways on either of them.

Hi @wfpeter,

Sorry for not replying sooner.

The firewall has been “Enabled and Protecting” for the past 5 days (Learning Mode ended on Dec 26th).

Just yesterday I noticed the homepage took over a minute to load, but it’s loading faster tonight.

(BTW, I’ve made clones of the site on 2 different web hosts with the Duplicator plugin, and am not seeing the very slow loading times that sometimes occur on this installation.)

Joseph

Hi Peter,

I’ve just sent the Diagnostic report.

Looking through it, it shows the correct path. Which is not what I saw when I tried to configure the firewall.

The firewall is currently in Learning Mode.

Thanks for your help.

Joseph

Oh, I don’t think I explained something clearly to you.

The three domains all have their own WordPress installations, and their own Wordfence firewalls. Their paths in their respective .USER.INI files are:

Primary Domain:
/PATHWAY/public_html/wordfence-waf.php

Add-On Domain #1:
/PATHWAY/public_html/ADD-ON-DOMAIN-1/wordfence-waf.php

Add-On Domain #2:
/PATHWAY/public_html/ADD-ON-DOMAIN-2/wordfence-waf.php

But for some reason, Add-On Domain #2’s Wordfence is trying to follow the Primary Domain’s pathway instead of its own.

• This reply was modified 3 years, 11 months ago by JPecsenyicki.

That’s a relief to hear.

Thank you, @wfadam!

Hi @corylamleorg,

The files in question were deleted from the server a couple days ago, though this isn’t a problem going forward because I download the backups whenever they’re made (so I still have the original, hopefully uninfected, backups).

If I understand the information at the link correctly, if this happens again, we can submit a ticket to compare the original file to the supposedly infected file.

(At this point, I tend to think it was case of false positives, given that the reports were on 3 different sites at the same time and were undetected by Wordfence on all 3 sites. Virustotal.com shows nothing wrong with any of the sites themselves.)

Thanks for your help!

Thanks, I’m glad to hear that.

Hi Marko,

You said that you were not seeing /?wc-ajax=get_refreshed_fragments on the page.

On further investigation, I found a setting on a different proprietary plugin installed on the site’s managed WordPress hosting account:

Dequeue WooCommerce Cart Fragments AJAX calls

Description: Disable WooCommerce Cart Fragments on your homepage. Also enables “redirect to cart page” option in WooCommerce

The mini-cart worked correctly after this option was disabled. Had nothing to do with “W3 Total Cache” at all.

Thanks again for pointing me in the right direction.

This problem was caused by a proprietary plugin automatically installed on the managed WordPress hosting account.

The following setting was enabled:

Dequeue WooCommerce Cart Fragments AJAX calls

(Disable WooCommerce Cart Fragments on your homepage. Also enables “redirect to cart page” option in WooCommerce)

When disabled, the cart on the Homepage worked correctly.

Thank you for looking into this!

In the meantime, the plugin on the site has been rolled-back back to version 2.64.

Looking forward to version 2.66.

Hi Marko,

I forgot to mention that the minicart on the homepage works fine when A2 Fixed W3 Total Cache is deactivated.

Anyways, thanks for looking into this for me. I’ll ask about this on the WooCommerce forum.

Hi Marko,

Yes, I find it very strange that the same minicart widget works on every page except for the homepage.

In Woocommerce > Settings > Products > General, the “Enable AJAX add to cart buttons on archives” option is checked.

In Performance > Page Cache, /cart/, cart, and cart/* have all been added to the “Never cache the following pages” option.

The site is using WooCommerce 3.9.1 and A2 Fixed W3 Total Cache 0.9.4.6.4.6. (Though I’ve deactivated this and activated the latest standard version of W3 Total Cache, and it does the same thing.)

I fixed this by:

1. Downloading the developer’s fonts for Simple Line Icons
2. Uploading these fonts into a new “fonts” folder in the root directory
3. Using @font-face in the stylesheet in the child theme to load the fonts. (With CSS adapted from the developer.)

I’ve also turned off OceanWP’s loading of Simple Line Icons so that my child theme rules take precedence (Theme Panel > Scripts & Styles > Simple Line Icons set to “Disable”. Then “Save Changes” at the bottom of the page).

Upon further investigation, it looks like the other fellow is trying to use Simple Line Icons. So that’s what’s not loading correctly.

(I’ve managed to display a magnifying glass on the homepage, using Font Awesome.)