You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
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:
Automatic core update to 5.6.1
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:
deactivated all lexicons -> no change
created simple test article (to test if something in the affected article was blocking audio creation) -> no change, also test article with NO audio
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 text was updated successfully, but these errors were encountered:
[05-Mar-2021 09:12:29 UTC] PHP Notice: Trying to get property 'ID' of non-object in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/amazon-polly/public/class-amazonpolly-public.php on line 112
As my programming skills end with the content of the log file, I would like to ask if anyone could assist.
Any help will be appreciated
Thanks in advance
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
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:
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 text was updated successfully, but these errors were encountered: