[wp-hackers] Custom field for enclosures
casey.bisson at gmail.com
Sat Mar 20 10:44:44 UTC 2010
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>
> 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.ne
>> t> 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 s
>>> 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
>> 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.
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers