Contributors: Takahashi_Fumiki, tarosky
Tags: custom field
Requires at least: 4.4.0
Tested up to: 4.4.3
Stable tag: 1.0
License: GPLv3 or later
License URI: http://www.gnu.org/licenses/gpl-3.0.txt

TaroSky's Custom Field manager. Scalable, Well-Structured and Maintainable. Requires PHP5.4 or later.

Custom fileds are stuff box for WordPress. They can store almost everything. Number, Date, CSV and nested array.

Besides that, custom fields can be used for many purpose.

• To display extra information for posts.
• To sort posts by their event date.
• To hide posts from unregsitered user.

Thus, they can be easily uncontrollable.

TSCF provides scalable way. A JSON file indicates what custom fields should be and you can get their value.

You can maintain it on VCS like git or svn.

Additional features:

• Supports child theme. you can override config file.
• JSON editor. But we don't recommend it. Don't edit it directly on production environment.

1. Upload the plugin files to the /wp-content/plugins/tscf directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the 'Plugins' screen in WordPress
3. If JSON doesn't exist, put it or create from Appearance > Custom Fields Config

An answer to that question.

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets directory take precedence. For example, /assets/screenshot-1.png would win over /tags/4.3/screenshot-1.png (or jpg, jpeg, gif).
2. This is the second screen shot

• A change since the previous version.
• Another change.