Plugin failed

  • Resolved jackkharding

    (@jackkharding)


    7 years, 1 month ago

    Hi there.

    I’ve had a problem where the plugin has failed and de-activated itself twice. When I log back in to the CMS I’m shown an alert with a message like ‘WP Sermon Manager has failed’. It shows where the error happened and the stack trace.

    The first time it pointed to the use of wpfc_sermon_meta() in one of my theme files. I believe it said the function was undefined, or something like that.

    The second time it failed, it pointed to a line in one of the files in another plugin – Download Manager. I can’t quite remember the error though, sorry.

    Is this a known issue or do you know what might be the cause of this? I’ve used this plugin for nearly a year, with no issues until recently.

    Any help would be greatly appreciated!

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

  • Hey @jackkharding,

    The bug has been fixed in 2.8, it won’t deactivate itself anymore unless it creates an error (rare chance). ??

    If wpfc_sermon_meta() error shows up again, it would be great if you contact us or click the blue button “Send Anonymous report”, but please include at least the email address so we can contact you ??

    Thank you for your patience

    Getting one with the latest version deactivation

    require_once(): Failed opening required ‘~/wp-content/plugins/jetpack/sync/class.jetpack-sync-sender.php’ (include_path=’.:/usr/php/56/usr/lib64:/usr/php/56/usr/share/pear’)

    I am having success after getting the error message. I deactivated Jetpack, then activated Sermon Manager. Then Reactivated Jetpack. So far so good. Granted it’s only been a few minutes. (SM wouldn’t reactivate at all. It would give a successful activation then not show up in the dashboard.)

    • This reply was modified 7 years, 1 month ago by themps.

    Hey, it is definitely fixed in 2.8.2.

    We removed error catching since it’s causing too much issues.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin failed’ is closed to new replies.