gqevu6bsiz

This plugin is manage of custom options for site.
You can create the options easily. 
And, you can use for Template. 
 .
And then, you can use to Shortcode for Post. 
 [coppi key=”example”]
If you create a lot of options, You can manage the category for custom options.
<h3>日本語でのご説明</h3>
このプラグインは、オプションの値を追加できるようにするプラグインです。 
作成したオプション値は、テンプレートで使用でき、 
記事本文でショートコードとしても使用できます。

CUSTOM OPTIONS PLUS POST IN

This plugin is create to custom options in your WordPress. You can use in the Template and Shortcode.

NicolasKulka

Amaury Balmer

Maxime Culea

BE API

Are you using Advanced Custom Fields for option pages and Polylang for your multilingual site?
Polylang does not natively support ACF Option Pages, so option values are shared across all languages. This plugin improves that: once activated, you can set different values per language. Values are stored per language in the database and the correct one is loaded according to the current Polylang language. If a value isn’t set for a language, the “All languages” value is used by default.
Note: On activation, existing option values become temporarily unavailable (but remain in the database); you can recover them by deactivating the plugin. To edit options for a language, use the Polylang language switcher in the admin bar before opening the options page.
Requirements: WordPress 6.0+, PHP 7.4–8.4, <a href="https://www.advancedcustomfields.com/pro" rel="nofollow ugc">Advanced Custom Fields</a> 5.6.0+, <a href="https://polylang.pro/" rel="nofollow ugc">Polylang</a> (tested up to 3.7.7).
For full documentation (usage, filters, API, excluding pages, default fallback, loading untranslated values), see the <a href="https://github.com/BeAPI/acf-options-for-polylang#readme" rel="nofollow ugc">project README on GitHub</a>.

ACF Options For Polylang

Improves Polylang by adding per-language support for ACF options pages—each language can have its own option values.

CUSTOM OPTIONS PLUS POST IN vs ACF Options For Polylang