Conflict with gravity smtp

—

by

Mike Bavistock

When Gravity SMTP and Groups File Access v2.7.0 are installed, Groups File Access links https://domain.tld/?gfid=1 returns a 500 error.

When Gravity SMTP is deactivated, Groups File Access urls work fine.

Tested by deactivating all plugins except:
Gravity Forms
Gravity SMTP
Groups
Groups File Access

Posted in
Tags

Comments

3 responses to “Conflict with gravity smtp”

  1. George Avatar
    George

    Hey Mike,

    Thanks for sharing the error you get. If you look at the trace, when GFA tries to send a notification email, then Gravity SMTP gives an error.
    Have you reached out to Gravity SMTP for this case? The error relates to a function that I have no access at the moment.

    Kind regards,
    George

  2. Mike Bavistock Avatar
    Mike Bavistock

    Thanks George, here is debug.log:

    [25-Feb-2025 11:37:12 UTC] PHP Fatal error: Uncaught Error: Call to a member function mail() on null in /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-content/plugins/gravitysmtp/includes/functions_include.php:19
    Stack trace:
    #0 /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-content/plugins/groups-file-access/lib/core/class-groups-file-access.php(862): wp_mail(‘mike@tandem.net…’, ‘File accessed a…’, ‘The file /home3…’, ‘MIME-Version: 1…’)
    #1 /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-content/plugins/groups-file-access/lib/core/class-groups-file-access.php(922): Groups_File_Access::mail(‘mike@tandem.net…’, ‘File accessed a…’, ‘The file /home3…’, Array)
    #2 /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-includes/class-wp-hook.php(324): Groups_File_Access::groups_file_served(2, 1)
    #3 /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array)
    #4 /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #5 /hom in /home3/hvsgsa/domains/hvsgsa.org.au/public_html/w/wp-content/plugins/gravitysmtp/includes/functions_include.php on line 19

  3. George Avatar
    George

    Hey Mike,

    Thanks for mentioning that issue with us.
    I’m wondering if you have checked the contents of your debug.log for additional pointers, when the error occurs. The debug.log file is generated if WP Debugging is enabled with the following options

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );

    and can be found by default in wp-content/debug.log.

    Kind regards,
    George

Only authorized members can comment on this topic.

Log in

Share