• Resolved boabo

    (@boabo)


    Hello,

    I wanted to test your plugin 1.1.7 on local first, but after install, wp dashboard sends this message “Plugin could not be activated because it triggered a fatal error.” In local, the SSL is set to “trusted” to bypass browser connection warnings. No https but it usually works with all plugins. Thank you

    WP 6.9.7

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

    (@cagriuckan)

    Hi,

    Thanks for the report — it’s not an SSL issue; activation doesn’t touch HTTPS.

    Could you check your PHP version? Tools → Site Health → Info → Server.

    If it’s 8.1.x, that’s the cause and it’s our mistake: 1.1.7 is labelled as
    requiring PHP 8.1, but a bundled library actually needs 8.2. Switching your
    local stack to PHP 8.2+ will let it activate right away, and we’ve corrected
    the requirement for the next release.

    If you’re already on 8.2+, add these to wp-config.php, retry the activation,
    and send us the last lines of wp-content/debug.log:

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Sorry for the trouble, and thanks for writing in.

    Best regards,
    PushAI Support

    Thread Starter boabo

    (@boabo)

    Hello,

    Find attached debug.log but i’m still getting the error message, even with php 8.3.23 and WP 7.0.4

    https://drive.google.com/file/d/1GKTsAONTMYcbp6dNW7vGTaRx3mYqsfiR/view?usp=sharing

    Hope it helps

    Plugin Author cagriuckan

    (@cagriuckan)

    Hi Charles,

    1.1.8 is out — the fix is live on wordpress.org. Updating (or installing

    fresh) should let it activate cleanly on your Local site with no changes

    needed on your end.

    Thanks again for the debug log; it made this a quick fix.

    Best regards,

    PushAI Support

    Thread Starter boabo

    (@boabo)

    Plugin activated. Thank you.

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

You must be logged in to reply to this topic.