holmpage

Further to the error reported by @mtwoffice, here’s the report I got by email, replacing my path and domain with “###”:

`Error Details
=============
An error of type E_ERROR was caused in line 21 of the file /var/www/vhosts/###/wp-content/plugins/ht-easy-google-analytics/ht-easy-google-analytics.php. Error message: Uncaught Error: Call to undefined function bget_option() in /var/www/vhosts/###/wp-content/plugins/ht-easy-google-analytics/ht-easy-google-analytics.php:21
Stack trace:
#0 /var/www/vhosts/###/wp-content/plugins/ht-easy-google-analytics/includes/class.ht-easy-ga4.php(50): ht_easy_ga4_get_id()
#1 /var/www/vhosts/###/wp-includes/class-wp-hook.php(307): Ht_Easy_Ga4->init()
#2 /var/www/vhosts/###/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#3 /var/www/vhosts/###/wp-includes/plugin.php(476): WP_Hook->do_action()
#4 /var/www/vhosts/###/wp-settings.php(461): do_action()
#5 /var/www/vhosts/###/wp-config.php(90): require_once(‘/var/www/vhosts…’)
#6 /var/www/vhosts/###/wp-load.php(50): require_once(‘/var/www/vhosts…’)
#7 /var/www/vhosts/###/wp-login.php(12): require(‘/var/www/vhosts…’)

I just had the same problem and did a bit of research, following which I found a .user.ini file in the ROOT of the site, and renamed it to something not useful. The site works again.

Many sites I build do not get changed very often. They’re built on WordPress for its functionality, but don’t have active blogs or members logging in. A weeklong learning period for the WordFence Firewall is not likely to yield any useful information. Also, my own IP address changes, thanks to my ISP, if that is one of the things it “learns”. I think I shall not set up the firewall again if this is to be the result.

There could me many causes to the problem. If you are not intentionally redirecting query strings from the WordPress route using .htaccess (and if you don’t know what this means, then you definitely aren’t doing it), the cause of your problem is different than mine was. My client’s site had been hacked, which added thousands of URIs linking to other hacked sites selling brand name designer goods. I rebuilt the site in WP and used Webmaster Tools and .htaccess to get rid of the unwanted addresses so that the site could get properly indexed again. A sad tale of woe.

If you can’t see your .htaccess file using an FTP client (e.g. Filezilla), you’ll have to find the setting that allows you to show hidden files, which depends on the server. (In Filezilla you can try Server > Force showing hidden files.)

For those who do need to do this, to redirect query strings using .htaccess, you could use the following code. The ‘!’ means to add an exception for a directory, which has to be done for wp-admin in order for the WP backend to work. To solve this problem for WooCommerce I simply added the same exception to checkout and cart. Other plugins may have similar requirements. You should do more reading on .htaccess before you start playing with it. (There are good reasons for servers to hide it – one wrong move can break your site.)

# RewriteEngine On
# Options +FollowSymlinks
# RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /([^?]*)\?
# RewriteCond %{THE_REQUEST} !wp-admin
# RewriteCond %{THE_REQUEST} !checkout
# RewriteCond %{THE_REQUEST} !cart
# RewriteRule (.*) /$1? [R=301,L]

Ah-hah! That explains all. A previous version of the site was pharmahacked and I’ve been stripping query strings via .htaccess with an exception for wp-admin.

With the new ajax features in woocommerce, it finally caught up with me.

I’ve added exceptions for checkout and cart, and now the checkout works, and I can also use the ‘x’ to delete items in the cart, which had stumped me before.

Thank you!

Resolved with 2.4.6

Marking as resolved.

Thank you, this issue was corrected in 2.4.6.

Thank you. ??

Thank you so much for taking this on!

No Rob, I haven’t heard anything. I’m still doing manual updates for the site and replacing inc/geography.php (which came from PayPal’s developer resources) with my altered version immediately after updating the plugin.

Will do. Thanks for looking into it and I will let you know if it happens again.

MU Domain Mapping has been working since December last year. Wordfence is more recent. Last site I added was on Sept. 7 but it isn’t domain mapped. Previous one was June 10 and is domain mapped. Comparing previous versions of htaccess, there doesn’t seem to be anything pertaining to domain mapping there that changes when sites are added. That seems to happen in wp-admin/includes/, which is referenced in htaccess near the end.

What is in the .htaccess file of the multisite:
1. #WFIPBLOCKS
2. an xmlrpc block (since about Aug 31)
<files xmlrpc.php>
Order Deny,Allow
Deny from all
</files>
3. #WFCACHECODE
4. a few manual 301 redirects for a site I moved to this network
5. WP’s Rewrite Rules that are the same as when I set up the site, before Wordfence.

There was also the Aug. 22 case on a single site. Could there have been a cached version somewhere of an old Wordfence file from before the correction was made 4 months ago? CloudFlare, some archive or mirror site… does that ever happen?

Thanks so much for your help. I’ve posted a screenshot of the network plugins at https://holmpage.ca/images/Plugins-2014-09-12.png

Note that some are not activated at all.

Not specifically. Jetpack is network-enabled but none of the components seem to be for caching or security. I don’t have W3 Total Cache or WP Super Cache or anything like that. IWP as I mentioned, backup plugins, Akismet, but nothing else strictly for security or caching.

It’s 5.2.3 now, but just got updated today (Sept. 12) via InfiniteWP. It’s on automatic updates, however. My IWP activity log goes back to Sept. 2 and doesn’t show any updates to Wordfence in that time, but it was probably getting updated automatically. So I can’t say for sure what version was active yesterday, but I would guess 5.2.2. (Unless that info is in the database? I can look if I know where it would be.)