• Resolved fredpeng

    (@fredpeng)


    After I updated to version Version 3.3.2, I cannot active the plugin. It shows:

    Plugin could not be activated because it triggered a?fatal error.

    I think the new version has a bug.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author ali2woo

    (@ali2woo)

    Hello, please send the request to our support center: https://support.ali2woo.com, we will check the issue

    Thread Starter fredpeng

    (@fredpeng)

    Hi, I have reported this issue to your support center. I think it is easy to re-produce from your side.

    Plugin Author ali2woo

    (@ali2woo)

    We have tested alinext lite on our local server (deactivate/activate function). We don’t see any errros.
    Please make sure you have php 8.0 installed on your server as well as woocommerce.

    Also, please contact our support.

    Thread Starter fredpeng

    (@fredpeng)

    Hi, yes, my php is 8.3.6. And I can see the error log from system status. Please check if it will help.

    2024-05-27T19:44:15+00:00 Critical Cannot declare class AliNext_Lite\ApplyPricingRulesProcess, because the name is already in use

    Additional context{ “error”: { “type”: 64, “file”: “\/var\/www\/hsapp\/content\/plugins\/ali2woo-lite\/includes\/classes\/utils\/ApplyPricingRulesProcess.php”, “line”: 15 }, “backtrace”: [ { “file”: “\/var\/www\/hsapp\/content\/plugins\/woocommerce\/includes\/class-woocommerce.php”, “line”: 377, “function”: “critical”, “class”: “WC_Logger”, “type”: “->” }, { “function”: “log_errors”, “class”: “WooCommerce”, “type”: “->” } ] }

    Plugin Author ali2woo

    (@ali2woo)

    Need to check your files through ftp. Let’s continue conversation in your support ticket.

    Thread Starter fredpeng

    (@fredpeng)

    OK. Thank you.

    Plugin Author ali2woo

    (@ali2woo)

    We close this thread, because work on it in our support center.

    • This reply was modified 6 months ago by ali2woo.
    Plugin Author ali2woo

    (@ali2woo)

    We have release new plugin version 3.3.3 today.
    It should prevent the activation error.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.