Plugin could not be activated because it triggered a fatal error.

  • Resolved Jeasy

    (@jeasysehgal)


    7 years, 11 months ago

    Caused a total downtime of 8 hours and had to go through a Multisite Network system to identify it was your plugin that caused the issue.

    Plugin could not be activated because it triggered a fatal error.

    Please fix. Really like your plugin and would be a shame to have to stop using it.

    Cheers, Jeasy

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.