Automatic calculating of MP3 length causing errors on some websites
Several tickets have been opened since last update for users not able to post new sermons and getting the following error message.
Warning: file_get_contents(/audio/pastor_ron/ttbs2/19-PSA/2014-19-PSA-119-081.mp3) [function.file-get-contents]: failed to open stream: No such file or directory in /home/rondozler/www.ccmyrtlebeach.com/wp-content/plugins/sermon-manager-for-wordpress/includes/podcast-functions.php on line 168
Warning: Cannot modify header information - headers already sent by (output started at /home/rondozler/www.ccmyrtlebeach.com/wp-content/plugins/sermon-manager-for-wordpress/includes/podcast-functions.php:168) in /home/rondozler/www.ccmyrtlebeach.com/wp-includes/pluggable.php on line 1196
That is from HelpScout ticket # 590
Here is an alternate error message featuring Amazon S3 as file source
Warning: file_get_contents(http://peircemain.s3.amazonaws.com/Sermoncasts/Moments%20with%20the%20Master/04%20-%20A%20Touching%20Moment.mp3) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /home/content/11/11260111/html/wp-content/plugins/sermon-manager-for-wordpress/includes/podcast-functions.php on line 168
Warning: Cannot modify header information - headers already sent by (output started at /home/content/11/11260111/html/wp-content/plugins/sermon-manager-for-wordpress/includes/podcast-functions.php:168) in /home/content/11/11260111/html/wp-includes/pluggable.php on line 1196
From HelpScout ticket # 600
Comments (3)
-
reporter -
reporter #836
-
reporter ongoing issue still...
- Log in to comment
Make that three tickets. HelpScout ticket # 601