Navneil Naicker

<p>You might be having a complex project where you have to show the field groups based on the page level. Thanks to ACF (Advanced Custom Fields), there is a way to make our work less painful. This plugin is very lightweight and adds functionality to show field groups depending on the page level. You can also set the page ancestor to more specific.</p>
<h4>Website</h4>
<p>http://www.navz.me/</p>
<h4>Please Vote and Enjoy</h4>
<p>Your votes really make a difference! Thanks.</p>


ACF Page Level

Sometimes you want to show the field groups based on the page level right? Well here you go. Enjoy!

Generaxion

<p>The plugin contains the features and settings generally deemed to be the most commonly used in all projects. It is meant to be used together with <a href="https://github.com/generaxion/axio-starter" rel="nofollow ugc">axio-starter</a> but functions on its own as well. Use the site specific plugin to configure the specs of this plugin.</p>
<p>This plugin replaces the previous Aucor Core and is backwards compatible with same function and filter names working.</p>
<h3>Contents</h3>
<h4>Abstract Classes</h4>
<p>Directory: root</p>
<p>The models the features are built on</p>
<h4>Features and subfeatures</h4>
<p>Directory: <code>/features/</code></p>
<p>Features (containing subfeatures) ranging from security settings to speed optimizations and dashboard cleanup.</p>
<p>admin:</p>
<ul>
<li>front page edit link</li>
<li>gallery</li>
<li>image-links</li>
<li>login</li>
<li>admin menu cleanup</li>
<li>notifications</li>
<li>profile cleanup</li>
<li>remove customizer</li>
</ul>
<p>classic-editor:</p>
<ul>
<li>tinymce</li>
</ul>
<p>dashboard:</p>
<ul>
<li>cleanup</li>
<li>recent widget</li>
<li>remove panels</li>
</ul>
<p>front-end:</p>
<ul>
<li>clean up empty html nodes</li>
<li>excerpt</li>
<li>html fixes</li>
</ul>
<p>localization:</p>
<ul>
<li>string translations</li>
</ul>
<p>plugins:</p>
<ul>
<li>acf</li>
<li>cookiebot</li>
<li>gravityforms</li>
<li>redirection</li>
<li>public post preview</li>
<li>seo</li>
<li>yoast</li>
</ul>
<p>polyfills:</p>
<ul>
<li>acf</li>
<li>polylang</li>
</ul>
<p>security:</p>
<ul>
<li>disable admin email check</li>
<li>disable file edit</li>
<li>disable unfiltered html</li>
<li>head cleanup</li>
<li>hide users</li>
<li>remove comment moderation</li>
<li>remove commenting</li>
</ul>
<p>speed:</p>
<ul>
<li>limit revisions</li>
<li>move jquery</li>
<li>remove emojis</li>
<li>remove metabox</li>
</ul>
<p>debug:</p>
<ul>
<li>style guide</li>
<li>wireframe</li>
</ul>
<h4>Helper functions</h4>
<p>Directory: root</p>
<p>Contains functions, like enhanced (internal) debugging, for all features/subfeatures to use</p>
<h3>Configuration (optional)</h3>
<h4>“Active” subfeatures</h4>
<ul>
<li>
<p>The <em>style guide</em> subfeature overrides the WP function <code>the_content()</code> with default markup for testing the most common tag styles, when the GET parameter ‘?ac-debug=styleguide’ is found in the url. You can however replace this markup with a filter:</p>
<p>add_filter(‘axio_core_custom_markup’, function($content) {<br />
  $content = ‘custom markup’;<br />
  return $content;<br />
});</p>
</li>
<li>
<p>The <em>wireframe</em> subfeature adds outlines to all elements on page to help with visual debugging, when the GET parameter ‘?ac-debug=wireframe’ is found in the url. It also appends ‘?ac-debug=wireframe’ to the href value in all anchor tags on the page to keep the feature enabled during navigation.</p>
</li>
</ul>
<h4>Disable feature/subfeature</h4>
<p>By default all the features/subfeatures are on, but you can disable the ones you don’t want with filters in theme or plugin. Here is a minimal code snippet you can use to disable features:</p>
<pre><code><?php
// disable a feature in Axio Core
add_filter('feature or subfeature key', '__return_false');
</code></pre>
<p>Note that if you disable a feature, all underlying subfeatures will be disabled as well.</p>


ACF Page Level vs Axio Core