LifterLMS Fatal Error

  • Resolved DManIT

    (@dmed)


    3 weeks, 3 days ago

    When GravityKit’s Gravity View plugin is activated, LifterLMS cannot be activated. I reached out to GravityKit and they provided the following response.

    The LifterLMS/GravityView issue can be reproduced with the following steps on the plugin page:

    1. Deactivate LifterLMS
    2. Confirm that GravityView is active
    3. Click activate LifterLMS, the fatal error occurs and LifterLMS is not activated
    4. Disable GravityView, click activate LifterLMS and it activates successfully
    5. Reactivate GravityView

    [05-Sep-2024 00:54:55 UTC] PHP Fatal error: Uncaught Error: Class “LLMS_Integration_GravityView” not found in ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/class.llms.integrations.php:81 Stack trace: #0 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/class.llms.integrations.php(41): LLMS_Integrations->init()
    #1 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/traits/llms-trait-singleton.php(38): LLMS_Integrations->__construct()
    #2 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/class-lifterlms.php(525): LLMS_Integrations::instance()
    #3 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/admin/settings/class.llms.settings.integrations.php(129): LifterLMS->integrations()
    #4 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/admin/settings/class.llms.settings.integrations.php(61): LLMS_Settings_Integrations->get_table_html()
    #5 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/admin/settings/class.llms.settings.integrations.php(113): LLMS_Settings_Integrations->get_default_settings()
    #6 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/class.llms.install.php(225): LLMS_Settings_Integrations->get_settings(true)
    #7 ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/class.llms.install.php(571): LLMS_Install::create_options()
    #8 ../public_html/website_fd6f1ff7/wp-includes/class-wp-hook.php(324): LLMS_Install::install(false)
    #9 ../public_html/website_fd6f1ff7/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)
    #10 ../public_html/website_fd6f1ff7/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #11 ../public_html/website_fd6f1ff7/wp-admin/includes/plugin.php(703): do_action(‘activate_lifter…’, false)
    #12 ../public_html/website_fd6f1ff7/wp-admin/plugins.php(60): activate_plugin(‘lifterlms/lifte…’, ‘example.com’, false)
    #13 {main} thrown in ../public_html/website_fd6f1ff7/wp-content/plugins/lifterlms/includes/class.llms.integrations.php on line 81

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Alexander

    (@alextonio22)

    Hi @dmed ,

    Thank you for the detailed information. It looks like there’s a conflict between LifterLMS and the GravityView plugin, resulting in the fatal error you encountered. This issue seems to stem from the LLMS_Integration_GravityView class not being found when both plugins are active.

    To address this, I recommend the following steps:

    1. Ensure that both LifterLMS and GravityView are updated to their latest versions, as compatibility improvements are often included in updates.
    2. Since the issue is reproducible, it may be helpful to report this directly to GravityKit with the specifics of your setup and the error message. They may need to investigate further or provide a patch.
    3. Conflict Testing: If possible, try deactivating other plugins to see if the issue persists with only LifterLMS and GravityView active. This can help identify if there’s an interaction with another plugin causing the conflict.

    If the problem continues after these steps, please let us know, and we can explore further solutions.

    All the best,

    Thread Starter DManIT

    (@dmed)

    Hi @alextonio22,

    Thanks for the reply! Both plugins were updated. I did report this to GravityKit and their response was:

    “Regarding that fatal error with LifterLMS, it’s a code issue on their plugin. Please share this with them (LifterLMS):”

    ..followed by the stack trace I provided in my first message.

    GravityKit stated this is an issue with LifterLMS and it appears the issue in the stack trace is in the lifterlms/includes/class.llms.integrations.php file. Is this incorrect?

    • This reply was modified 3 weeks, 2 days ago by DManIT.

    @dmed, could you please try the latest GravityView build and let me know if it fixes the issue?

    • This reply was modified 3 weeks, 2 days ago by mrcasual.

    @dmed, sorry, I meant to share this build.

    mrcasual

    (@mrcasual)

    To follow up, we’ve just released GravityView 2.31, which fixes the fatal error.

    @alextonio22, it was indeed our issue. That said, I noticed in your code that integration classes are instantiated without checking if they exist. Perhaps adding a class_exists() check before instantiation could help prevent similar issues in the future. Cheers!

    Plugin Support Alexander

    (@alextonio22)

    Hi @mrcasual ,

    Thank you for confirming the fix in GravityView 2.31 and for your transparency. I appreciate the suggestion regarding the class_exists() check before instantiation in our integration classes. We’ll review this in our codebase and implement it where needed to help prevent similar conflicts.

    Thanks again for the collaboration.

    All the best,

    Plugin Support Alexander

    (@alextonio22)

    Hi @dmed ,

    Could you confirm if updating to the latest GravityView 2.31 resolved the issue on your end? Please let us know so we can mark this as resolved or assist you further if needed.

    All the best,

    Plugin Support Nick Mariano

    (@reddotinmotion)

    Hi @mrcasual and @mrcasual,

    Could you please let us know if the issue is resolved? As we haven’t had any response in over a week, I am going to mark this thread as resolved. Please reopen or post a new thread if you require further assistance.

    @reddotinmotion, I believe you’re looking for a response from @dmed, not me.

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