[wp-hackers] Custom field for enclosures

[Karl Wångstedt]

The response headers from the server is video/quicktime and video/mp4. So as far as I can tell everything is correctly configured and behaves as expected on the server.

This is what I get from the server for the quicktime movie:

	• Accept-Ranges:bytes
	• Cache-Control:max-age=3600
	• Connection:Keep-Alive
	• Content-Length:16396702
	• Content-Type:video/quicktime
	• Date:Sat, 20 Mar 2010 12:33:31 GMT
	• Etag:"4e453e5-fa319e-4821b130a1b80"
	• Expires:Sat, 20 Mar 2010 13:33:31 GMT
	• Keep-Alive:timeout=15, max=500
	• Last-Modified:Thu, 18 Mar 2010 22:51:42 GMT
	• Ms-Author-Via:DAV
	• Server:Apache/2.2.13 (Unix) mod_ssl/2.2.13 OpenSSL/0.9.8l DAV/2 PHP/5.3.1 SVN/1.6.5

But still, does it work for any of you guys, or do you get the same results as I do?

Karl Wångstedt



20 mar 2010 kl. 11.44 skrev Casey Bisson:

> 
> I've had the same problem where Apache was configured to send the right mime type, but other factors broke it. In my case it was the cache that munged the header.
> 
> You should check wht the output actually is, not what it's set to be.
> 
> 
> On Mar 20, 2010, at 5:22 AM, Karl Wångstedt <maillist at wangstedt.net> wrote:
> 
>> Both .mov and .mp4 is configured to return video/quicktime and video/mp4 respectively in httpd.conf. I don't think that is where the problem is.
>> 
>> Do you get the enclosures field populated automatically?
>> 
>> I did open a ticket in Trac, but if it's only affecting my install I'll delete it.
>> 
>> Karl Wångstedt
>> 
>> 
>> 
>> 19 mar 2010 kl. 14.26 skrev Otto:
>> 
>>> On Thu, Mar 18, 2010 at 5:54 PM, Karl Wångstedt <maillist at wangstedt.net> wrote:
>>>> One of the sites I manage is a podcasting site, and I'm preparing a move to html5 (with <video>) and WP3 for it — hence the test site.
>>>> 
>>>> It seems like the enclosure custom field isn't automatically generated when a video is linked to in the post anymore.
>>> 
>>> Check the mime type.
>>> 
>>> WordPress does a call to get the file via the webserver and looks at
>>> the headers return. If the mime type that the webserver returns starts
>>> with "video" or "audio" then it gets enclosed. So if your webserver
>>> isn't configured to return the right mime type for that filetype, no
>>> enclosure gets made.
>>> 
>>> This all happens in do_enclose, which gets called from do_all_pings,
>>> which is hooked to the do_pings action, which is a scheduled event
>>> created by the _publish_post_hook.
>>> 
>>> -Otto
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> 
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers