John Huebner

<p>*** New feature added: Custom Post ID Slugs ***</p>
<p>This is an add on plugin for Advanced Custom Fields (ACF) 5 + the Options Page Add On (or ACF Pro).<br />
<strong><em>This plugin will not provide any functionality unless ACF 5 and the Options Page Add On (or ACF5 Pro)<br />
is installed</em></strong></p>
<p>This plugin provides an admin interface for adding options pages in ACF including all options for ACF<br />
options pages. Most options are selectable, for example the menu location, capability and where to save<br />
field values to.</p>
<p>For more information see<br />
<a href="https://wordpress.org/plugins/options-page-admin-for-acf/other_notes/" rel="ugc">Other Notes</a> and<br />
<a href="https://wordpress.org/plugins/options-page-admin-for-acf/screenshots/" rel="ugc">Screenshots</a></p>
<h3>Github Repository</h3>
<p>This plugin is also on GitHub<br />
<a href="https://github.com/Hube2/acf-options-page-adder" rel="nofollow ugc">https://github.com/Hube2/acf-options-page-adder</a></p>
<h3>Change Capability</h3>
<p>The capability required to add/edit options page settings is “manage_options”. This capability can be changed by adding a filter.</p>
<pre><code>add_filter('acf-options-page-adder/capability', 'my_acf_options_page_adder_cap');
function my_acf_options_page_adder_cap($cap) {
  $cap = 'edit_published_posts';
  return $cap;
}
</code></pre>
<h3>Saving Values to the Options Page Post</h3>
<p>ACF v5.2.7 added the ability to save options page fields to a post ID. This plugin will let you save the options to the same post ID of the post created when adding an options page using this plugin. You can even use get_fields($options_page_id) without needing to worry about getting the fields for the options page itself. Why? because all the fields used for creating the options page start with an underscore _ and will not be returned by get_fields(). The only thing you need to be careful of is not using any of the field names used by this plugin, which should be extremely easy since they all start with <em>acfop</em>.</p>
<h3>Saving Values Using a Custom post ID slug</h3>
<p>It is posible to use a custom slug for saving options page values. For example, if you wanted to save values of an options page to a user you could supply “user_1” as the $post_id value for the opitons page. This also has another side effect. Normally, when ACF saves values to “options” in the options table you will find the fields with the “options_” prefix. So for example, if your field name is “my_field” then in the options table you will find “options_my_field” as the options name. You can supply a custom slug for this, let’s say that you set the post ID setting for the options page to “my-custom-slug”. this would cause the same field in the options page to have the name “my-custom-slug_my_field”. 2 New options have been added to this plugin and you can choose to use the options page slug for the post ID or you can specify a custom slug to use instead.</p>
<h3>Get Post ID for Options Page</h3>
<p>A function and a filter are available for getting the correct ACF $post_id value to use for getting<br />
values from the options page. This function/filter will return ‘options’ for options pages stored in<br />
options or will return the correct post ID if options are saved to a post. The correct ID is returned<br />
based on the “menu_slug” value of the options page.</p>
<pre><code>/ example 1: function get_options_page_id()

// get the post_id of an options page
$post_id = get_options_page_id('my_options_page_slug');
// get a value using $post_id
$value = get_field('my_option_field', $post_id);

// or it can be combined like this
$value = get_field('my_option_field', get_options_page_id('my_options_page_slug'));



// example 2: by filter
$default = 'option',
$slug = 'my_options_page_slug';
$post_id = apply_filters('get_option_page_id_filter', $default, $slug);
$value = get_field('my_option_field', $post_id);

// or it can be combined like this
$value = get_field('my_option_field', apply_filters('get_option_page_id_filter', $default, $slug));
</code></pre>
<p><em>There is a condition where you will get the incorrect post id. This condition is created by having a top level redirect page that is set to redirect to the first sub options page. If there is no sub options page that exists then it will return the value for the top level options page. If you later create a sub options page it will return the new value from the sub options page. This is why I have see the default value of redirect to false. If you want the top level page to redirect the you need to be aware that it can cause you issues later down the road if you haven’t created a sub option page. You should also specifically set the order of sub options pages so that these do not change at some point in the future because adding a new options page with the same order as the existing top level page will alter the save and get location to the new options page. There’s noting I can do about this, it the way it works. When setting up ACF options pages to save to a post instead of options you must be more precise in with the options page arguments.</em></p>
<h3>Font Awesome Support</h3>
<p>Please note that this plugin does not enqueue or include Font Awswsome in the admin of your site.<br />
If you include Font Awsome in your admin then you can use Font Awesome Icons for the icons of<br />
top level options page. For example if you wanted to use <a href="http://fontawesome.io/icon/address-book/" rel="nofollow ugc">Address Book Icon</a> then all you need to do is add <code>fa fa-address-book</code><br />
into the Icon field when adding or editing the options page.</p>
<h3>Filter Options Page Header/Footer/Content</h3>
<p>Version 3.8.0 of this plugin added the ability to customize the ACF options page by adding header and footer content. In addtion to the WYSIWYG fields that have been added to the options page admin editor you can also customize these sections, or the entire options page using filters.</p>
<p>Version 3.8.2 of this plugin adds a toggle to enable this feature. This feature can cause an out of<br />
memory fatal error on options pages that have large numbers of fields. If content was entered into this field before the toggle to turn in on then the toggle will be automatically turned on. Otherwise the default for this option will be off.</p>
<p><strong>Header Content</strong></p>
<pre><code>add_filter('acf-options-page-adder/page-header', 'my_custom_options_page_header', 10, 2);

function my_custom_options_page_header($content, $hook) {
  // $content = content, by default it is '' or the value of the WYSIWYG editor
    // $hook = the current options page hook that is being called
    $content = '<p>My Custom Header Content</p>';
    return $content;
}
</code></pre>
<p><strong>Footer Content</strong></p>
<pre><code>add_filter('acf-options-page-adder/page-footer', 'my_custom_options_page_footer', 10, 2);

function my_custom_options_page_footer($content, $hook) {
  // $content = content, by default it is '' or the value of the WYSIWYG editor
    // $hook = the current options page hook that is being called
    $content = '<p>My Custom Footer Content</p>';
    return $content;
}
</code></pre>
<p><strong>Filter Entire Options Page</strong></p>
<pre><code>add_filter('acf-options-page-adder/page-content', 'my_custom_options_page_filter', 10, 2);

function my_custom_options_page_filter($content, $hook) {
  // $content = entire content or options page, including all ACF fields
    // $hook = the current options page hook that is being called
    // caution should be taken when making modification to the page content
    return $content;
}
</code></pre>
<h3>Remove Nag</h3>
<p>If you would like to remove my little nag that appears on some admin pages add the following to your functions.php file</p>
<pre><code>add_filter('remove_hube2_nag', '__return_true');
</code></pre>


ACF Options Page Admin

Allows easy creation of options pages using Advanced Custom Fields Pro without needing to do any PHP coding. Requires that ACF5 Pro is installed (or A …

NicolasKulka

Amaury Balmer

Maxime Culea

BE API

<p>Are you using Advanced Custom Fields for option pages and Polylang for your multilingual site?</p>
<p>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.</p>
<p><strong>Note:</strong> 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.</p>
<p>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).</p>
<p>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>.</p>


ACF Options For Polylang

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

ACF Options Page Admin vs ACF Options For Polylang