jomo

Hyyan retired this plugin, though it is possible to get it working for this sort of thing and has been done on GitHub it is not possible to maintain the plugin for all the woo changes happening

This plugin is no longer maintained and the author has closed it on GitHub

1. Yes development is stopped, Hyyan has archived project
2. As Divi is a paid supported product you could ask them

synchronisation options by product are not supported
synchronisation options are on a field by field basis, see https://github.com/hyyan/woo-poly-integration/wiki/Settings-Metas

please note:

• this project is archived
• there is specific help on this point here:
  https://github.com/hyyan/woo-poly-integration/wiki/Product-Meta-and-Custom-Fields
• before archival of this project there were more recent updates which may not be published to wordpress: https://github.com/hyyan/woo-poly-integration/releases

I use the plugin with translated emails, it should work,
to report an issue, please post on:
https://github.com/hyyan/woo-poly-integration/issues
including the full details especially the plugin versions used.

Also if you are using recent versions of WooCommerce it is worth checking the latest version at:
https://github.com/hyyan/woo-poly-integration/releases
as at time of writing 1.5.2 is not published to www.ads-software.com

I don’t know what versions you were trying but variations and stock are working in the latest version at:
https://github.com/hyyan/woo-poly-integration/releases
And there are very few open issues.

In general you have a point: sadly WooCommerce is not designed to support true multilingual or multicurrency operation and whichever plugins you choose are vulnerable to issues with upgrades which need to be handled with great care.

Hi, that line of code looks like it is historic and should never be called in recent plugin versions, specifically to get to that line of code means that Polylang does not have the language requested..
You could try commenting out the related line:

//20190630: old code used in previous versions of this plugin
$polylang->curlang->locale = $languageLocale;

or raise the issue with more detail on https://github.com/hyyan/woo-poly-integration/issues
as there is no support on this forum

you could have a compatibility issue with a particular payment gateway plugin or theme or combination of plugin versions.

Please try with the default WooCommerce payment gateways and standard WooCommerce theme such as Storefront to confirm.

The issue template for raising a new issue at https://github.com/hyyan/woo-poly-integration/issues/new/choose explicitly asks that you confirm this, version details of key plugins and WooCommerce status report in particular for the active plugins and versions. This information is necessary to be able to provide any advice on the issue.

Please test and re-raise on Github as appropriate as there isn’t support on these forums.

this is an option called the Fields Locker, if you don’t like it you can turn it off at Settings, WooPoly, Fields Locker: /wp-admin/options-general.php?page=hyyan-wpi

The idea is that the field which are synchronised should be updated in the shop base language and are then synchronised to the translated versions.
Only the fields which are selected for synchronisation are disabled.
Unless you turn the feature off.

standard update, though is multisite. scheduled actions were run but the database update complete message would not go away until wc-update-db-reminder forcibly actioned in wp_wc_admin_notes.

error messages do not appear in normal use either by admins, or by users successfully checking out via multiple gateways.

wp-cron is disabled and cron is run by wp-cli wp cron event run –due-now for each site, however error in logs do not appear to match cron timetable either

error doesn’t appear in local development environment

initial conclusion, could be penetration attacks, trying some url which isn’t part of normal operation, will try to capture url

I can’t tell but if the product count seems wrong, use the tools available in WooCommerce, Status, ie:
/wp-admin/admin.php?page=wc-status&tab=tools

Options 1, 5 and 6 are relevant, in English:
– Clear transients
– Regenerate [Product Lookup tables]
– Recount terms

Also as usual, if something doesn’t appear to show up on a page, check for caching at all levels, clear page output caching, clear transients – if you have Redis or other caching tool enabled, flush that etc, add a url parameter to ensure you break any proxy caching etc.

Lastly there is no support on this forum, however if not solved by the above you are able to replicate the issue in more detail you are welcome to open on: https://github.com/hyyan/woo-poly-integration/issues

since 1.5 is now released on www.ads-software.com and declares compatibility with WooCommerce 5.0, I’m closing this thread about WooCommerce 4.0 compatibility.
Please report any new issues with 1.5 or WooCommerce 5 on https://github.com/hyyan/woo-poly-integration/issues

[that example wouldn’t work as is as is not handling the adding and removing which is the event it really needs to]

@stasz please feel free to add comments and requirements for import to the open issue at: https://github.com/hyyan/woo-poly-integration/issues/208

tbh I’m not sure what the import should do, other than trigger a synchronisation on any items which already exist and are linked to translations which is what the code was attempting to do here.