Latest Slip Stream update causing Fatal PHP error

  • Hi folks, running wordpress 6.6.2 – and the latest Slickstream update brought down my website.

    I had to get support to deactivate the plugin – as it prevented the WPADMIN page starting. 

    Message
    PHP Fatal error:  Uncaught Error: Class "SlickEngagement_Plugin" not found in /srv/htdocs/wp-content/plugins/slick-engagement/slick-engagement_init.php:6
    Stack trace:
    #0 /srv/htdocs/wp-content/plugins/slick-engagement/slick-engagement.php(65): SlickEngagement_init('/srv/htdocs/wp-...')
    #1 /wordpress/core/6.6.2/wp-settings.php(522): include_once('/srv/htdocs/wp-...')
    #2 /srv/htdocs/wp-config.php(81): require_once('/wordpress/core...')
    #3 /wordpress/core/6.6.2/wp-load.php(55): require_once('/srv/htdocs/wp-...')
    #4 /wordpress/core/6.6.2/xmlrpc.php(31): require_once('/wordpress/core...')
    #5 {main}
      thrown in /srv/htdocs/wp-content/plugins/slick-engagement/slick-engagement_init.php on line 6
    Timestamp
    2024-11-12T09:25:00.000Z
    Kind
    plugins
    Name
    slick-engagement
    File
    /srv/htdocs/wp-content/plugins/slick-engagement/slick-engagement_init.php
    Line
    6

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)

  • Just a data point, I quickly updated to 2.0.1. without doing much testing because of the security warning Jetpack gave. But I have it running on 6.6.1 and 6.6.2 (staging) and don’t see this issue in the admin or the frontend. With 6.6.2 I poked around with query monitor and don’t even get warnings. I see they’ve updated to 2.0.2 wonder if that addresses your issue (and related, the change log is still at 1.2.5)

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