aiolosweb

Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Forum: Plugins
    In reply to: [GTM4WP - A Google Tag Manager (GTM) plugin for WordPress] Function wc_enqueue_js deprecated since version 10.4.0!
    aiolosweb

    (@aiolosweb)

    2 months ago

    Hello,

    I’m experiencing the exact same issue on my setup.
    Additional confirmation

    The deprecated call to wc_enqueue_js() is triggered via:

    gtm4wp_woocommerce_datalayer_filter_items()
    /integration/woocommerce.php:799

    It appears during the gtm4wp_compile_datalayer process and is visible in Query Monitor. ⚠️ Impact

    In my case, this results in:

    • Continuous deprecated warnings in logs
    • Increased log size due to repeated calls
    • Potential future compatibility risks with WooCommerce updates

    Environment

    • WooCommerce: latest (10.5+)
    • WordPress: latest
    • GTM4WP: 1.22.3
    • CheckoutWC also active

    Would appreciate any update on:

    • Planned fix timeline
    • Recommended workaround (if any)

    Thank you!

    Forum: Plugins
    In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Critical error after latest Yoast SEO update
    aiolosweb

    (@aiolosweb)

    2 months, 1 week ago

    Hi Yoast team,

    We are seeing the same fatal error in our logs after the latest Yoast SEO update:

    Declaration of Yoast\WP\SEO\Task_List\Application\Tasks\Complete_FTC::get_call_to_action():
    ?Yoast\WP\SEO\Task_List\Domain\Components\Call_To_Action_Entry
    must be compatible with
    Yoast\WP\SEO\Task_List\Domain\Tasks\Task_Interface::get_call_to_action():
    Yoast\WP\SEO\Task_List\Domain\Components\Call_To_Action_Entry

    Our details:
    1) The error appeared during the update process and was logged in the fatal error log. At the moment, the site appears to load normally.
    2) The update path was from Yoast SEO 27.1.1 to 27.2.
    3) WooCommerce is installed on the site.

    In our case, the error appeared in the logs multiple times during the update process.
    We also noticed the same error in multiple log files, including fatal-errors and woo-feed-fatal-errors, which suggests the issue may be surfacing during plugin loading rather than being caused by the feed plugin itself.

    Please let us know if you need any additional details, plugin versions, or environment information.

    Forum: Plugins
    In reply to: [Mollie Payments for WooCommerce] Component was not unmounted correctly
    Thread Starter aiolosweb

    (@aiolosweb)

    6 months, 3 weeks ago

    Hi Femi,

    Thank you for your clarification.

    However, as we’re now entering a critical sales period with upcoming discounts and high checkout traffic, it’s important that everything runs perfectly and without any console warnings or unexpected behavior even if harmless.

    Please make sure this issue is fully resolved and the warnings are suppressed in the next update as soon as possible.

    Forum: Plugins
    In reply to: [Mollie Payments for WooCommerce] Component was not unmounted correctly
    Thread Starter aiolosweb

    (@aiolosweb)

    6 months, 4 weeks ago

    Hi Femi,

    Thank you for checking on your side.

    I can confirm that we’re using the Classic Checkout (with [woocommerce_checkout] shortcode).

    The console error does appear immediately when entering the checkout page, even with all other plugins disabled meaning only WooCommerce and Mollie are active. So it’s reproducible in a clean environment.

    While the checkout itself still loads, the console shows the same recurring Mollie-related error as before, which indicates that the component lifecycle isn’t being handled correctly when the page initializes.

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