Skip to:
Content
Pages
Categories
Search
Top
Bottom

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


  • jimgroom
    Participant

    @jimgroom

    15 years, 3 months ago

    I have upgraded to WPMu 2.8.1 and also upgraded to BP 1.0.3, and when I activate BP 1.0.3 I get the following error:

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

    More than that, when it is activated, seems like it is doing strange things to the ajax in the backend. Anyone run into something similar? I have a pretty crazy setup with mapped domain, mapped sites, etc. And I wonder if this is just an oddity I have to contend with and find a fix for, or if someone else out there is experiencing something similar.

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

  • Mariusooms
    Participant

    @mariusooms

    15 years, 3 months ago

    I noticed this as well when using the “Site Wide activation link” at the bottom right of each plugin. Instead try activating like you usually would by just clicking the activate link. It will just activate Site Wide without error. This worked for me…

    You ajax back end issues could well be other related and not related to the activation issue.


    jimgroom
    Participant

    @jimgroom

    15 years, 3 months ago

    Mariusooms,

    Thank you, the activate link fixed the fatal error notice, but the ajax issues remain. Hmmm, wonder what it is colliding with.


    Mariusooms
    Participant

    @mariusooms

    15 years, 3 months ago

    I would close this topic as the title indicate it is solved now and open a new ticket to get help specifically for that issue ;)

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

Topic Info

Topic Tags

Skip to toolbar