Support » Plugin: AdRotate Banner Manager - The only ad manager you'll need » Plugin could not be activated because it triggered a fatal error.

  • Resolved taniav

    (@taniav)


    Hi Arnan,

    I just want to let you know the problem I run into when using your plugin.

    I installed this plugin on my development site on XAMPP. Testing it a bit, everything seems okay. Then, I tried to install it on my live site. And… I can’t activate it on my live site. I got this message:

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

    Fatal error: Call to a member function add_cap() on a non-object in /home/mysite/public_html/wp-content/plugins/adrotate/adrotate-setup.php on line 35

    Do you know what’s happening?

    http://wordpress.org/plugins/adrotate/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Arnan de Gans

    (@adegans)

    Which version of AdRotate do you use?
    There was an issue with this a few months ago, but that has been fixed many versions ago…

    Thread Starter taniav

    (@taniav)

    I was using AdRotate version 3.8.9

    Edit: Downloaded it from WordPress repository on 22 Nov 2013, by the way.

    Plugin Author Arnan de Gans

    (@adegans)

    I have no idea, I can’t reproduce it anywhere 🙁
    It may be related to your WordPress setup. But I’m not sure.

    Thread Starter taniav

    (@taniav)

    I don’t think it’s related to my WP setup because I have exactly the same setup on my localhost (XAMPP) and this plugin works well, but not work on my live site.

    I don’t know, maybe it’s my shared hosting.. But it runs on Apache, PHP5.2.17 (this plugin’s minimun is PHP5.2).

    Plugin Author Arnan de Gans

    (@adegans)

    Sounds like a server issue of some kind, although the error suggests otherwise.
    Perhaps something with your wordpress setup.

    I can’t find useful info on it, and still am not able to reproduce the issue on any of my servers – Including Xampp/Mamp.

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