Scott Reilly

This plugin provides a powerful widget, shortcode (with shortcode builder tool), and template tags for easily retrieving and displaying custom field values for posts or pages.
The power of custom fields gives this plugin the potential to be dozens of plugins all rolled into one.
This plugin allows you to harness the power of custom fields/meta data. Use the “Get Custom Field” widget, the <code>[custom_field]</code> shortcode (which has a post editor sidebar widget to help you build the shortcode), or one of six template tags to retrieve and display custom fields. Find a custom field for the current post, a specified post, a recent post, or randomly. And for the custom field values found by the plugin, you may optionally specify text or HTML to appear before and after the results. If nothing is found, then nothing is display (unless you define text to appear when no results are found). If multiple results are found, only the first will be displayed unless you specify a string to be used to join the results together (such as “,”), in which case all will be returned. Visit the Examples section to see how this plugin can be cast in dozens of different ways.
There are six template tags provided by this plugin. Here they are, with an explanation of when they are appropriate for use:
<ul>
<li><code>c2c_get_custom()</code> : Use this inside “the loop” to retrieve a custom field value for a post</li>
<li><code>c2c_get_current_custom()</code> : This is only available on the permalink post template (single.php) and page template (page.php). Can be used inside or outside “the loop”. Useful for using custom field to define text you want to include on a post or page’s header, footer, or sidebar.</li>
<li><code>c2c_get_post_custom()</code> : Useful when you know the ID of the post whose custom field value you want.</li>
<li><code>c2c_get_random_custom()</code> : Retrieve the value of a random instance of the specified custom field key, as long as the field is associated with a published posted, non-passworded post (you can modify a setting in the plugin file to search passworded posts as well).</li>
<li><code>c2c_get_random_post_custom()</code> : Retrieves the value of random custom field(s) from a post when you know the ID of the post you’re interested in.</li>
<li><code>c2c_get_recent_custom()</code> : Retrieves the most recent (according to the associated post’s publish date) value of the specified custom field.</li>
</ul>
You can filter the custom field values that the plugin would display. Add filters for ‘<code>the_meta</code>‘ to filter custom field data (see the end of the code file for commented out samples you may wish to include). You can also add per-meta filters by hooking ‘<code>the_meta_$sanitized_field</code>‘. <code>$sanitized_field</code> is a clean version of the value of <code>$field</code> where everything but alphanumeric and underscore characters have been removed. So to filter the value of the “Related Posts” custom field, you would need to add a filter for ‘<code>the_meta_RelatedPosts</code>‘.
Links: <a href="https://coffee2code.com/wp-plugins/get-custom-field-values/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/get-custom-field-values/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/get-custom-field-values/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Developer Documentation</h3>
Developer documentation can be found in <a href="https://github.com/coffee2code/get-custom-field-values/blob/master/DEVELOPER-DOCS.md" rel="nofollow ugc">DEVELOPER-DOCS.md</a>. That documentation covers the numerous template tags, hooks, and shortcode provided by the plugin.
As an overview, these are the template tags provided the plugin:
<ul>
<li><code>c2c_get_custom()</code> : Template tag for use inside “the loop” and applies to the currently listed post.</li>
<li><code>c2c_get_current_custom()</code> : Template tag for use on permalink (aka single) page templates for posts and pages.</li>
<li><code>c2c_get_post_custom()</code> : Template tag for use when you know the ID of the post you’re interested in.</li>
<li><code>c2c_get_random_custom()</code> : Template tag for use to retrieve a random custom field value.</li>
<li><code>c2c_get_random_post_custom()</code> : Template tag for use to retrieve random custom field value(s) from a post when you know the ID of the post you’re interested in.</li>
<li><code>c2c_get_recent_custom()</code> : Template tag for use outside “the loop” and applies for custom fields regardless of post.</li>
</ul>
These are the hooks provided by the plugin:
<ul>
<li><code>c2c_get_custom_field_values_shortcode</code> : Filter to customize the name of the plugin’s shortcode.</li>
<li><code>c2c_get_custom_field_values_post_types</code> : Filter to customize the post types that should support the shortcode builder metabox.</li>
<li><code>get_custom_field_values/can_author_use_shortcodes</code> : Filter to customize if post author can make use of the ‘custom_field’ shortcode.</li>
<li><code>get_custom_field_values/show_metabox</code> : Filter to customize if the shortcode builder metabox is shown.</li>
</ul>
The shortcode provided is <code>[custom-field]</code>, which has a number of attributes to customize its behavior and output.

