WP 3.6 Audio Player, multisite, Accept-Ranges: bytes

  • Resolved Michael

    (@eizzumdm)


    10 years, 7 months ago

    We have been trying to get the new WordPress 3.6 audio player working with one of our fall semester courses that heavily features audio. The problem we are experiencing manifests in Safari and mobile Safari, and it only occurs on subsites of a multisite subdirectory environment.

    The audio player cannot get the length of the movie clip, so it does not allow scrubbing the audio or jumping to different locations in the audio. On iOS, the end duration displays as NaN:NaN.

    Everything works perfectly on main site, the one at blogs.princeton.edu. However, on subsites of the multisite environment, the audio only works properly if I supply the original URL (no .htaccess rewrites).

    Here is my test page:
    https://blogs.princeton.edu/wdstest/2013/08/14/audio-test/
    All of the working audio clips return the response header Accept-Ranges: bytes
    The non-working clips do not return this response header.

    The first source URL for the audio is the problem one on the production server:
    https://blogs.princeton.edu/colonialsounds/files/2013/08/01.mp3

    The second source URL works fine, and is the same file on the same server, but it does not use WordPress’s htaccess rewrite rules:
    https://blogs.princeton.edu/wp-content/blogs.dir/164/files/2013/08/01.mp3

    The third source URL also works, and is the same file, but it is on the main site.
    https://blogs.princeton.edu/wp-content/uploads/2013/09/01.mp3

    Does anyone have experience with this and might be able to help us? Is this a bug for all multisite environments in WordPress 3.6?

    Thanks,
    Michael

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Michael

    (@eizzumdm)

    10 years, 7 months ago

    We may have found the answer after some more Googling.
    http://www.technowut.com/2012/05/14/how-to-stream-videos-to-ios-devices-with-multisite-wordpress/

    This solved the issue on my local development environment (MAMP). I installed mod_xsendfile, added SendFile on and XSendFilePath /path/to/wordpress to my httpd.conf file, and I added define('WPMU_SENDFILE', true); to my wp-config.php file.

    I did find out through trial and error, that if WPMU_SENDFILE is set to true, but xsendfile is not properly configured, all audio files on the server fail.

    If this works in our QA and production environments (RedHat Enterprise Linux), I will update this thread.

    Thread Starter Michael

    (@eizzumdm)

    10 years, 6 months ago

    I wanted to update and resolve this thread just in case someone searches for this problem, expecting to find a resolution.

    We finally had time to install mod_xsendfile on our QA environment, but the audio files now returned 404 errors. I finally figured out that the value I was using for XSendFilePath contained a symbolic link because we use a version control system.

    My original setting for XSendFilePath was /var/local/www/wordpress/current/public with “current” being an alias to a directory name with a timestamp. Everything worked after I changed the XSendFilePath to /var/local/www/wordpress

    Now our audio player works as it should in Safari and mobile Safari.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WP 3.6 Audio Player, multisite, Accept-Ranges: bytes’ is closed to new replies.