jackennils

Thank you Yordan for your help ??

Dankesch?n, das schaue ich mir an. ??

Hallo und danke für die Rückmeldung.

So ganz funktioniert das aber nicht. Wenn ich beide Versandarten zur Verfügung stelle, dann habe ich bei einem Artikel im Warenkorb mit der günstigeren Versandklasse zwar die Wahl zwischen dem Versand als Warensendung oder Paket aber wenn ich sowohl einen Artikel mit der günstigeren Versandklasse als auch einen Artikel ohne Versandklasse im Warenkorb habe, bietet er weiterhin den günstigeren Versand an, obwohl dann nur der teurere greifen sollte.

Thank you very much Dennis! Excellent support – even on a Sunday. ??

Thank you for confirming Olaf!

Okay, I did some additional testing and I figured out that 3.16.8 is actually working fine as long as I keep the official WC Amazon Pay plugin deactivated. As soon as I activate it, I get the 503 when trying to go to cart/checkout.

3.16.7 works fine with Amazon Pay Plugin (2.5.1).

So something in 3.16.8 must have broken compatibility with the Amazon Pay plugin.

@olaf23 / @networka : Do you also use the Amazon Pay plugin?

The php log does not show any entries which could possibly be related to this issue.

I did replicate the issue on my staging environment and after deactivating all extensions/plugins and re-activating them one by one, I did not experience any issues until Germanized was activated (as the last of them).

Sounds good. Thanks for the help ??

It even works with minification enabled. Only merging of Java scripts files needs to be disabled. Any idea what could be the root course for that?

I would hate to lose this function, as otherwise a lot of individual JS files would have to be loaded.

As you can see in the video which I have added in the first post, I am on 5.7.13.

I think I have found the issue. After cloning the live site for the staging environment, I had to empty the OMGF cache so that fonts are downloaded again. Now it works again. ??

I get this error in my debug log:

[19-Jan-2024 16:10:30 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify.php:131) in /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/themes/woodmart/inc/integrations/woocommerce/functions.php on line 2311

Maybe that helps?

Thank you Pepe.

I already did a conflict test on my staging site. I actually did a lot of testing. I have disabled all plugins except for WC and I have used Storefront to test it with. The problems still occur. And as I have stated in my above reply, I’m not the only one having such problems.

I believe you – really, without any doubt – that a fresh install works. But maybe there is a bug in the upgrade process which leads to these issues?

No, I wrote that all plugins have been disabled except for WC and OMGF.

The debug log shows this error when OMGF is active:

`[19-Jan-2024 16:03:01 UTC] PHP Fatal error: Uncaught TypeError: array_keys(): Argument #1 ($array) must be of type array, bool given in /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Helper.php:220
Stack trace: 0 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Helper.php(220): array_keys(false) 1 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Helper.php(184): OMGF\Helper::cache_keys() 2 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Frontend/Process.php(613): OMGF\Helper::get_cache_key(‘xts-google-font…’) 3 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Frontend/Process.php(391): OMGF\Frontend\Process->build_search_replace(Array) 4 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/class-wp-hook.php(324): OMGF\Frontend\Process->parse(‘…’) 5 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘…’, Array) 6 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Frontend/Process.php(298): apply_filters(‘omgf_buffer_out…’, ‘…’) 7 [internal function]: OMGF\Frontend\Process->return_buffer(‘…’, 9) 8 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/functions.php(5373): ob_end_flush() 9 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/class-wp-hook.php(324): wp_ob_end_flush_all(”) 10 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 11 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 12 /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-includes/load.php(1260): do_action(‘shutdown’) 13 [internal function]: shutdown_action_hook() 14 {main}

thrown in /www/htdocs/w01a4bb6/web/staging-lumiqy2/wp-content/plugins/host-webfonts-local/src/Helper.php on line 220′

Yes it seems, WC 8.5.1 is a total mess. I hope it’s a problem on their side and they’ll fix it soon.

• This reply was modified 1 year, 1 month ago by jackennils.

Yes, for cart and checkout. Of course. But I was not talking about cart or checkout. I was talking about normal product pages. And as I have tried to explain, it has worked until WC 8.4. So something must have changed with the latest WC 8.5.1 update that WPO is not working properly anymore.

Did you watch the video in my first post?

Same here, it’s happening since the update to 8.5.1, see my topic:
https://www.ads-software.com/support/topic/since-8-5-1-selecting-variations-and-adding-item-to-cart-not-working-anymore/

Do you use WP-Optimize?