• Resolved Hiroki Sano

    (@novembersteps)


    Posting from Japan.

    I upgraded Amazon polly plugin from ver 1.0.11 to ver 2.0.2.

    Although ver1.0.11 was able to be executed normally, ver2.0.2 plugin reported a fatal error message.

    Because of I don’t know what solution for this fatal error,after all, I downgraded from 2.0.2 to 1.0.11.(executing normally)

    Excerpt of error message:
    Client error: POST https://polly.ap-northeast-1.amazonaws.com/v1/speech resulted in a 400 Bad Request response:
    {“message”:”Invalid SSML request”} in /RequestException.php:113

    My Enviroments:
    Amazon EC2(Tokyo Region)
    OS:CentOS Linux release 7.4.1708 (Core)
    httpd: Apache/2.4.6
    PHP:7.1.16

    Best regards.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @novembersteps,
    Did you enable SSML in plugin settings page?

    Thread Starter Hiroki Sano

    (@novembersteps)

    >>Did you enable SSML in plugin settings page?

    Yes of course.

    When I did set up plugin that I enabled SSML on polly setting menu both ver 1.0.11 and ver 2.0.2.
    (On plugin update from 1.0.11 to 2.0.2, setting was take over.)

    ##additional info/my enviroment:
    WordPress:4.9.6(ja)

    Best regards.

    Thread Starter Hiroki Sano

    (@novembersteps)

    Hi.

    This is additional fatal error messages on use ver 2.0.2.

    Stack trace:
    #0 Middleware.php(66):GuzzleHttp\\Exception\\RequestException::create(Object(GuzzleHttp\\Psr7\\Request), Object(GuzzleHttp\\Psr7\\Response))
    #1 WrappedHttpHandler.php on line 191, referer: https://mywebsite/wps/wp-admin/post.php?post=190&action=edit

    Best regards.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    @novembersteps,
    1) Any chances to get bigger log file part? I’m especially interested to see what was send to backend (which text).
    2) Also is it happening with each new text?
    3) And are you using some actual SSML tags in your text?

    Thread Starter Hiroki Sano

    (@novembersteps)

    Dear tstachlewski,

    >>1) Any chances to get bigger log file part? I’m especially interested to see what was send to backend (which text).

    I prepared now. If you need for analyzing,You can get logfile(gzip) from this URL.
    https://s3-ap-northeast-1.amazonaws.com/wordpress-polly-log/php_fatal_error.log.gz
    (from now within 24 hours)

    >>2) Also is it happening with each new text?
    Yes.I meet fatal error in every time always creating new post.
    (Always It can not checking Checkbox”Enabling Amazon Polly”.)

    >>3) And are you using some actual SSML tags in your text?
    According to depends on contents. For example,one of post is using SSML tags,and,other contents is only plain-text post.

    Best regards.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @novembersteps,
    Sorry for late answer. The log file is not publicly accessible, could you make it public (if you can of course) so I could check it?

    Thread Starter Hiroki Sano

    (@novembersteps)

    Dear tstachlewski,

    You can download from now.
    Expiration date is Jun 23, 2018 9:00:00 AM GMT.
    (S3 lifecycle is configured.)

    URL:
    https://s3-ap-northeast-1.amazonaws.com/wordpress-polly-log/php_fatal_error.log.gz

    Best regards.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @novembersteps
    Unfortunately those logs didn’t add a lot of information. Any chance that we could move to email (stachlew @ amazon com) to discuss it in more details?

    Thread Starter Hiroki Sano

    (@novembersteps)

    Dear tstachlewski,

    OK.I will email to you later.

    Best regards.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @novembersteps,
    Should be fixed in latest release (2.0.3). If the problem will still exists, please let me know!

    Cheers,
    Tomasz

    Thread Starter Hiroki Sano

    (@novembersteps)

    Dear tstachlewski,

    Now,I installed plugin latest ver 2.0.5 to new enviroment(Amazon EC2,PHP ver 7.1.19 on CentOS 7).

    This version is OK,so far.

    Thanks!

    Best regards.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘ver 2.0.2 fatal error’ is closed to new replies.