doffine

Hey @bungeshea,

no problem. We are using Windows 10 Pro 1909 64 Bit.

It only happens in Firefox – it seems in any versions at least between 71.0 (64-Bit) and 72.0.2 (64-Bit). It doesn’t happen in Chrome or Opera.

Perhaps it helps if you google e. g. “downloadable font: OS/2: Bad sTypoLineGap”?

Note: The error is only logged to console when you load the backend page for the first time. After this and while you are browsing backend pages the error is gone. But you can get it back on any backend page by forcing reload and press STRG+F5. In the WordPress’ frontend the error never happens.

Many greetings,
-doffine

Hey @fabiorino,

great – many thanks for the perfect support!

-doffine

Hey @nickirongate,

thanks for coming back to us!
What you discovered is exactly the problem. We want the message…

Sie haben Ihren Mindestbestellwert von 70,00 € noch nicht erreicht. Ihr aktueller Bestellwert beträgt 10,00 €.

…to be shown additionally on the checkout page, too – not only on the cart page.

The wc_add_notice() is performed on both pages but the message is shown only on the cart page. Hasn’t this been the case earlier, that wc_add_notice() messages are printed out on the checkout page, too?

We noted that using wc_print_notice() it is possible to show the message on the checkout page. But if we use ONLY wc_print_notice() (although with an error paramter set) on the checkout page the checkout isn’t blocked. But it must be blocked. So the only possibility we can use at this moment seems to be to perform both functions consecutively on the checkout page:

wc_add_notice( 
				('Sie haben Ihren Mindestbestellwert von <b>'.number_format($minimum_cart_total,2,',','').' '.
                 get_woocommerce_currency_symbol(get_option('woocommerce_currency')).'</b> noch nicht erreicht. Ihr aktueller Bestellwert beträgt <b>'.
                 number_format(WC()->cart->subtotal,2,',','').' '.get_woocommerce_currency_symbol(get_option('woocommerce_currency'))).'</b>.','error');

AND

wc_print_notice( 
				('Sie haben Ihren Mindestbestellwert von <b>'.number_format($minimum_cart_total,2,',','').' '.
                 get_woocommerce_currency_symbol(get_option('woocommerce_currency')).'</b> noch nicht erreicht. Ihr aktueller Bestellwert beträgt <b>'.
                 number_format(WC()->cart->subtotal,2,',','').' '.get_woocommerce_currency_symbol(get_option('woocommerce_currency'))).'</b>.','error');

Where the first function blocks the checkout and the second prints out the message.

This seems to be a little bit odd to us.

Hello Rustaurius,

we never intended to post any login credentials in this WordPress forum.

The other “translation” issue is not resolved yet. We are not using WPML or any other plugins as stated above. I hope you can help us out here – we are not able to fix this problem.

Hello @scsiraidguru,

thank you very much for your well-founded advice. When I came to the office this morning I saw that in the meantime the auto update had taken place – this morning at 7am. This is about 30 hours after all of our other WordPresses auto updated – and without me having done anything.

But allow me a last question: Of course I’m playing with the thought going to PHP 7.3.x for quite a time because of the obvious advantages. And perhaps this auto update issue wouldn’t have happended. But we use about 150+ different plugins and about 30+ different themes. So I’m worrying if we will get problems because of some not updated components. All of the plugins are explicitly not outdated since we always take care to use newest and if possible wide spread components. So I wanted to wait as long as possible to upgrade to PHP 7.3.x (as mentioned above its 190 WordPresses) and perform it then for all WordPresses, since I want to have a landscape as homogeneous as possible. So I don’t want to update this bunch of WordPresses and the other not – controlling every single component. This is the reason for me to adjourn the mass upgrade as long as possible – so that every component manufacturer had enough time to upgrade compatibility to PHP 7.3.x.

So the question is: Have you any experience in upgrading WordPresses to PHP 7.3.x at this point of time? Does this process go fluently mostly or are there still frequent issues with the use of PHP 7.3.x?

Many thanks for your help and opinion again,
– doffine