• Resolved joy0114

    (@joy0114)


    Hi,

    Do you think to publish a new release of AST in order to solve this issue appeared with WordPress 6.7 ?
    Thanks a lot.
    Best regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author gaurav1092

    (@gaurav1092)

    Hi @joy0114,

    Yes, we’ve addressed this issue in the latest version of AST (3.7.3). Please update to the latest version to resolve the warning.

    Best regards,
    Gaurav

    Thread Starter joy0114

    (@joy0114)

    Hi Gaurav,

    Strange … I’m using 3.7.3 and wordpress debug tells me the “well known” warning about textdomain, is always present.
    All server caches had been purged (files, opcache, object cache, js).

    Do you think it could be relative to Loco Translate which deals with all my plugin’s translations ?

    In Loco, I’ve got your translation, in plugins/woo-advanced-shipment-tracking/lang/woo-advanced-shipment-tracking-fr_FR.po
    And mine (not updated with your plugin), in languages/loco/plugins/woo-advanced-shipment-tracking-fr_FR.po

    I precise that Loco Translate is loaded before AST.

    Thanks if you have any idea …
    Best regards

    Plugin Author gaurav1092

    (@gaurav1092)

    Hi @joy0114,

    Thank you for reaching out!

    To help identify the issue, could you please try deactivating the Loco Translate plugin temporarily and check if the warning still appears? This will help us determine if Loco Translate is causing the conflict.

    Let me know how it goes, and we’ll assist you further if needed.

    Best regards,
    Gaurav

    Thread Starter joy0114

    (@joy0114)

    Hi Gaurav,

    Ok, finally solved with several purges and purges of ALL caches …

    Thanks !
    Best regards

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.