kiburisa

Hello,

Thanks for your response.
I have tried to exclude all internal and external stylesheets and scripts following your instructions but the problem persists.
It makes sense since, as indicated in the first message, the mere fact that the “Enable Minify” option is activated (even with the “Process HTML”, “Process JavaScript files” and “Process CSS files” options disabled) already causes the problem.
It is as if unchecking those options is not helping file minification to occur, and it only stops occurring with “Enable Minify” disabled.
Any idea why this may be happening?

Thanks

@jimk1416 I’m sorry, I’m not sure about that. Maybe the plugin author can help with it.

Kind regards

Hi @vncdpllr ,

To speed up the process for you, I’m forwarding the steps that the Support team sent me to solve the issue, it worked like a charm for us:

1. Go to the page: Google Reviews / Settings / Advance
   2.Scroll down the page to the end
2. Find the last section: Execute db update manually
3. Type 1.8.6 in the version field and click Submit
4. After page refreshed, type 2.0.1 in the same version field and click Submit again

After that, the reviews will be updated in 24 hours.

Hope it works for you too ??

Done!

Hello @nikhilgadhiya,
Thanks a lot, the problem is fixed now.

All the best

I see! It doesn’t seem to make much sense but it’s obviously not related to this plugin. Apologies for the late reply and thanks a lot for your help ??

Thanks for your answer @ihereira

The exact message is:

“A payment of 2.621.033 ?.?. LBP failed to complete with the following message: Error: Amount must be no more than 999,999.99 ?.?.”

Actually we don’t really need to modify the maximum payment amount itself. We are using the Multi-Currency feature of Woocommerce Payments and it seems like the amount should be the equivalent for each currency, not specific to each currency (i.e. if the maximum amount in AUD was 5000, it should be 5291503,81 for LBP, not 999,999.99).

Best regards

In case someone else is struggling with this, I found the solution: set your custom price with the specific function wc_price

That way Multi-currency will recognize it as price-type and convert it.

@jdembowski that access was a trial access for a wholesaler in our e-commerce.

It doesn’t give anyone access to anything at all but the possibility to make a wholesale that we can freely cancel on our side.

The only purpose was to show the support team the wholesale prices not being converted.
Please take it easy, it’s something the whole internet can have without any issue at all.

Thank you @adamkheckler I’ll create a ticket.

Thank you @maykato

We finally decided to handle this with a different approach, in case you prefer to close this thread.

Regards

Thanks for the information.

Alternatively, are there any specific requirements that a custom price must have in order to be considered “price type” by Multi-currency and thus be converted correctly?

Kind regards

Thanks @erania-pinnera ,

Unfortunately the link that you sent was not working, so I used the one in the previous message (I assumed it was the same form you sent previously).

I mentioned this thread and asked for the secure link to provide our hosting provider access.

Regards

• This reply was modified 2 years, 11 months ago by kiburisa.

Nevermind, we contacted Google and those are ghost errors, meaning they’re being displayed, but they don’t actually exist and our products are active.

So everything is good in the feed.

Thanks for your help

Hi,

Our feed is targeted to Australia only (we used to have more countries but we removed all of them but Australia weeks ago in order to identify these errors).

Regarding the shipping issue. According to this documentation, shipping labels are only needed for groups of products:

“Shipping services can be associated with either all products or groups of products, the latter of which can be specified using the shipping_label attribute”

We have 3 shipping services (one for Australia and 2 for every other country) but all three are valid for all of our products. They are account-level shipping settings, so we shouldn’t need any shipping label. In case we do, I’m not very sure what kind of product attribute we need to create since it’d be the same for all products.

Regards

That worked perfectly, thanks @supportadtribes