chaleybgis

The fix is easy. If someone can get ahold of the developer here’s what worked for me. (not heavily tested, but it appears to work.)

Gutenberg uses the REST API so Taxonomy’s must be registered with “show_in_rest => true”.

WP Post Series registers the post_series taxonomy on line 68 of wp-post-series.php..

If you add

‘show_in_rest’ => true,

above line 78 — ‘show_ui’ => true,

you should see the series metabox in Gutenberg.

Note: If you edit the file directly, plugin updates will wipe your changes. However, the plugin hasn’t been updated for 3 years, so it is unlikely that will happen. If you’re worried about it, the register_taxonomy() function can update existing post types as well, so you could fairly easily craft a function in functions.php that would be impervious to updates.
Developer, if you’re out there, thanks for this neat little plugin, hope you find the time to update it for Gutenberg.

• This reply was modified 5 years, 7 months ago by chaleybgis.
• This reply was modified 5 years, 7 months ago by chaleybgis.

Whaddya know. A little bit of patience and it’s working just fine. Thank you for the prompt response.

Quick Q if you don’t mind. I notice that “Contact Form” and “Email” are both options for output, but I’m not seeing any output for these fields. What is Contact Form intended to do? And do you know if emails not showing is due the data not being there, or possibly a bug?

Thanks for this plugin. The world needs it.

I think removing the default margin is absolutely the best way to go here for new users although if it changes the way the layouts behave when folks upgrade the plugin to the latest version I could see that being a problem. Might be better to just add the default value in the attribute editor.

• This reply was modified 7 years, 4 months ago by chaleybgis.

Cool. Thanks for the plugin. It works really well.

I apologize, I didn’t recognize that syntax. It may be that this particular site is using an aging version of PHP. Changing the lines as suggested seems to fix everything up. No PHP error and forms appear to submit and save fine.

Here is the line from my error log with the previous line in place:

PHP Parse error: syntax error, unexpected ‘[‘ in class-gf-field-repeater.php on line 286

Thanks for the help!

I’ve tried that eight or nine times. I think it has something to do with the doubled review that posted with no stars (I only posted once).

It will not let me edit my review, nor post a new one. My apologies. 5 STARS!

Excellent work Kodie. Many, many thanks.

It’s things like this that are steadily driving me towards developing websites using ProcessWire or Concrete5. Two really nice alternatives to WordPress.

Actually that documentation was the first line on the link that jeffparker provided

Custom post types

To make YARPP support your custom post type, the attribute yarpp_support must be set to true on the custom post type when it is registered. It will then be available on options on the YARPP settings page.

I think that you need to add the yarrp_support parameter when you register your CPT.

Like this:

add_action( 'init', 'create_post_type' );
function create_post_type() {
	register_post_type( 'acme_product',
		array(
			'labels' => array(
				'name' => __( 'Products' ),
				'singular_name' => __( 'Product' )
			),
		'public' => true,
		'has_archive' => true,
                'yarpp_support' => true
		)
	);
}

If you’ve created the CPT with a plugin, you may have to remove it and add it via functions.php. If you’re using Custom Post Type UI I think you can export your post type to a function then add the yarpp_support parameter.

Note: I haven’t tested this and have no idea if it will work or not.

@mariusbratu –

You should be able to safely echo get_the_title(); outside of the loop,,

I had the same problem.. I altered line 674 of index.php in plugins/wp-orbit-slider to read:

// Create an array with default values that we can use to build our query

			$query = array('numberposts' => $numberposts, 'post_type' => $post_type, 'orderby' => 'menu_order', 'order' => 'ASC');

Note: This will be over-ridden on plugin upgrade so be careful…

In the following lines it looks like there may be a function for passing cutom query parameters but my PHP is not strong enough to determine if that’s the case…