Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Concept Image

    (@devci)

    Hello,

    Sorry for the late reply.
    I can’t access the test website anymore so I can’t try to reproduce the warning.

    My WPML account is configured in french so I’m automatically redirected to french WPML support. Do you want me to create it on the english support so that you can take of the new ticket ?

    Regards,
    Valentin – Concept Image

    Thread Starter Concept Image

    (@devci)

    Hello,

    Thanks for the demo website.

    I achieved to reproduce the bug only once :
    – I created a custom field associated to products
    – I created product attribute and terms
    – I created a variable product (Test product) with variations and filling the custom field
    – I went to WooCommerce -> WooCommerce Multulingual -> I clicked the “+” icon to translate the product to spanish and I had a fatal error.

    When I had this fatal error, I think the ATE was enabled in options.

    After this, the “+” icon was replaced by an orange gear icon and I could access translation from there without problem.

    I disabled ATE, duplicated the product (Test product (Copy)) and tried to translate with the same manipulation but I had no errors.

    I re-enabled ATE, created another variable product without duplication (new product), and again, tried to translate to spannish from WooCommerce Multilingual menu and now I have a WPML error message in BO when I click on the orange gear icon to translate “new product”. The error says “WPML didn’t manage to translate this page.”, you can see this on the demo website.

    In addition to that, I made tests with and without ATE on my website, and it didn’t change the problem, I still have the Fatal Error with and without ATE.

    Also, as said in my previous message, the error that I have on my website is a juste PHP Warning with PHP 7 and a fatal error on PHP 8.
    I saw that the demo website you gave me is on PHP 7 with WP_DEBUG set to false. It may be possible that the bug occur on the demo website but the warnings are not displayed.

    Kind regards,
    Valentin – Concept Image

    Thread Starter Concept Image

    (@devci)

    Thank you, I’ll try this.

    Thread Starter Concept Image

    (@devci)

    Ok, thank you.

    Thread Starter Concept Image

    (@devci)

    Ok thank you for your help.
    I’ll try to find an other solution so.

    Can you simply indicate me if this requirement is specific to your plugin or if it’s a wordpress one ?

    Thread Starter Concept Image

    (@devci)

    Thank you for the reply.

    However, I can’t change the database settings. So, each time a new meta is created, associated meta_id are separated by 10.
    So it couldn’t work.

    To associate the ACF fields meta the link are post_id and meta_key:

    Exemple:
    post_id = 18952 / meta_key = search_content_extra
    post_id = 18952 / meta_key = _search_content_extra

    I can’t get how the query work exactly.
    Is there an other table involve in the request ?

    Even if the auto increment range change now, I won’t be able to change already saved meta.

    Thread Starter Concept Image

    (@devci)

    I’m still investigate on this issue.
    When I display the sql request I can see this:
    b.meta_id = a.meta_id + 1

    I think it support my previous comment about database auto_increment range.
    Is there any reason to have this behavior ?
    Post_id and meta_value are they not enough for the request ?

Viewing 7 replies - 1 through 7 (of 7 total)