I am testing out this awesome plugin. First congrats on the Idea.

I have created a test template with an image and a couple of other fields, assigned to "posts". Template appear & works fine in Guttenberg editor. However, it doesn't output the content on the front-end if you view the page once published/saved draft.

Am I missing something? Do the developers need to output these custom data like we used to do so with custom meta fields?

On a fresh install of WP 4.9.8, using the twentyseventeen theme, and using the following plugins:

• gutenberg 3.6.2
• gcf 1.5.5
• pods 2.7.9

I create a new GCF template. My pods show up as a post type to use it with, but the fields I create in GCF don't show up when adding or editing posts of the types created by Pods. If I switch to the default Posts or Pages post type, the fields from GCF show up, but when I switch back to my Pods post type, the fields are no longer visible.

Do you know if these fields should be expected to work with post types created by the Pods plugin? Also, to be clear, I'm only concerned with seeing the fields in the administrative backend.

In my current use case I'm using multiple CPT's to create posts of differing fixed content layouts and features. I can see moving to Gutenberg I can create the same effect using templates. However, what would be really nice would be if I could assign multiple templates to a given post type and have the user select the appropriate content structure to be used as differing choices of static layout.

However right now GCF seems to only support one template per post type; you can set up multiple templates ok but there does not seem to be a mechanism for the user to select the template to use. Ideally for example, when they select Add New, I'd like for there to be a sub-menu where they can select the template they want to use. I'd also like to restrict the templates that are available based on the member role.

Is this something that can be done in GCF, am I missing something, or should this be raised with the Gutenberg team direct?

Does this plugin work for newer versions of WordPress and Custom Post Types?

It seems to be fine when using Post and Page types but I can't seem to get it to work for a custom post type.

