bytefarmer

/plugins/eu-vat-for-woocommerce/includes/class-alg-wc-eu-vat-core.php line 466

echo get_option( 'alg_wc_eu_vat_advanced_vat_shifted_text', __( 'VAT SHIFTED', 'eu-vat-for-woocommerce' ) );

So you can translate this string in the WPML String Translation tool, but not the English version afaik

Other options in this plugin are translatable. Eg if you go to the main options under the EU VAT Number tab in Woocommerce you see the first option for label for VAT number, there you can enter

[alg_wc_eu_vat_translate lang="EN" lang_text="VAT number" lang="FR" lang_text="Numéro TVA" not_lang_text="BTW Nummer"]

in the text box for the label and it will translate the field accordingly. A bit of strange way of working but it works…

While translating I checked the source code of the plugin and it will also store this text as metadata on the invoice object. In case you use another plugin to generate the PDF.

Only drawback is that in our country we need a specific sentence and I need to translate the original English string as well in orde to comply with regulations here.

I was just checking this functionality and I have VAT SHIFTED on the invoice when I use the invoice plugin in combination with their UK/EU VAT number manager plugin which seems to do the right tricks

• This reply was modified 1 month, 2 weeks ago by bytefarmer.

Those categories already had images assigned to them. I’m using another plugin now from IKS that has this option available.

Thanks for your reply. I actually had a similar issue with another plugin. I then discovered the lazy loading of ‘Riode’ theme was causing some scripts to run before the DOM was properly populated, thus omitting the necessary event listeners. Disabling the Lazy Loading function was the solution!

Hi, I’m having the exact same issue. I’m running the latest version. In the customizer I can see the expand (+) class wpb-submenu-indicator, but on the actual page that element is not rendered.

https://sundar.be/winkel/

I just restested the site and the optimization (minify + bundle) is working fine again.

I stumbled across this thread while facing the same issue. However, this is now not caused anymore by JS but by the UCSS generated by litespeed cache. I found that including following CSS selectors in the UCSS selector allowlist solves it:

.main-header-menu
.menu-item
.ast-header-break-point .main-navigation ul .menu-item .menu-link
.menu-toggle
.main-header-menu-toggle
.ast-mobile-menu-trigger-minimal
.toggled
.ast-mobile-header-content
.ast-builder-menu-mobile
.ast-builder-menu
.ast-builder-menu-mobile-focus-item
.ast-builder-layout-element
.site-header-focus-item
.ast-main-header-nav-open
.ast-header-break-point .main-header-bar-navigation
.ast-header-break-point .main-navigation .stack-on-mobile li