WordPress.org

Crna Gora

Get WordPress
WordPress.org

Plugin Directory

Secure Custom Fields

Secure Custom Fields

By WordPress.org
Download

Description

Secure Custom Fields (SCF) turns WordPress sites into a fully-fledged content management system by giving you all the tools to do more with your data.

Use the SCF plugin to take full control of your WordPress edit screens, custom field data, and more.

Add fields on demand.
The SCF field builder allows you to quickly and easily add fields to WP edit screens with only the click of a few buttons! Whether it’s something simple like adding an “author” field to a book review post, or something more complex like the structured data needs of an ecommerce site or marketplace, SCF makes adding fields to your content model easy.

Add them anywhere.
Fields can be added all over WordPress including posts, pages, users, taxonomy terms, media, comments and even custom options pages! It couldn’t be simpler to bring structure to the WordPress content creation experience.

Show them everywhere.
Load and display your custom field values in any theme template file with our hassle-free, developer friendly functions! Whether you need to display a single value or generate content based on a more complex query, the out-of-the-box functions of SCF make templating a dream for developers of all levels of experience.

Any Content, Fast.
Turning WordPress into a true content management system is not just about custom fields. Creating new custom post types and taxonomies is an essential part of building custom WordPress sites. Registering post types and taxonomies is now possible right in the SCF UI, speeding up the content modeling workflow without the need to touch code or use another plugin.

Simply beautiful and intentionally accessible.
For content creators and those tasked with data entry, the field user experience is as intuitive as they could desire while fitting neatly into the native WordPress experience. Accessibility standards are regularly reviewed and applied, ensuring SCF is able to empower as close to anyone as possible.

Documentation and developer guides.
Over 10 plus years of vibrant community contribution alongside an ongoing commitment to clear documentation means that you’ll be able to find the guidance you need to build what you want.

Features

  • Simple & Intuitive
  • Powerful Functions
  • Over 30 Field Types
  • Extensive Documentation
  • Millions of Users

Screenshots

  • Simple & Intuitive

  • Made for Developers

  • All About Fields

  • Registering Custom Post Types

  • Registering Taxonomies

Reviews

I have to verify I’m not with WP Engine now to enter the community?

15. Oktobar 2024.
This is so crazy. Give the plugin back to the people that spent thousands of dollars and man hours building it, acquiring it and improving it. Developers beware – if they do this to one company they can do it to anyone. There’s no problem with a plugin offering a paid version and promoting it with ads. I’ve seen WAY more intrusive pro plugin advertising on other plugins. Besides the Pro version actually works really well and adds good features.

Do not use Secure Custom Fields (SCF), for yourself and the whole community

15. Oktobar 2024.
Guys, please stop this war. I’ve been developing websites with WordPress for 18 years, and I feel that this situation is harming my business and creating risks for me. Sure, it’s nice to have a free ACF Pro plugin, but in the long run, it creates huge problems. I’m sure it will be extremely hard to support Secure Custom Fields because you need a dedicated team that knows what they’re doing.

I do not recommend using the plugin

15. Oktobar 2024.
Guys, please stop this war. I’ve been developing websites with WordPress for 10 years, and I feel that this situation is harming my business and creating risks for me. Sure, it’s nice to have a free ACF Pro plugin, but in the long run, it creates huge problems. I’m sure it will be extremely hard to support Secure Custom Fields because you need a dedicated team that knows what they’re doing.

Breach of trust by automatically re-linking all users’ sites.

15. Oktobar 2024.
The recent ‘fork’ is a huge breach of trust in the repository. I can understand the disagreement between WordPress.org and wpengine.com. I can understand (but do not entirely agree) with removing wpengine from the repository, and telling them to host on their own infrastructure. I can almost even understand whole cloth forking GPL code from ACF as a new plugin. (although it would be better to just integrate more flexible content handling in WordPress core) However, I do not understand how it can be considered reasonable to replace all links to users’ sites. This is dependency hijacking, and it reeks similar to the polyfill.io situation. I am very glad I have auto-updates turned off.

Don’t destroy WordPress, Matt!

15. Oktobar 2024.
Hey Matt! Please don’t destroy Wordpress with this war. 🙏 It’s useless like any war and destroys more that it gains for any given participant. Millions of people rely on Wordpress to make money out of it – mostly small business and freelancers like myself. That’s the whole point of Wordpress: Giving people a great OS for their websites – and build something great upon it. Some make it at greater scale like WP Engine. They might be idiots. Or But in the end, a rising flood raises all ships, doesn’t it? Isn’t it a possibility to just let them do whatever they do? And see Wordpress prosper?
Read all 1.300 reviews

Contributors & Developers

“Secure Custom Fields” is open source software. The following people have contributed to this plugin.

Contributors

“Secure Custom Fields” has been translated into 31 locales. Thank you to the translators for their contributions.

Translate “Secure Custom Fields” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

6.3.6.2

Release Date 12th October 2024

  • Security – Harden fix in 6.3.6.1 to cover $_REQUEST as well.
  • Fork – Change name of plugin to Secure Custom Fields.

6.3.6.1

Release Date 7th October 2024

  • Security – ACF defined Post Type and Taxonomy metabox callbacks no longer have access to $_POST data. (Thanks to the Automattic Security Team for the disclosure)

Meta

Ratings

See all
Log in to submit a review.

Support

Issues resolved in last two months:

44 out of 66

View support forum