[Resolved] Toolset WooCommerce Views causes blank error on checkout page, can't pay

[Author]

Posts

[Marcel]

When I have WooCommerce Views enabled, I get a blank error on the checkout page. Therefor, users can't complete the checkout and thus can't get to the payment provider. When I disable WooCommerce Views, everything works well.

[Shane]

Hi Marcel,

Thank you for getting in touch.

It seems there is a fatal error appearing on this page given that it is blank.

Would you mind enabling the wordpress debug and checking again to see what exactly is triggering this fatal error ?

Thanks,
Shane

[Marcel]

Hi Shane,

When I enable debug in wp_config, the order overview and payment method field keep having a spinning loading circle on them, I don't get any debug information. I would like to give you FTP credentials, but I can't find how to make a reply private...

[Shane]

Hi Marcel,

I've enabled the private fields for your next response.

Thanks,
Shane

[Shane]

Marcel,

I'm assuming this is the checkout page hidden link

Also see my screenshot. It loads up fine for me.

Could you send me a screenshot of what you are seeing on your end.

Thanks,
Shane

[Shane]

Hi Marcel,

I'm not seeing this. Have a look at my screenshot

The errors show up fine for me.

Perhaps try using a different browser.

Thanks,
Shane

[Marcel]

The blank error is after you filled in all the fields... the error you're seeing is because you didn't fill in the fields yet. The red bordered error at the top is put there by me of course.

[Shane]

Hi Marcel,

Not sure if you've tried this but I would recommend disabling all the non toolset plugins and trying again.

I've just setup a fresh install of wordpress with Woocommerce along with the Woocommerce views and the payments would go through with no issue at all.

I'm not getting any blank errors on my end.

Thanks,
Shane

[Marcel]

Hi Shane,

I did some more testing. It seems there's a conflict between WooCommerce Views and Yoast SEO. If I disable one of those, everything works fine. However, if they'e both active, the error occurs.

Can you reproduce that?

[Shane]

Hi Marcel,

I've got other tickets with the similar issue.

It has already been reported to our development team for a more permanent fix.

However our 2nd tier supporter post that removing a line in the seo plugin fixes the issue but this isn't a recommended fix.

I would suggest that we wait on a permanent fix from our development team.

Thanks,
Shane

[Marcel]

If you have other tickets with similar issues, why didn't you say "try to disable Yoast" instead of letting me spend a lot of time on testing? I provided the login details, so you could have checked this scenario yourself as well...