bsteeletx

Any plans for an update? Or at least a direction I can look at to fix it myself?

Alright! Well, thanks for your help!

They provided a picture

You can see the cart at the bottom. I’m fairly certain that they’ve purchased before, as they mentioned that they’ve never seen that issue before. There has not been any refunds, and the product has not had a different product ID, nor has any other product used that ID.

The product that was affected is located here

The good news, it’s only happened the one time, I was really worried it was going to happen much more often. ??

That plugin looks pretty good, but our site is too large, unfortunately for the plugin.

Thanks for the idea though!

Hmm, the host idea is a good one as we just did switch to a new host, and we hadn’t experienced this before the new host.

The message comes up through cloudflare.

Well, when switching to a new browser, I don’t experience the same issues (for an undetermined amount of time). But yes, I guess calling it ‘fixed’ is a small stretch.

I’ll check with my host and see what they might be able to tell me.

Thank you!

if it were a theme or plugin, wouldn’t it affect each browser instead of completely being fixed if I go to a different browser?

Found out that woocommerce was the culprit.

For anyone else, here’s the link to fix the issue:

Tried that one too. It last longer, but I eventually got the problem to pop up again. ??

Nope, still the same issue. ??

Anybody else have an idea on this?

Thanks for your response, Juthawong!

The rest of the code is just standard WooCommerce code. The logic behind what we’re trying to do seems sound: If this particular user has already bought the product, print out ‘Purchased’ instead of the WooCommerce cart you were going to post.

I’ll try the is_user_logged_in() function and report back…

I’m sorry, I don’t see a difference between

“this couldn’t possibly be a WordPress issue”

and

“It won’t be anything to do with WordPress”

Both responses are basically saying, “not our fault”, when it was working fine with a non-WordPress system, and now aren’t working very well, where the only change (albeit a big one) is WordPress.

Your response is rather insulting actually.

But, just to play your little game, I’ll talk with my host. $100 says they’ll blame WordPress–then what are you going to tell me? The same thing?