Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Author Jason Hendriks

    (@jasonhendriks)

    Http Error 500 means the PHP process crashed. It’s not directly due to misconfiguration or a problem with the plugin, though they most certainly triggered the problem.

    I suggest looking in your web server log to see if there is any kind of error message. Also I would enable WordPress debug and see if you there are error messages in the WordPress log.

    Who is your web host?

    Thread Starter maciek772

    (@maciek772)

    Thanks for fast reply.

    Web host – nazwa.pl (if you mean the provider?)

    Debug installed. What can I send you?

    Thread Starter maciek772

    (@maciek772)

    Debug log – “No Log File Found” after sending test mail failed (default Debug settings)

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Did you enable WP_DEBUG_LOG in the Debug plugin? Is your WordPress deployed on a read-only file system?

    I’ve never heard of nazwa.pl. Their support team might be able to help you with server error 500’s.

    Thread Starter maciek772

    (@maciek772)

    Did you enable WP_DEBUG_LOG in the Debug plugin?

    Sorry for it, I’ve just enabled it. It didn’t change anything.

    Is your WordPress deployed on a read-only file system?

    I don’t really know. Should I change permissions of anything on my server?

    I’ve never heard of nazwa.pl. Their support team might be able to help you with server error 500’s.

    I don’t think so. I will paste here my debug log as soon as it starts working.

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    WordPress attempts to write the debug log to wp-content/debug.log. Obviously write access by the www user is required.

    But the web server error log should also be copied on the WordPress output.. in case you can’t get debug.log to work.

    Thread Starter maciek772

    (@maciek772)

    I created debug.log manually. Here it goes.

    [23-Jun-2015 18:09:59] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [23-Jun-2015 18:11:00] PHP Fatal error:  Wrong parameters for Exception([string $exception [, long $code ]]) in /home/thekick/ftp/profeina_new/wp-content/plugins/postman-smtp/Postman/Postman-Mail/PostmanMailEngine.php on line 237
    Plugin Author Jason Hendriks

    (@jasonhendriks)

    ok! nice going ??

    So looks like a Postman problem, at least in your particular environment. Would you please post the output of the Postman Diagnostic Test.

    Looks like Postman found a problem and tried to tell you about it, but your PHP environment does not like the way it is creating the Exception and halted with PHP Fatal Error.

    Assuming you have v1.6.22, that line of code is:

    $newException = new Exception ( $message, $e->getCode (), $e->getPrevious () );

    And according to the PHP Exception documentation, that is correct:

    public __construct ([ string $message = "" [, int $code = 0 [, Exception $previous = NULL ]]] )

    The only thing I can think of is you are running a PHP version earlier than PHP 5.1.0??

    Thread Starter maciek772

    (@maciek772)

    Diagnostic test output:

    OS: Linux thekick.nazwa.pl 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 i686
    HTTP User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.125 Safari/537.36
    Platform: PHP Linux 5.2.17 / WordPress 4.2.2 pl_PL
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes
    WordPress Plugins: Polylang, Debug, Polylang Theme Strings, Postman SMTP, Revive Old Post (Former Tweet Old Post), WP Product Review
    WordPress Theme: Zerif PRO
    Postman Version: 1.6.22
    Postman Sender Domain: profeina.pl
    Postman Transport URI|Force Email|Name: smtp:tls:plain://profeina.pl:465|No|No
    Postman Transport Status (Configured|Ready|Connected): Yes|Yes|Yes
    Postman Deliveries (Success|Fail): 0|0
    Postman Bind (Success|Fail|Path): Yes|No|/home/thekick/ftp/profeina_new/wp-content/plugins/postman-smtp/Postman/PostmanWpMailBinder.php
    Postman TCP Timeout (Connection|Read): 10|60
    Postman Email Log (Enabled|Limit|Transcript Size): Yes|10|128
    Postman Run Mode: production
    Postman PHP LogLevel: 40000
    Postman Stealth Mode: No
    Postman File Locking (Enabled|Temp Dir): Yes | /tmp

    How to check PHP version from WP?

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    It says your PHP version is 5.2.17 that’s so weird. Then why is your PHP saying the Exception constructor only takes two parameters when the current documentation says three?

    Would you please try changing that line of code, PostmanMailEngine.php, line 237 from:

    $newException = new Exception ( $message, $e->getCode (), $e->getPrevious () );

    to

    $newException = new Exception ( $message, $e->getCode () );

    And try your test again.

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    I’ve already patched the plugin, if you’d just like to download an official version and install it. https://downloads.www.ads-software.com/plugin/postman-smtp.zip

    Thread Starter maciek772

    (@maciek772)

    Done:

    [23-Jun-2015 18:48:46] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [23-Jun-2015 19:04:29] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [23-Jun-2015 19:06:14] PHP Parse error:  syntax error, unexpected T_PUBLIC in /home/thekick/ftp/profeina_new/wp-content/plugins/postman-smtp/Postman/Postman-Mail/PostmanMailEngine.php on line 237

    edit: I edited manually, before you told me to download. What should I do?

    Thread Starter maciek772

    (@maciek772)

    This is my actual code. Should I download an official version anyway?

    $message = $e->getMessage ();
    				if ($e->getCode () == 334) {
    					// replace the unusable Google message with a better one in the case of code 334
    					$message = sprintf ( __ ( 'Communication Error [334] - make sure the Sender Email belongs to the account which provided the OAuth 2.0 consent.', 'postman-smtp' ) );
    				}
    				// create a new exception
    				public __construct ([ string $message = "" [, int $code = 0 [, Exception $previous = NULL ]]] );
    				// throw the new exception after handling
    				throw $newException;

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    Yes, download the version I made. The edit you made is not correct.

    Thread Starter maciek772

    (@maciek772)

    Progress ??
    Status: Could not read from profeina.pl

    Diagnostic test:

    OS: Linux thekick.nazwa.pl 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 i686
    HTTP User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.125 Safari/537.36
    Platform: PHP Linux 5.2.17 / WordPress  4.2.2 pl_PL
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes
    WordPress Plugins: Polylang, Debug, Polylang Theme Strings, Postman SMTP, Revive Old Post (Former Tweet Old Post), WP Product Review
    WordPress Theme: Zerif PRO
    Postman Version: 1.6.23d
    Postman Sender Domain: profeina.pl
    Postman Transport URI|Force Email|Name: smtp:tls:plain://profeina.pl:465|No|No
    Postman Transport Status (Configured|Ready|Connected): Yes|Yes|Yes
    Postman Deliveries (Success|Fail): 0|0
    Postman Bind (Success|Fail|Path): Yes|No|/home/thekick/ftp/profeina_new/wp-content/plugins/postman-smtp/Postman/PostmanWpMailBinder.php
    Postman TCP Timeout (Connection|Read): 10|60
    Postman Email Log (Enabled|Limit|Transcript Size): Yes|10|128
    Postman Run Mode: production
    Postman PHP LogLevel: 40000
    Postman Stealth Mode: No
    Postman File Locking (Enabled|Temp Dir): Yes | /tmp

    Debug log:

    24-Jun-2015 07:38:49] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [24-Jun-2015 07:41:07] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [24-Jun-2015 07:42:14] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [24-Jun-2015 07:58:53] PHP Warning:  urldecode() expects parameter 1 to be string, array given in /home/thekick/ftp/profeina_new/wp-includes/query.php on line 1890
    [24-Jun-2015 08:10:09] ERROR PostmanWpMailBinder: wp_mail is already bound, Postman can not use it
    [24-Jun-2015 08:11:39] ERROR PostmanWpMail: Exception code=0 message=Could not read from profeina.pl
    [24-Jun-2015 08:11:39] ERROR PostmanSendTestEmailAjaxController: Test Email NOT delivered to server - 0
    [24-Jun-2015 08:11:39] ERROR PostmanSendTestEmailAjaxController: SMTP session transcript follows:
Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Cant send , error 500’ is closed to new replies.