Elliot

OK. this was a good hint. It has something to do with JS minification. But, when I exclude all JS files in On site messaging plugin, nothing happens. It does not work.

I was looking for specific JS files and I was seeing just this one:

/wp-content/plugins/klarna-onsite-messaging-for-woocommerce/assets/js/klarna-onsite-messaging.js

If I exclude just this file, on site messaging also does not work.

Are there any other JS files I am not aware of? I am probably missing something…

So, basically, on site messaging works only if I disable JS minification on the entire site. I am using WP Rocket. Maybe they jump in and help us here…

Thanks.

Hi,

Thanks for getting back.

Yes, that is the site and also – the live version, of course (you ca figure out what is the live version pretty easily from the logo). I tried from multiple browsers, mobile phones and tablets, incognito windows… and everywhere it was the same. The pop-up never appeared.

It is trange…

Thanks.

OK. Thanks. I will let them now.

Happy Holidays.

BR,
M.

Hey,

I forgot to update you. I am sorry.

I decided to rebuild everything from scratch. It looks like a faster solution then chasing that error.

But thanks for the help anyway.

BR,
M.

• This reply was modified 3 years, 8 months ago by Elliot.

Hey, no problem. I am glad that you have detected the issue. Before, I was thinking that I was doing something wrong…

BR,
M.

OK, got it.

Thanks for letting me know.

When location priority will work again?

BR,
M.

Hi,

Well, it is the same with Storefront. The error is still there.

Also, I have disabled all the plugins except Woo Commerce and Amazon Pay, cleared the cache and tried to make a purchase and the error was still there.

I do not know what is the problem. Does everything work correctly at your staging websites? Does anybody else complain?

It is strange…

Thanks.

BR,
M.

Hi,

This one.

But there are not just visual issues. The only active thing is Amazon log out button at that page. And under the payment method (under the radio button at the screenshot) it says that there is a fatal error.

It is written in German:

“Es gab einen kritischen Fehler auf deiner Website.”

Thanks.

BR,
M.

Hi,

Thanks. I will ask them.

BR,
M.

Hi,

This is an example for updating existing products. Of course, you can do this for new products as well, but this time I will explain how to update existing ones.

In order to have this work out, your products need to have all those locations already assigned. You can also assign locations to products using WP All import, but that is a different topic.

Lets begin now.

In WP All import, when you initiate an import, you will find an option called “Function editor”. There you can add your PHP code snippet.

But before you do that, you need to identify your custom fields for all your locations you are using for your stock.

Usually those fields are looking something like this: _stock_at_1234

This number part (1234) you will find under WooCommerce >> SLW settings. Those numbers are actually your stock location IDs. So they are different from website to website.

Lets pretend for this example that my stock location IDs are: 1234 and 5678, so I am using 2 stock locations.

So, now when we have all we need, this is the code snippet we have to implement in WP all import:

<?php
add_action( 'pmxi_saved_post', 'my_fix_stock', 10, 1 );

function my_fix_stock( $id ) {
	$product = wc_get_product( $id );
	if ( ! $product ) return;
	
	$stock1 = $product->get_meta( '_stock_at_1234', true );
	$stock2 = $product->get_meta( '_stock_at_5678', true );
    
	
	if ( empty( $stock1 ) ) $stock1 = 0;
	if ( empty( $stock2 ) ) $stock2 = 0;
	
	$product->set_stock_quantity( $stock1 + $stock2 );
	$product->save();
}
?>

You change these dummy values with your real ones, paste the snippet and hit save. Also, adjust this code for all your locations accordingly.

Upper, in the inventory tab, do not put any values in your stock quantity field, set manage stock to on and stock status has to be set automatically.

Those are all actions you need to take in that step. In the next step, you need to tell WP all import how to run the update, how to match the records.

So, records in your file will be matched with products on your site based on SKUs, product IDs, or whatever you are using as a special custom field (EANs, MPNs…)

You are updating existing products, so you set that checkbox and then you choose which data to update.

For this, you are using only custom fields and you are setting the option called: update only these custom fields and to leave the rest alone.

Custom fields are:

_stock_at_1234
_stock_at_5678
_stock
_manage_stock

Again, do not forget to change dummy numbers with your real values.

Save the settings, go to the next step and run the import.

Hopefully this helps.

• This reply was modified 3 years, 9 months ago by Elliot.
• This reply was modified 3 years, 9 months ago by Elliot.

Hi,

Yes. Everything is fine. I figured what is “the problem”.

The answer is here.

• This reply was modified 3 years, 9 months ago by Elliot.

OK. Everything is actually fine. There is just one small catch.

In order to have correct translations in emails, you, as a back end administrator or shop manager, need to use that exact language as backend interface language.

I was using English as my backend user language and the global website language was German. So, in that setup whenever I was working with orders, that language “issue” was there.

Then, I switched my user language to German and I did a test order and the language was correct.

So, Your user backend language is determining in what language those email parts will be.

Yes. That is exactly what I thought.

There is a 30-day free trial for magnalister. Could you please use that?

I could send you the installation file, but that would not work without some tokens you will get from them. For that you need an account there.

BR,
M.

Hi,

Regarding the issues with WP Rocket on some of the websites, I just want to confirm that after this last update, that issue is gone as well.

So, now everything works everywhere nice and smooth, like it is supposed to.

Thanks,
M.

Hi,

In my case it was enough just to go to Settings>>Permalinks and there under the “Optional” section I changed the permalink in the “Brands” input box.

Before the change it was written /all-brands/

So, what I did is I removed both slashes and I left only all-brands words in that box.

After that, brand pages were active again.

BR,
M.

• This reply was modified 3 years, 10 months ago by Elliot.