horst

Deprecation warnings say, that it potentially may not be ready for 8.4.2 or 8.4.3 or any other further version. But in my understanding, it is ready for PHP 8.4.0 and 8.4.1. 🙂 If the deprecation warnings bother you, you can disable showing only those messages with a call of PHPs set_error_handler(): /** OWN ERROR HANDLER FOR DEPRECATION NOTES ************************************/ function myLocalDevDeprecationErrorHandler($errno, $errstr, $errfile, $errline) { return true; // true | false = suppress further processing } // preceed the callback function name with the PW namespace, // and define the error types that should passed to the function set_error_handler('ProcessWire\myLocalDevDeprecationErrorHandler', E_DEPRECATED); /** OWN ERROR HANDLER FOR DEPRECATION NOTES ************************************/ I often use this directly in site/config-dev.php, when I want to collect them, but only show them collected at the end of pages in dev local. /** OWN ERROR HANDLER FOR DEPRECATION NOTES ************************************/ function myLocalDevDeprecationErrorHandler($errno, $errstr, $errfile, $errline) { // CHECK / CREATE COLLECTION CONTAINER if (!isset($GLOBALS['DEPRECATION_WARNINGS_BAG'])) { $GLOBALS['DEPRECATION_WARNINGS_BAG'] = []; } if (!is_array($GLOBALS['DEPRECATION_WARNINGS_BAG'])) { $GLOBALS['DEPRECATION_WARNINGS_BAG'] = []; } // DO NOT SHOW THIS KNOWN THIRD PARTY ONES : $hideThisOnes = [ //'FileCompiler', 'Duplicator', 'ProcessCustomUploadNames', ]; foreach($hideThisOnes as $item) { if (preg_match("/{$item}/", $errfile)) return true; } // ADD IT TO THE COLLECTION $GLOBALS['DEPRECATION_WARNINGS_BAG'][] = [$errfile, $errline, $errstr]; return true; // true | false = suppress further processing } // preceed the callback function name with the PW namespace, // and define the error types that should passed to the function set_error_handler('ProcessWire\myLocalDevDeprecationErrorHandler', E_DEPRECATED); /** OWN ERROR HANDLER FOR DEPRECATION NOTES ************************************/

I had to fix the detection with 'is_resource()' into a combination with 'is_object()', to validate if an image load into memory with GD was successful. And just 15 minutes after I pushed my fixes to github, I thought: lets go into PWs online module section and update it too, - but it already was auto-updated! 🤩

Hi @Ivan Gretsky I have pushed a new branch into Github here: https://github.com/horst-n/WireMailSmtp/tree/php-namespace This is called version 0.8.0 and all PW-PHP-module-files are now added into the PHP namespace ProcessWire. So now the module only can be used with PW > 3.0.62 (after merging to master branch). All the backwards compatibility to starting PW version 2.4 is lost now. 🙂 Please, can you fetch the new version from the github dev branch and test it, if it helps with your errors and let me know? For me everything is working fine here. The normal sending, the DebugTests in Frontend and in Backend, etc. PHP 8.1 + 8.2 ...

Ok, I will try to find whats going wrong. And just for the record: I'm currently using it, also in PW 3.0.241 with PHP 8.2, without any errors. (?!?)

Hi, @Ivan Gretsky Which PW-Version? (And maybe you can find / remember the first PW version, it came up with?)

No! Just need a bit time for a short test. 🙂

Ok! 👍 That is something, I can test here without having WireMailRouter.

Hi, I don't have WireMailRouter and therefor don't know how it works together. But please can you (or @Ivan Gretsky or @wbmnfktr, who seems to have it too, like you) simply test the following OneLineChange in the WireMailSmtp-Testfunction? $mail = wireMail(); if ($mail->className != 'WireMailSmtp' && $mail->className != 'WireMailRouter) { .... It then will skip the abort. So, don't know if it then works like it should, but that's why I ask for the test. 🙂 Let me know if someone can do that, and if so, what was the result. Greetings! 🙋‍♂️

... what was it? ?? No, everything is good! ? PS: I do get support forum e-mails, (as a forum moderator), whereas 99% of the blocked messages are real spam. But today I've read this in the mail subject: "Jan Romero has posted a post in a topic requiring approval", what lets me have used the posts url-link to look at it! ?

In the first page of this thread are working examples: like:

Hey, I will try to test it with PW 3.0.220 + and make a PW 3.x namespace version of it, as I think, every PW 2.x installation that is using it, does not need more new WireMail-SMTP updates from now on. (As some or one of you suggested!) I try to do it this week! @ceberlin @Ivan Gretsky @zoeck ...

Sorry to be so unclear! But this "we" referred to the PW project! ? And yes, as @Jan Romero already said, it is only one in the wire directory, so that you can use your own in the site directories.

Maybe your editor is able to use / change configurations via .editorconfig? Then it would be easy to train it. ? (We use it in PW, like in many other projects too. https://editorconfig.org/)

Very nice! ?? (https://processwire.recipes/code-of-conduct/)