이 플러그인은 최근 3개의 주요 워드프레스 출시와 시험 되지 않았습니다. 워드프레스의 좀 더 최근 버전으로 이용할 때 더 이상 관리되지 않고 지원되지 않고 호환성 문제가 있을 수 있습니다.

Advanced Custom Fields: oEmbed Field

설명

Requires the Advanced Custom Fields plugin. Output can be selected as HTML embed, URL, or data object. Includes settings for preview and output resolution and will accept any provider registered in WordPress.

With the news that ACF V5 includes a built-in oEmbed field type, we’re discontinuing further development of this plugin. The plugin will remain online for legacy V4 support to those that haven’t upgraded, but only essential updates will be released.

Compatibility

This add-on will work with:

  • Advanced Custom Fields version 4 and up
  • Repeater Field

스크린샷

  • The Add Field interface.
  • The field in an Advanced Custom Field.

설치

This add-on can be treated as both a WP plugin and a theme include.

Plugin

  1. Copy the ‘acf-oembed’ folder into your plugins folder
  2. Activate the plugin via the Plugins admin page

Include

  1. Copy the ‘acf-oembed’ folder into your theme folder (can use sub folders). You can place the folder anywhere inside the ‘wp-content’ directory
  2. Edit your functions.php file and add the code below (Make sure the path is correct to include the acf-oembed.php file)

    add_action(‘acf/register_fields’, ‘my_register_fields’);

    function my_register_fields()
    {
    include_once(‘acf-oembed/acf-oembed.php’);
    }

FAQ

What oEmbed sources are supported?

Any supported by WordPress. See Embeds on wordpress.org

Can I use this in a repeater field?

Yep, you sure can.

후기

이 플러그인에 대한 평가가 없습니다.

기여자 & 개발자

“Advanced Custom Fields: oEmbed Field”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

자국어로 “Advanced Custom Fields: oEmbed Field”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하세요.

변경이력

1.0.3

  • Remove PHP short tag dependancy
  • Fix for ‘Missing argument’ warning when getting the object and not supplying arguments

1.0.2

  • Improve reliability on freaky servers

1.0.1

  • Prevent PHP error caused by missing v3 compatibility

1.0.0

  • Initial Release.