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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Bizstudio

    (@ajamm)

    Just read this… not an actual issue with this plugin… just a shortcode clash. Shame… my design needs both functions…

    Plugin Author Jeff Lambert

    (@lambje)

    Not certain why I never deprecated my use of that function name. If you open a ticket on my WEBphysiology.com site, I’ll let you know when I have a fix. Might be as soon as a week from now.

    Out of curiosity, what other plugin has this function?

    Thread Starter Bizstudio

    (@ajamm)

    wp-user-frontend

    Plugin Author Jeff Lambert

    (@lambje)

    Looks like that plugin is having other issues according to the broken/not broken buttons. Anyhoo, I’ve made this change and you may either download it now, https://s3.amazonaws.com/webphysiology_portfolio/webphysiology-portfolio-1.4.7.zip, or I should be pushing out a “legit and tested” version in a day or two.

    Thread Starter Bizstudio

    (@ajamm)

    Yeah, I am working thru that one currently. Bit of a mess to be honest. But the only plugin with that functionality. I may need to reassess the required functionality, as I don’t want to be dependent on an unreliable plugin. From what I have found, I wonder if the developer has simply made some mess of an update. There are several bits just missing.

    Thankyou for your help.

    Plugin Author Jeff Lambert

    (@lambje)

    The function was renamed in v1.4.7 and this should no longer be an issue for you.

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