Debugging a Plugin under 2.2

  • tomtvotw

    (@tomtvotw)


    16 years, 10 months ago

    I’m a “first time” plugin developer – although with limited php development skills, and I’m having a problem.

    When I try to activate my new plugin, I get a “Plugin could not be activated because it triggered a fatal error.” message.

    Unfortunately this doesn’t tell me what the fatal error actually was. Is there any way to get the actual error message?

Viewing 2 replies - 1 through 2 (of 2 total)
  • tmuka

    (@tmuka)

    16 years, 8 months ago

    is there an official technique for debugging these plugin error messages? are they logged somewhere behind the scenes?

    buzink

    (@buzink)

    16 years, 8 months ago

    yes, this very usefull new feature for users in 2.2, is a big problem for developpers.

    maybe the specific php error message could be hidden in the html-source? In that way users won’t see it and the more adventurous plugin developers will find it.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Debugging a Plugin under 2.2’ is closed to new replies.