Sha'ves

The update to Woocommerce database did not solve the issue. Appeared as though fixed, because test was loaded from cache.

After clearing cache, same problem :

WordPress version: 		5.8
WooCommerce version: 		5.6.0
WooCommerce database version: 	5.6.0     <<<<<<<<<<
PHP version: 		        7.4.23

WP Activity Log 	  	by WP White Security – 4.3.2 
WP Activity Log for WooCommerce by WP White Security – 1.2.3

Temporarily reverting back to v1.2.2 until a solution can be found.

@danielspain, I faced something similar you might want to see if this helps: https://www.ads-software.com/support/topic/fatal-error-v1-2-3-wc_order_item_tax-wc_order_item_shipping/

Additional Info

WordPress version: 		5.8
WooCommerce version: 		5.6.0
WooCommerce database version: 	5.5.2     <<<<<<<<<<
PHP version: 		        7.4.23

WP Activity Log 	  	by WP White Security – 4.3.2 
WP Activity Log for WooCommerce by WP White Security – 1.2.3

Temporary Fix

Revert back to v1.2.2 : WP Activity Log for WooCommerce

Permanent Fix

Update WooCommerce Database : https://prnt.sc/1r3g0yu

• This reply was modified 3 years, 6 months ago by Sha'ves.
• This reply was modified 3 years, 6 months ago by Sha'ves.

That’s the fix. Thank you for the assistance, Alex.

https://pastebin.com/p1A8wAL3

Hi Alex,

I cant get pass the recaptcha in your helpdesk. Tried creating new ticket and signing up new account. Some issue with Freshdesk’s recaptcha. Browser console (Chrome, Firefox, Edge) yields the following error:

Uncaught (in promise) SyntaxError: Unexpected token in JSON at position 0
at JSON.parse (<anonymous>)
at recaptcha__en.js:24
at recaptcha__en.js:45
at Array.<anonymous> (recaptcha__en.js:307)
at Array.<anonymous> (recaptcha__en.js:44)
at js.$ (recaptcha__en.js:23)
at Array.<anonymous> (recaptcha__en.js:195)
at zO.g.next (recaptcha__en.js:370)
at P (recaptcha__en.js:41)

This is not related with my initial reported issue.

Hi Adam,

I wasn’t encountering any issues with Client IP. This is going to return my IP: https://www.whatsmyip.org, not the server’s IP. The issue was all along with wrong SERVER IP detected by Wordfence, because of SiteGround misconfiguration.

Refer to : https://imgur.com/DfOBk4N
(The IPs are not actual IPs, it was generated using random IP generator and for illustration purpose only.)

The red box is not a valid IP (the old IP). The green box is correct IP which got listed only after the wrong A record was removed. So now, how can this invalid IP be removed?

Really appreciate your perseverance in assisting me in solving this issue.
Thank you.

• This reply was modified 4 years, 7 months ago by Sha'ves.

Yes it is resolved.

The issue was with SiteGround having two A records with different IP addresses (old and new) pointing to my domain. They were giving me a run around for 4 days by saying I need to get a developer’s assistance as this was an plugin issue and then another support guy said its CloudFront’s problem.

So I disabled CF totally, pointed name servers back to SiteGround directly. The problem was obvious now, as the old site was loading because my domain was always pointing to the old IP.

I highlighted this to Siteground and they had to delete the A record with old IP, as I couldn’t see it my CPanel’s DNS Zone Editor. After propagation my site was loading fine. Miraculously, Siteground staff apologized for their mistake.

Wordfence scan works now as expected. Under diagnotics >> Connectivity >> Connecting back to the site says “Ok – with the correct IP address”.

But, IP(s) used by this server was only refreshed to actual IP after a couple of days.

Faced same issue. Rolled back to 4.3.3 until a fix is available for 4.4