Support » Plugin: Beans Visual Hook Guide » Plugin could not be activated because it triggered a fatal error.

  • Resolved hazephase

    (@hazephase)


    I have a child theme and every time I try to activate the plugin, I get this error

    Parse error: syntax error, unexpected ‘function’ (T_FUNCTION), expecting identifier (T_STRING) or \\ (T_NS_SEPARATOR) in /home2/plustlb1/public_html/thewaterconnection.in/wp-content/plugins/beans-visual-hook-guide/src/markup/handler.php on line 14

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jeff Cleverley

    (@deftly)

    Hi Elroy,

    I have also messaged you in the slack channel.

    I think you might have come across the same situation as Paal, he raised the this Parse error on the plugin’s github here:

    https://github.com/JeffCleverley/Beans-Visual-Hook-Guide/issues/7

    The issue with Paal was he was developing locally on Desktop Server using PHP5.5.4, but the minimum PHP version for this plugin is 5.6 as it is using namespacing amongst other things.

    Could you confirm that you are using PHP5.6+ please?

    Thanks

    Jeff

    Plugin Author Jeff Cleverley

    (@deftly)

    Hi Elroy,

    I still didn’t get a reply here or the slack channel. But after testing myself this problem appears when you try to run the plugin using the incorrect PHP version.

    Since I didn’t hear back from you I am going to close this ticket and mark it as resolved.

    If it turns out that this persists on the correct PHP version, please open another ticket, reach out to me in the Beans Slack Channel, or alternatively post an issue on the Github page:
    https://github.com/JeffCleverley/Beans-Visual-Hook-Guide/issues/

    Have a nice day.

    Jeff

    Hi Jeff,

    Sorry for not replying, I think you are right. Thanks for your reply.

    • This reply was modified 2 years, 2 months ago by hazephase.
    Plugin Author Jeff Cleverley

    (@deftly)

    Hey Elroy,

    You’re welcome.

    Jeff

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