Coen Jacobs

Thank you for the suggestion. I’ll have a look at home this is easiest to implement. Would a filter work for you, so that you can add it to your themes functions.php or a separate plugin, so that it will always work – even after plugin (template files) updates?

Thanks for the feedback – much appreciated. Can you maybe open a separate support thread for issues like this? It’s much easier to work in support threads than support.

To give you some more ideas on template overrides; in the 1.0 version of the plugin, which will be released soon after all issues have been resolved, you can override any template file you want in your theme, but adding the file with the same name in a listings directory. Should you now want to override a template file and it doesn’t work, please file a new support thread as mentioned before, or a new GitHub issue in our tracker. Thank you!

Yes, absolutely Bill. All feedback is absolutely valuable, not just developers feedback. We’re confident that the majority of users of our platform aren’t developers, so non-developer problems are probably the most important for us. ??

Please create a new forum thread for each problem you find. It’s easier for us to deal with multiple issues in separate threads. Thank you!

Thanks again for reporting this. I’ve just released version 0.2.2 and that version fixes this issue. Please let us know if this resolved all the issues that you have. ??

Can you please enable debug mode on your site and activate the Listings Jobs plugin again? This might show us the actual error that is being suppressed under that 500 HTTP error.

Can you also please verify that you’re running the latest stable version of Listings Jobs (currently v0.2.1)?

Please don’t use this topic for support requests, but open separate topics. This is purely an announcement topic and not for support requests. Thank you.

Can you please open a separate support topic explaining the issue, detailing about what is not compatible with the latest releases of WordPress? I’d be happy to fix any issues.

(Let’s keep the conversation in English here, so it can be used by other people for reference)

Yes, as a vendor you are required to check the name and business address of your buyer if they are trying to be VAT exempt. This can not be automated though and needs to happen by the buyer after the order is received, unfortunately.

No, it’s actually not required to check the business name as well. As you can see with the official VIES VAT number validation tool, all that is required to validate a VAT number is the locale code and the VAT number itself.

So that’s what this plugin does (among the other features, of course), but it’s the same as all the other VAT validation plugins out there.

markmich, if you can’t find the actual line that I pasted in here, try searching for just the function name woocommerce_cart_totals and you’ll probably find one in your (child) theme that maybe has the <?php above it, or ?> below it. Same solution applies to this change, just strip out the function call entirely.

For everyone else reading this, the steps as explained by ericbakuladavis are actually the ones I used to recommend when I was still working on the WooCommerce plugin. ??

Thanks for the detailed report. I know what’s causing both of these issues and will have a fixed release available soon. You can further track the issues on our GitHub development repository:

• empty modules array foreach error
• parse error on ()[] symbol error

Sorry for the late reply here. Can you please provide me with the error message that is being shown when you get the blank page?

You can force WordPress to show error messages by enabling the debug mode.

Search for just that function call in your templates. It doesn’t have to wrapped by <?php and ?> on the same line.

For your checkout page, that’s a different issue and unrelated to this change.

I’ve provided some more details on how to fix this, in this post.

This behaviour was introduced in this commit. The function call in the template got removed, added back via an action. Every theme overwriting this template will still have the original function call, as well as the function added via the action. This shouldn’t be pushed in a fix release like this, in my humble opinion. But now it’s there, let’s resolve this.

Resolving the issue
Resolving this issue is actually fairly easy. Your theme will have the cart/cart.php overwritten in the woocommerce folder of your (child) theme. In there, you will find this line (or at least something similar calling that same function):

<?php woocommerce_cart_totals(); ?>

You need to remove this line from your overwritten template file and your cart totals should only appear once.