I was working with this plugin and got a fatal error.

  • Resolved Gary Gordon

    (@garymgordon)


    2 years, 9 months ago

    I was working with this plugin and got a fatal error.

    I had simply highlighted a group of my other plugins (after installing and creating the MU plugin) and it immediately generated the error. So I had to delete the MU plugin which allowed me to get back in.

    But as soon as I recreate the MU plugin to test it again, I get the error again, immediately. So I can’t continue to work with the plugin.

    I had also tried deleting the plugin, and then reinstalling it, but I continue to get the error.

    I’m presuming it added something to the database that isn’t being removed when I delete the plugin.

    Do you know what information I can remove from the database to safely and completely uninstall this plugin from my website?

    I’d like to be able to try it again, but unless I can get past this point, I can’t since simply re-activating the plugin causes my site to fail.

    Good thing is, it only seems to fail on the backend. LOL

    Any advise?

    Gary

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author ioannup

    (@ioannup)

    Hey @garymgordon !
    We store only check_conflicts_settings option in wp_options table.
    Also, we store mu-check-conflicts.php file in /wp-content/mu-plugins/ folder – it’s the MU plugin.
    If it shows the fatal error again – please, share me the whole message of it here.
    Best regards.

    Thread Starter Gary Gordon

    (@garymgordon)

    Thank you so much for your quick reply. This is exactly what I needed to know.

    I’ll try the plugin again and see if the problem continues. But I’m suspecting that everything will be fine once I remove the option in the database. ?? If not, I’ll let you know.

    Cheers,
    Gary

    Thread Starter Gary Gordon

    (@garymgordon)

    FYI. I just added the plugin back into the website after deleting the option entry in the database, and that fixed the issue. Thanks. (Not sure why it gave the issue in the first place, but removing the option row in the database allowed me to try it again.) *smile*

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘I was working with this plugin and got a fatal error.’ is closed to new replies.