WordPress.org

Support

Support » Plugins and Hacks » P2 Resolved Posts » [Resolved] Plugin could not be activated because it triggered a fatal error.

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Daniel Bachhuber

    @danielbachhuber

    Hand Built

    It sounds like the file might be corrupted. Can you try downloading and reinstalling the entire plugin?

    Ya, I tried a few times. Both via wp-admin and wp-cli. Same result.

    [vmg@SWITCHWP wordpress]> wp plugin install p2-resolved-posts --activate
    Installing P2 Resolved Posts (0.3)
    Downloading install package from http://downloads.wordpress.org/plugin/p2-resolved-posts.0.3.zip...
    Unpacking the package...
    Installing the plugin...
    Plugin installed successfully.
    Activating 'p2-resolved-posts'...
    PHP Parse error:  syntax error, unexpected $end in ...wordpress/wp-content/plugins/p2-resolved-posts/p2-resolved-posts.php on line 754

    Is there a hash of the zip file?

    Plugin Author Daniel Bachhuber

    @danielbachhuber

    Hand Built

    Can you try manually downloading?

    Same result. Oddly, attempting to activate the plugin using wp-cli didn’t produce any errors even though it failed to activate. When I used wp-admin the same error was printed at the top of the plugins screen.

    On a single blog all versions of the plugin activate fine for me.

    But on multisite, I get the same error with .2, .3 and dev versions.

    Parse error: syntax error, unexpected $end in p2-resolved-posts.php on line 754

    Plugin Author Daniel Bachhuber

    @danielbachhuber

    Hand Built

    Crazy talk. There’s only 751 lines in p2-resolved-posts.php

    Joe, want to ping me on Skype when you have a moment so we can track this down?

    dkukral

    @dkukral

    Issue was the server had short_tags turned off ..

    lines 521 and 591 of p2-resolved-posts.php use the short php open tag <? instead of the long tag <?php

    You should probably use <?php for better portability.

    Plugin Author Daniel Bachhuber

    @danielbachhuber

    Hand Built

    Aha! Thanks for tracking it down, dkukral. I’ll have a fix for it shortly.

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