• Resolved ziegel

    (@ziegel)


    Hi,

    I got emails stuck in queue.

    Running cron from server where PHP ver 8.2.4 is installed, I got the error notification:

    PHP Fatal error: Uncaught TypeError: DeliciousBrains\WP_Offload_SES\Carbon\Carbon::setLastErrors(): Argument #1 ($lastErrors) must be of type array, bool given, called in /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/vendor/Carbon/Carbon.php on line 487 and defined in /var/www/vhosts/example.com/staging.example.com/wp-content/plugins/wp-ses/vendor/Carbon/Carbon.php:800
    Stack trace:
    
    0 /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/vendor/Carbon/Carbon.php(487): DeliciousBrains\WP_Offload_SES\Carbon\Carbon::setLastErrors()
    
    1 /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/vendor/WP-Queue/Connections/DatabaseConnection.php(166): DeliciousBrains\WP_Offload_SES\Carbon\Carbon->__construct()
    
    2 /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/classes/Queue/Connection.php(160): DeliciousBrains\WP_Offload_SES\WP_Queue\Connections\DatabaseConnection->vitalize_job()
    
    3 /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/classes/Queue/Worker.php(56): DeliciousBrains\WP_Offload_SES\Queue\Connection->pop()
    
    4 /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/classes/Queue/Email-Cron.php(60): DeliciousBrains\WP_Offload_SES\Queue\Worker->process()
    
    5 /var/www/vhosts/example.com/httpdocs/wp-includes/class-wp-hook.php(308): DeliciousBrains\WP_Offload_SES\Queue\Email_Cron->cron_worker()
    
    6 /var/www/vhosts/example.com/httpdocs/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
    
    7 /var/www/vhosts/example.com/httpdocs/wp-includes/plugin.php(565): WP_Hook->do_action()
    
    8 /var/www/vhosts/example.com/httpdocs/wp-cron.php(188): do_action_ref_array()
    
    9 {main}
    
    thrown in /var/www/vhosts/example.com/httpdocs/wp-content/plugins/wp-ses/vendor/Carbon/Carbon.php on line 800

    Possible Bug:

    The error is seemed to be caused by 2 different, incompatible versions of the same PHP library (in this case PHP Carbon) by 2 plugins. In this case, the other plugin is using a drop-in replace for Carbon, https://github.com/cakephp/chronos which doesn’t appear to support Carbon v2 (which we’re using)

    DIAGNOSTIC INFO is:

    site_url(): https://example.com
    home_url(): https://example.com
    Web Server: Apache
    WordPress: 6.2
    WP Locale: en_US
    PHP: 8.2.4
    PHP Memory Limit: 512M
    WP Memory Limit: 256M
    Memory Usage: 14 MB
    WP Max Upload Size: 3 MB
    PHP Time Limit: 3600
    PHP Error Log: /var/www/vhosts/example.com/logs/PHP_errors.log
    MySQL: 8.0.32
    Database Name: admin_example
    Table Prefix: rOIz1f_
    ext/mysqli: yes
    cURL: 7.81.0
    OpenSSL: OpenSSL 3.0.2 15 Mar 2022
    fsockopen: Enabled
    allow_url_fopen: Enabled
    Zlib Compression: Enabled
    Basic Auth: Disabled
    Proxy: Disabled
    Blocked External HTTP Requests: None Send Mail Using SES: On
    Enable Open Tracking: Off
    Enable Click Tracking: Off
    Region: us-east-1
    Log Duration: 180 WP Cron: Disabled
    Alternate WP Cron: Disabled
    Last Run: 22:56:10 2023-04-17 UTC
    Next Scheduled: 23:02:02 2023-04-17 UTC
    Queued: 2
    Failures: 0 WPOSES_SETTINGS: Not defined
    WPOSES_LICENCE: Not defined
    AWS_USE_EC2_IAM_ROLE: Not defined WP_DEBUG: No
    WP_DEBUG_LOG: No
    WP_DEBUG_DISPLAY: No
    SCRIPT_DEBUG: No
    WP_CONTENT_DIR: /var/www/vhosts/example.com/httpdocs/wp-content
    WP_CONTENT_URL: https://example.com/wp-content
    UPLOADS: Not defined
    WP_PLUGIN_DIR: /var/www/vhosts/example.com/httpdocs/wp-content/plugins
    WP_PLUGIN_URL: https://example.com/wp-content/plugins Active Theme Name: Currenge Theme
    Active Theme Version: 1.0.0
    Active Theme Folder: example Active Plugins:
    ACF Content Analysis for Yoast SEO (v3.0.1) by Thomas Kr?ftner, ViktorFroberg, marol87, pekz0r, angrycreative, Team Yoast
    Advanced Custom Fields (v6.1.4) by WP Engine
    Advanced Custom Fields Multilingual (v1.8.1) by OnTheGoSystems
    Advanced Custom Fields PRO (v6.1.4) by WP Engine
    Advanced Custom Fields: ACF Code Field (v1.8) by Peter Tasker
    CAPTCHA 4WP (v7.1.0) by WP White Security
    Classic Editor + (v4.2.0) by Pieter Bos, Greg Schoppe
    Classic Widgets (v0.3) by WordPress Contributors
    Conditional Fields for Contact Form 7 (v2.3.7) by Jules Colle
    Contact Form 7 (v5.5.3) by Takayuki Miyoshi
    Contact Form 7 Signature Addon (v4.2.2) by Breizhtorm
    Contact Form CFDB7 (v1.2.6.5) by Arshid
    GDPR Cookie Compliance (v4.10.6) by Moove Agency
    Listo (v1.3) by Takayuki Miyoshi
    NinjaFirewall (WP Edition) (v4.5.7) by The Ninja Technologies Network
    Redirect 404 Error Page to Homepage or Custom Page (v1.7.9) by Fullworks
    SVG Support (v2.5.5) by Benbodhi
    Simple Custom Post Order (v2.5.6) by Colorlib
    Toolset Module Manager (v1.8.6) by OnTheGoSystems
    Toolset Types (v3.4.19) by OnTheGoSystems
    Toolset Views Lite (v2.9.4-lite) by OnTheGoSystems
    Video Background (v2.7.5) by Push Labs
    WP Crontrol (v1.15.1) by John Blackbourn & crontributors
    WP Last Login (v5) by Konstantin Obenland
    WP Offload SES Lite (v1.6.3) by Delicious Brains
    WPBakery Page Builder (v6.10.0) by Michael M - WPBakery.com
    WPML CMS Nav (v1.5.5) by OnTheGoSystems
    WPML Media (v2.7.2) by OnTheGoSystems
    WPML Multilingual CMS (v4.6.3) by OnTheGoSystems
    WPML SEO (v2.1.0) by OnTheGoSystems
    WPML Sticky Links (v1.5.4) by OnTheGoSystems
    Yoast Duplicate Post (v4.5) by Enrico Battocchi & Team Yoast
    Yoast SEO (v20.5) by Team Yoast
    miniOrange 2 Factor Authentication (v5.7.0) by miniOrange
    plugin load filter (v4.0.13) by enomoto@celtislab Must-use Plugins:
    0-ninjafirewall.phpplugin load filter plf-filter by enomoto@celtislab Drop-ins:
    maintenance.php - maintenance.php

    Issue seems to be, as resulting from the above possible bug.

    Can you please assist?

    • This topic was modified 1 year, 7 months ago by ziegel.
Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter ziegel

    (@ziegel)

    Hi @tikguy ,

    Thanks

    May I ask to confirm, you have tested it, and the error situation has its “if routing” as it had previously, or it would now fall between the chairs?

    Thread Starter ziegel

    (@ziegel)

    Hi @deliciousbrains,

    Thanks for the advise regarding rolling back to an older plugin version. Although it did solve most problems, I still once in a day or two get an alert email saying the plugins cron fails.

    For functionality, I have set a serer level cron task to activate the wp-cron.php file once in 10 minutes, which add hock temporary solves the emails being queued, however this problem is still there. I suspect the rolling back didn’t fully solve the issue.

    May I ask if you can think of three:

    1. Solving root cause for the errors, which I’m still not aware of.
    2. coding the IF for the different data structure the error function may have as output according to errors existance or absence.
    3. A walk-around solution, which will enable a specific call for the server level ‘cron’ (event management? other?) that release the sending of queued emails, possibly according to identifying existence of an error reported, or by the status of emails being pended to queued.

    The cron error message received looks like this:

    Email Subject line:
    
    WP Offload SES - Cron not running
    
    Test:
    
    Hi,
    
    You're receiving this email because WP Cron doesn't appear to be running on example.com.
    
    Please see our cron setup doc for more details.

    BTW

    It’s kind of “funny” the alert email (and plugin test email as well) can be sent, however the queued emails cant.

    Which leads to the thought, of possibly you enabling SERVER to directly also send emails, on some circumstances, and not only the SES configuration service.

    • This reply was modified 1 year, 7 months ago by ziegel.
    • This reply was modified 1 year, 7 months ago by ziegel.
Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Plugin Possible Bug – Using Old PHP Carbon, clash with newer on another plugin?’ is closed to new replies.