webdeveric

This plugin provides a simple <code>[meta]</code> shortcode that allows you to fetch meta information for the current <code>$post</code>. 
There are options to return a single value, multiple values joined by a user defined string, or a JSON string.
Examples:
<pre><code>[meta name="your_meta_field"]
</code></pre>
This will return the value of “your_meta_field”. If the value is an array, it will return a comma separated list, unless you specify an alternative join string.
<pre><code>[meta name="your_meta_field" single="false"]
</code></pre>
By default, [meta] will return a single value. If you have multiple meta fields with the same name, you can get them all by setting single=”false”.
<pre><code>[meta name="your_meta_field" single="false" json="true"]
</code></pre>
This will return the JSON encoded value of “your_meta_field”.
<pre><code>[meta name="your_meta_field" single="false" join="|"]
</code></pre>
This will return a pipe separated values of “your_meta_field”.
<pre><code>[meta name="your_meta_field" shortcode="false"]
</code></pre>
By default, the value will be passed to do_shortcode, unless you turn if off.
<pre><code>[meta name="your_meta_field" filters="true"]
</code></pre>
There are a couple filters available if you want to filter the value. They are called after do_shortcode and before any JSON/array handling. 
They are on be default, but can be turned of with filters=”false”. The filters are “meta_fetcher_value” and “meta_fetcher_{$name}”.

Meta Fetcher

This plugin provides a simple [meta] shortcode that allows you to fetch meta information for the current $post.

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.

Meta Fetcher vs Secure Custom Fields