The post type shows up on the section dropdown when setting up the fields but not in the editor (unless it's a page or post)

function register_project_type()
{
    $args = [
        'label'  => esc_html__('Projects', 'text-domain'),
        'labels' => [
            'menu_name'          => esc_html__('Projects', 'text-domain'),
            'name_admin_bar'     => esc_html__('Project', 'text-domain'),
            'add_new'            => esc_html__('Add Project', 'text-domain'),
            'add_new_item'       => esc_html__('Add new Project', 'text-domain'),
            'new_item'           => esc_html__('New Project', 'text-domain'),
            'edit_item'          => esc_html__('Edit Project', 'text-domain'),
            'view_item'          => esc_html__('View Project', 'text-domain'),
            'update_item'        => esc_html__('View Project', 'text-domain'),
            'all_items'          => esc_html__('All Projects', 'text-domain'),
            'search_items'       => esc_html__('Search Projects', 'text-domain'),
            'parent_item_colon'  => esc_html__('Parent Project', 'text-domain'),
            'not_found'          => esc_html__('No Projects found', 'text-domain'),
            'not_found_in_trash' => esc_html__('No Projects found in Trash', 'text-domain'),
            'name'               => esc_html__('Projects', 'text-domain'),
            'singular_name'      => esc_html__('Project', 'text-domain'),
        ],
        'public'              => true,
        'menu_icon' => 'dashicons-format-gallery',
        'exclude_from_search' => false,
        'publicly_queryable'  => true,
        'show_ui'             => true,
        'show_in_nav_menus'   => true,
        'show_in_admin_bar'   => true,
        'show_in_rest'        => true,
        'capability_type'     => 'post',
        'hierarchical'        => false,
        'has_archive'         => true,
        'query_var'           => true,
        'can_export'          => true,
        'rewrite_no_front'    => false,
        'show_in_menu'        => true,
        'supports' => [
            'title',
            'editor',
            'thumbnail',
            'custom-fields'
        ],

        'rewrite' => array('slug' => 'project'),
    ];

    register_post_type('project', $args);

}

add_action('init', 'register_project_type');

This feature would be useful for custom single post templates that have a predefined format for the top and bottom of their blog pages. Here are two possible implementations:

• First, as described in the title:

1. Select 'split' lock mode.
2. The GCF template field creation area splits into two areas corresponding to the top and bottom of the Gutenberg editor.

In Gutenberg, users would be able to move the blocks they create in-between, but not move their blocks above or below the header and footer custom fields respectively, so as to preserve their top and bottom position.

• Second: Creating a new field type that acts like a nested Gutenberg.

I create a fieldset, assign it to the post type, I enter data and it all seems fine in Gutenberg. When I visit the frontend none of the fields are visible. All the usual Gutenberg blocks will display as normal on the frontend. I expected the GCF blocks to display the same way.

Gutenberg Version 2.7.0 GCF Version 1.5.1

user error I'm sure.

Hi - I noticed that in version 1.5.0 you fixed a i18n error which works fine when I download your version 1.5.0 from GitHub but when installing it through WP-Admin the scripts/i18n folder is still missing. Looking at the SVN the folder is missing.

GCF 1.5.0 on WP SVN ==> https://plugins.svn.wordpress.org/gutenberg-custom-fields/tags/1.5.0/scripts/ GCF 1.5.0 on your GIT ==> https://github.com/youknowriad/gcf/tree/v1.5.0/scripts

The version on the WP plugin repo gives me the following error Warning: filemtime(): stat failed for /var/www/vhosts/website/wp-content/plugins/gutenberg-custom-fields/scripts/i18n/build/index.js in /var/www/vhosts/website/wp-content/plugins/gutenberg-custom-fields/lib/i18n-script.php on line 46

Hi Riad, It seem custom fields templates does not appear in posts published before custom fields templates creation. I'm using WP 4.9.4 with Gutenberg from the Github repo (master branch).

Wouldn't it be cleaner if the custom fields would be below the Gutenberg area? The fields are "just" a way to edit the post_meta at the moment so the top should reflect the site as much as it will look like on the frontend.

This PRs adds a repeater field. The content of the field is saved as JSON, if you use this field make sure you json_decode its value before usage.

This PR comes with a small redesign of the template form to accommodate the nesting aspect of the repeater field.

closes #11

I have Gutenberg and GCF activated to test my site. I use custom fields extensively through the Advanced Custom Fields plugin. I tried recreating a custom field in Gutenberg Custom Fields, but no new blocks show up for the custom field when I try to create or edit a page (I chose pages for the post type for the new custom field). I thought there might be a conflict with ACF so I deactivated it, but that didn't help. Next, I deactivated all plugins except Gutenberg and GCF, but the block for the custom field I added in GCF still isn't showing up. I'm at a loss as to why I can't get GCF to work in my installation.

How to add a Gutenberg block instead of a custom field?

For example: I have installed this Custom Gutenberg Block that add the native Wordpress Featured Image: https://github.com/modularwp/gutenberg-block-featured-image

How to add a Featured Image after title with all lock options?

I've created a new GCF template and added the text field large_title. Now I want to create a custom post page, where I can choose where to output the large_title text.

I've tried with get_post_meta( $frontpage, $large_title ); - frontpage being the title of the template in GCF, but that didn't work. I've also tried some other combinations. How do I do this?

When a block or template is deleted, the postmeta is not deleted. This is an issue because in templates, the data will be retrieved using get_post_meta.

Reproduce:

• make a template
• make a post, fill out the template and save
• go back into the post, delete the block then save

You can keep an eye on the postmeta table to see that it's still there or put a filter on the content to view it (at the bottom)

There are a couple of ways of fixing:

• delete postmeta on block deletion and delete all instances of the meta_keys used in a template on template deletion (so as not to leave orphaned uneditable/undeletable data)
• use a dynamic render which won't show the postmeta data unless the block is there

I think the first is the way to go as it avoids the orphaned data issue.

Cheap and cheerful content filter:

function mjj_filter_content( $content ){
	$post_id = get_the_ID();
	if( empty( $post_id ) ){
		return $content;
	}
	$gcf_postmeta = get_post_meta( $post_id, 'main field', true );
	if( empty( $gcf_postmeta ) ){
		return $content;
	}
	return '<h2>' . print_r( $gcf_postmeta, true ) . '</h2>' . $content;
}
add_filter( 'the_content', 'mjj_filter_content' );