• Resolved ashwoth

    (@ashwoth)


    I installed open ticket community edition (version 1.10.21 ) to see how it works before investing on the enterprise edition. I have WP 4.2.2 and Woo Commerce Version 2.3.10. The plugin installed successfully but it did not activate. I manually attempted to activate it and got the following error –
    Plugin could not be activated because it triggered a fatal error.

    Warning: include_once(/home/xxxxxx/public_html/wp-content/plugins/woocommerce/includes/libraries/class-lessc.php): failed to open stream: No such file or directory in /home/xxxxxx/public_html/wp-content/plugins/opentickets-community-edition/opentickets.php on line 505

    Warning: include_once(): Failed opening ‘/home/xxxxxx/public_html/wp-content/plugins/woocommerce/includes/libraries/class-lessc.php’ for inclusion (include_path=’.:/usr/local/lib/php’) in /home/xxxxxx/public_html/wp-content/plugins/opentickets-community-edition/opentickets.php on line 505

    Warning: include_once(/home/xxxxxx/public_html/wp-content/plugins/woocommerce/includes/libraries/class-cssmin.php): failed to open stream: No such file or directory in /home/xxxxxx/public_html/wp-content/plugins/opentickets-community-edition/opentickets.php on line 507

    Warning: include_once(): Failed opening ‘/home/xxxxxx/public_html/wp-content/plugins/woocommerce/includes/libraries/class-cssmin.php’ for inclusion (include_path=’.:/usr/local/lib/php’) in /home/xxxxxx/public_html/wp-content/plugins/opentickets-community-edition/opentickets.php on line 507

    Fatal error: Class ‘lessc’ not found in /home/xxxxxx/public_html/wp-content/plugins/opentickets-community-edition/opentickets.php on line 521

    https://wordpress.org/plugins/opentickets-community-edition/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author loushou

    (@loushou)

    Hey @ashwoth,

    I see what you are saying. Apparently WooCommerce released its new version right before ours came out, and they moved a few libraries we depend on. I will fix this directly.

    Loushou

    Thread Starter ashwoth

    (@ashwoth)

    Loushou,
    Thank you for your help. Will that fix be this morning?

    Plugin Author loushou

    (@loushou)

    Hey @ashwoth,

    First, I want to thank you. This apparently has slipped past our QA for quite some time, because a few steps our QA process need to be refined. I have been noticing a drop in our active installs recently and I could not seem to figure out why, but this clearly is it. You are the first person to see this and actually report it, and for that I thank you. I am going personally make sure that our internal QA process is updated so that this does not happen again. Again, really, Thank You.

    Second, it would seem that this lib has been missing for several versions. I had to back track just to find a copy that I could put in our plugin, instead of relying on the core WC to provide it. I have created a fix for this, and released it just now, 1.10.22. Because of this, I will also be starting a conversation in our internal meetings about not relying on WC to provide us certain code anymore, because I want to minimize the risk of this happening again.

    This should resolve the problem. If it does not, contact me here immediately.

    Thanks again,
    Loushou

    Thread Starter ashwoth

    (@ashwoth)

    Loushou,
    You are amazing. Thank you for the update. The error is gone.

    Plugin Author loushou

    (@loushou)

    No problem at all @ashwoth, and thanks again for reporting it!

    Loushou

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

The topic ‘plugin not activating – has fatal error code’ is closed to new replies.