Polly not working after Core upgrade to WP 5.6.1

  • Resolved minickel

    (@minickel)


    3 years, 9 months ago

    Hi,
    the AWS for WordPress plugin stopped working creating audio files after the WP Core was updated from 5.6.0 to 5.6.1
    The audio player is still visible, but there is no audio created in the S3 bucket.
    The only changes to the website were twofold:
    1. Automatic core update to 5.6.1
    2. SSL advanced settings through .htaccess (however those have been reversed and do not seem to play a role)

    Could you please check to compatibility of WP 5.6.1 and AWS Polly and make the necessary changes in the plugin is needed.

    I have tested the following possible sources of issues:
    1. deactivated all lexicons -> no change
    2. created simple test article (to test if something in the affected article was blocking audio creation) -> no change, also test article with NO audio
    3. deactivating and reactivating text-to-speech

    I cannot downgrade to 5.6.0 at present, since the site runs on a multisite network and this would affect more sites.

    Support will be greatly appreciated. Thank you.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter minickel

    (@minickel)

    Appendix: The following code is rendered

    <div id="amazon-ai-player-container">
<audio class="amazon-ai-player" id="amazon-ai-player" preload="none" controls   controlsList="nodownload" >
<source type="audio/mpeg" src=""></audio>
		</div>
<div id="amazon-polly-subscribe-tab"></div>
<div id="amazon-polly-by-tab"></div>

    So, there is also no audio link created (empty src=””)

    Thread Starter minickel

    (@minickel)

    Using a staging site, I downgraded the core to 5.6, but the plugin is still not working, neither on new posts, nor on the post where it stopped working on the production site.

    Logging is active, but no errors are logged.

    Using the latest pliugin version, I downgraded to 4.2.1 and updated to 4.2.2 again, with no result. Neither of the plugin versions working.

    The only change I had made apart from the automatic core upgrade to 5.6.1 has been adding the following lines reagrding ssl to the .htaccess – however I have removed them, without any effect on the issue, which still remains. However, the question is, if something of these settings will still remain active once set, even after removing from .htaccess 

    Header always set Strict-Transport-Security: "max-age=31536000" env=HTTPS 
Header always set Content-Security-Policy "upgrade-insecure-requests"
Header always set X-Content-Type-Options "nosniff"
Header always set X-XSS-Protection "1; mode=block"
Header always set Expect-CT "max-age=7776000, enforce"
Header always set Referrer-Policy: "no-referrer-when-downgrade"

    Any ideas what the issue could be?

    Thread Starter minickel

    (@minickel)

    @tstachlewski – any suggestions how to regain functionality?

    @brandonfire – you seem to have resolved a similar issue a while ago (https://www.ads-software.com/support/topic/text-to-speech-not-working/) – May I ask you to share how you resolved it?

    Thread Starter minickel

    (@minickel)

    In addition, I have deactivated (in the staging sandbox) all plugins that had been updated since the last successful audio conversion, but still the issue prevails … Not sure what option is left now to look into

    Not 100% sure – I believe updating the plugin solved it at that time or republishing the posts.

    Thread Starter minickel

    (@minickel)

    Thank you @brandonfire for your time and will to reply. Republishing a post helped in past issues sometimes and I also had one case before, where a certain German abbreviation crashed the audio creation, which was fixed by removal of this. However now, it stopped working completely, also for new posts with only a few simple words …

    Still hope for a solution, since I love the text-to-speech functionality …

    Thread Starter minickel

    (@minickel)

    One addition towards the additional ssl headers in .htaccess:

    Basically I can rule out that those affected the AWS plugin. I implemented those changes a day before the last audio-update of a post was created by polly. So the plugin stopped working independently of those headers for sure ….

    Still would be very much appreciating some support, @tstachlewski, @awslabs, @wpengine, @stevenkword

    Thread Starter minickel

    (@minickel)

    Looking into the timing details of the issue again, I can now also rule out that the core update to 5.6.1 created the issue, since the update came in a day before the last audio conversion took place after a post update according to my S3 bucket.

    I also ran tests to roll back and/or deactivate all plugins that got updates between February 5 (last conversion) and Feb 10 (detection of the issue):

    – Cookie Notice & Compliance for GDPR / CCPA 2.0.1 -> 2.0.2
    – Really Simple SSL 4.0.7 -> 4.0.8
    – Mailpoet 3 3.59.1 -> 3.59.2
    – WP Fastest Cache 0.9.1.4 -> 0.9.1.5
    – WP User Avatar 2.2.10 -> 2.2.11

    Rolling back or deactivating those plugins does NOT fix the AWS for WordPress Polly issue I encounter. I ran out of ideas on how to possibly fix it.

    Thread Starter minickel

    (@minickel)

    Ok guys, here is the solution and the whole story: the issue is user-dependent. Nothing else – quite trivial, yet, i don’t understand, why AWS for WordPress behaves that way.

    My page is a multi-user-blog. So far, I have created all Posts through a super-user account and audio conversion worked just fine.

    The problem began, after I started using my author account. Since that fell together with the WP Core upgrade and some plugin updates, i never thought that simply switching the user could make audio conversion stop working. Today, by chance, I switched back to the super-user account and audio conversion worked again.

    Is there any way of making the plugin work for more users? It is certainly not a issue of user rights, since both accounts I used are formally super-user accounts with the same rights. I just use one as a general super-user for setup and maintainance more … that is the one which works, which ahs likely been used to install AWS for WordPress …

    • This reply was modified 3 years, 9 months ago by minickel.
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Polly not working after Core upgrade to WP 5.6.1’ is closed to new replies.

Tags