Get Custom Field Values

Use widgets, shortcodes, and/or template tags to easily retrieve and display custom field values for posts or pages.

WordPress.org

Secure Custom Fields (SCF) extends WordPress’s capabilities, transforming it into a flexible content management tool. With SCF, managing custom data becomes straightforward and efficient.
Easily create fields on demand. 
The SCF builder makes it easy to add fields to WordPress edit screens, whether you’re adding a new “ingredients” field to a recipe or designing complex metadata for a specialized site.
Flexibility in placement. 
Fields can be applied throughout WordPress—posts, pages, users, taxonomy terms, media, comments, and even custom options pages—organizing your data how you want.
Display seamlessly. 
Using SCF functions, you can display custom field data in your templates, making content integration easy for all levels of developers.
A comprehensive content management solution. 
Beyond custom fields, SCF allows you to register new post types and taxonomies directly from the SCF interface, providing more control without needing additional plugins or custom code.
Accessible and user-friendly design. 
The field interface aligns with WordPress’s native design, creating an experience that’s both accessible and easy for content creators to use.
Installing this plugin will deactivate plugins with matching function names/functionality, specifically Advanced Custom Fields, Advanced Custom Fields Pro, and the legacy Secure Custom Fields plugins, to avoid code errors (this is the same behavior as ACF Pro).
Read more about Secure Custom Fields at <a href="https://developer.wordpress.org/secure-custom-fields/" rel="nofollow ugc">developer.wordpress.org/secure-custom-fields</a>.
<h4>Features</h4>
<ul>
<li>Clear and easy-to-use setup</li>
<li>Robust functions for content management</li>
<li>Over 30 Field Types</li>
</ul>

Secure Custom Fields


In case anyone is not clear - this is a "nulled" plugin - an exact copy of the paid support Pro version of Advanced Custom Fields, with the code to handle licensing and updates stripped out. This clearly part of the petty high school drama playing out between two multi million dollar for-profit companies, and it is going to wreak havoc on the entire WordPress ecosystem.



Who's going to invest in creating great Pro plugins if everyone's always afraid that Wordpress.org itself is going to just rip them and put them up on the main plugin repo if they don't like you today.



The "freemium" model has created great jobs for a lot of small development shops and many individual designers and developers depend on the quality and support you get from paid Pro level plugins to do their jobs.



I have no particular love for WP Engine, but this sets a horrible new precedent that is going to put the livelihoods of may less powerful individuals at risk. It must be stopped now!


Unprecedented bad behavior


Hello, WordPress contributors,



I am using WordPress as a developer more than 5 years.



And I have also contributed. There are some plugins in the Repository WP Adminer, Library Viewer, Gift Wrapping for WooCommerce, with old these plugins have 100% 5-stars reviews.



But this behaviour is Unacceptable.



What are the GPL requirements? Here you just took Advanced Custom Field Pro, removed their license system, changed the plugin author details without copyright anywhere WP Engine (the author of ACF Pro) and you released it as yours.







Such other "marketplaces" do in the Web...



Is all this ethical?



I have also paid plugins! Are you going to take them also?



Trust in WordPress is being cloned with your actions...


Unacceptable behaviour


ACF disabled gallery field and broke few sites, changed to SCF and everything started to work again. Thank you!


Great replacement for ACF


I am pleased to observe the addition of numerous valuable features without the frequent reminders about upgrading to a premium version.


Work great, no add for premium

Secure Custom Fields boosts content management with custom fields and options. It deactivates Advanced Custom Fields to prevent duplicate code errors.

Get Custom Field Values vs Secure Custom Fields