callerpatty

We deactivated the plugin on all our client sites and moved on to another plugin. I ran updates on one site that was using your plugin, reactivated the plugin and it would appear that the error is gone.

Still no resolution for this? Is anyone from the plugin monitoring this forum?

Is anyone monitoring this forum for support? Any resolution or information on this issue that seems to be pervasive as I see lots of the same support requests?

@billiardgreg They told me to start my own ticket so I did … but exact same issue. Plugin developers seem to be unresponsive, so fingers crossed.

Ok! I’ll move on to the popup builder folks!

As a follow up. I did some testing of plugin updates to see if I could find what was going south. If I keep PostSMTP version 2.9.2 and do not update it, the declaration notice appears after updating the Popup Builder plugin from version 4.3.0 to version 4.3.2 – by Looking Forward Software

If I keep the Popup Builder plugin on version 4.3.0 and update the Post SMTP plugin to version 2.9.2, the declaration notice does not appear, so it seems that you have a conflict with the popup plugin when updated.

@highburycorp – are you running that popup plugin?

Here is the PostSMTP diagnostic test results – please note we have NOT updated the PostSMTP to the current version yet. We cannot do that until the issues are corrected. I have no error emails right now in our email log queue.

Mailer: postsmtp
HostName: biomerestoration.com
cURL Version: 8.7.1
OpenSSL Version: OpenSSL/1.1.1w
OS: Linux host.biomerestoration.com 3.10.0-1160.53.1.vz7.185.3 #1 SMP Thu Dec 15 20:31:06 MSK 2022 x86_64
PHP: Linux 7.4.33 C
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=No, allow_url_fopen=No, mcrypt=No, zlib_encode=Yes
WordPress: 6.5.3 en_GB UTF-8
WordPress Theme: Biome Theme
WordPress Plugins: Advanced Custom Fields PRO, Better Font Awesome, Classic Editor, Classic Widgets, Honeypot for Contact Form 7, Contact Form 7, Contact Form CFDB7, Cookie Notice & Compliance for GDPR / CCPA, Health Check & Troubleshooting, Livemesh SiteOrigin Widgets, Plugins List, Popup Builder, Post SMTP, Really Simple Twitter Feed Widget, Text Blocks, Page Builder by SiteOrigin, SiteOrigin Widgets Bundle, UpdraftPlus – Backup/Restore, User Switching, Orders Tracking for WooCommerce, WooCommerce Print Address Labels, WooCommerce Checkout Field Editor, WooCommerce Stripe Gateway, WooCommerce Legacy REST API, PDF Invoices & Packing Slips for WooCommerce, WooCommerce Sequential Order Numbers Pro, Woo Subscriptions, WooCommerce, Wordfence Security, Yoast SEO, WP All Export Pro, WP All Export – WooCommerce Export Add-On Pro, WP Overnight Sidekick
WordPress wp_mail Owner: /home/biomerestor/public_html/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, WPO\WC\PDF_Invoices\Main->set_phpmailer_validator, PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): wpcf7_phpmailer_init, PostsmtpMailer->phpmailer_smtp_init
Postman: 2.9.2
Postman Sender Domain (Envelope|Message): biomerestoration.com | biomerestoration.com
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Active Transport: Other SMTP (smtps:login://biomerestoration.com:465)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 15093 | 59

I understand that I am changing the core files and they will be overwritten when we update the plugin, but do you have any intention of updating your plugin so the filter works if someone does NOT have featured images?

This would be a very thoughtful function for you to implement for users with no featured images.

Taking out that code fixes the issue. Filtering now works as expected.

Will you be making adjustments or will we need to make this change every time the plugin updates?

So the only way that your filter works is if all posts have featured images? That seems to be a bit quirky, and there is nothing in any documentation stating that.

Is there anything that can be done so that the filter works if some posts do NOT have images? Not all posts will have featured images.

I will reach out to support. I have already verified that the file that the code is looking for is NOT on the server, so somewhere in your codebase this is still being called.

I was going to submit this same issue, but I’ll add our information! We also ran a PHP 8.2 compatibility scan, and the following are examples of what came up as errors. The scan reported errors in around 50 files. Interestingly, they didn’t show up in the validation the other day before we updated Post SMTP to the latest version. Our client is very concerned about updating their PHP version with all these errors.

/plugins/post-smtp/Postman/Postman-Mail/Zend-1.12.10/Validate/Between.php.
Since PHP 7.0, functions inspecting arguments, like func_get_args(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter “$options” was changed on line 102.

/plugins/post-smtp/Postman/Postman-Mail/Zend-1.12.10/Validate/CreditCard.php.
Since PHP 7.0, functions inspecting arguments, like func_get_args(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter “$options” was changed on line 144.

/post-smtp/Postman/Postman-Mail/Zend-1.12.10/Validate/EmailAddress.php.
Since PHP 7.0, functions inspecting arguments, like func_get_args(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter “$options” was changed on line 140.

post-smtp/Postman/Postman-Mail/Zend-1.12.10/Validate/InArray.php.
Since PHP 7.0, functions inspecting arguments, like func_get_arg(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter “$options” was changed on line 74.
Since PHP 7.0, functions inspecting arguments, like func_get_arg(), no longer report the original value as passed to a parameter, but will instead provide the current value. The parameter “$options” was changed on line 74.

/post-smtp/Postman/Postman-Mail/libs/vendor_prefixed/phpseclib/phpseclib/phpseclib/Crypt/Common/SymmetricKey.php.
Extension ‘mcrypt’ is deprecated since PHP 7.1 and removed since PHP 7.2; Use openssl (preferred) or pecl/mcrypt once available instead

We are still getting these also, but they are also coming from sites that are not running Post SMTP – not sure how they are getting in and generating these!

Thank you for your reply.

That isn’t what we see: https://app.screencast.com/xEH0Ph9HnnmTY

And in the general options, there isn’t anything there either: https://app.screencast.com/Hj3d03en0WcYQ

I have uninstalled the plugin completely and reinstalled it and still don’t see any UTC.

As an addition: I just tried to at least change the time to be 11/17 20:00,,, saving it changed the expiration time to be 11/18 01:00 – something is wacked out and interfering with the save?