Plugin could not be activated because it triggered a fatal error

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Does it show you any error message after “fatal error”?

    Thread Starter algui91

    (@algui91)

    No.

    Thread Starter algui91

    (@algui91)

    Solved, it seems to be nginx and pagespeed module cache, after purging both caches, the plugin is now active.

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