GSynch not triggering automatic basic price calculation of Plugin Germanized

[Nikolaj Woroschilow]

Hi,

I’ve synced the following fields:
_unit
_unit_product
_unit_base
_unit_price_auto
_unit_price

All fields received the value from GSync.

But for some reason, there is a method which is probably not being triggered.
Here is what the devs of Germanized have to say.

”
On the one hand, it must be ensured via the custom meta field _unit_price_auto => yes that the calculation takes place automatically and on the other hand, it must be ensured that the corresponding methods provided by the Woo Core for saving the products are called so that the corresponding hooks are executed. which in turn are used by Germanized to (re-)calculate the basic price.
”

Regards

[Nikolaj Woroschilow]

If I uncheck and check the check-box within woocommerce, the product is showing the price correctly afterwards and only for that one product which I resaved after rechecking the check-box.

If I repead this process with other product, they will show the same result.

However, synching the product again with gsynch is resetting this calculations.

Regards

[Nikolaj Woroschilow]

test

[Nikolaj Woroschilow]

Here are more information:

h**ps://github.com/vendidero/woocommerce-germanized/blob/master/includes/abstracts/abstract-wc-gzd-product.php
h**ps://vendidero.de/dokument/products-rest-api

[nmedia]

Hi Nikole,

BPS plugin save meta as post meta of product post type, it will not be using any hook or function to trigger. It should be at the plugin end to manipulate these custom fields

[Nikolaj Woroschilow]

Hi,

the other dev told me the following:

”
Hi,

yes, I understood that. In the backend, the value is recalculated using JavaScript when the product edit page is accessed. However, this value may not be saved (after import). Germanized uses Woo-provided hooks that run as soon as a product is saved. Then the basic price calculation is triggered again and the basic price is calculated + saved. The import plugin you are using does not seem to use these hooks, so the prices are not included in the DB. So you have to implement an individual compatibility script for this plugin. To do this you need the hooks that the plugin provides as soon as a product has been saved/imported.

Greetings
”

Please tell me the information, they need to create an script for me. 🙂

Thank you.

[nmedia]

Hi,

we are saving data from sheet to store using WC API’s batch feature like:
https://woocommerce.github.io/woocommerce-rest-api-docs/#batch-update-products

and here metadata is being pushed inside:

{update: {id:123, name: Apple product, ...., meta_data:[{key:value}]}

also following action filter was used before we saved the product/chunk:
$products = apply_filters('wcgs_sync_data_products_before_processing', $chunk, $general_settings);

I hope it will help you

[Nikolaj Woroschilow]

Hi, it works now.
The issue was using a comma format instead of point when sync the numbers.

Regards

[nmedia]

Glad to see it works 🙂

Thanks for update. I hope you enjoying BPS version 8.

[Nikolaj Woroschilow]

The only thing I’m missing is to be able to export the “Managed Label” settings.

Also here is an UI improvement request.
Moving the editing area to the Top and making it sticky would support a quick and comfortable editing experience.
https://prnt.sc/rrfbcvlA0ZzM

The Issue at the moment is, that the user always have to scroll down to add or save.
Other issue is that every time I add a parameter the editing area is shifted downwards, which force the user to scroll down before saving is possible.

Another improvement would be to give the user a hint, after pressing save.
Otherwise the user have no idea if anything is happening, which can lead the user to press moreoften to see any visual change.
It happened to me. 😛

Next improvement would be to add a keyword filter at the top of the side-panel.
searching parameters to edit them is a pain at the moment.

And the last improvement would be to use accordions for parameter groups.
Eg.
standard parameters (collapsed by default)
custom parameters

This helps to hide the standards parameters and will remove distraction, result in less scrolling and in quicker finding the parameters the user is looking for.

[Nikolaj Woroschilow]

And I forgot to mention that editing the existing parameters will be great.
Otherwise the user is forced to remove the old parameter and add a new one.
This is unnecessary work.

Oh…and sorting features.
asc
desc
asc (by custom title)
desc (by custom title)

[nmedia]

Thanks for your feature request, we already thinking in the same way to optimize the Manage fields section. It will help us 🙂

[Nikolaj Woroschilow]

Perfect.
I hope to see the features as soon as possible. 🙂
Regards

[nmedia]

Sure

[Author]

Posts