Gutenberg Compatibility

  • Resolved Brad Griffin

    (@burlesonbrad)


    1 year, 11 months ago

    Am I to understand that Mike’s plugin isn’t cool with the new Gutenberries Block editor (yet)?
    https://prnt.sc/FmpGfQdcSy4A
    In that screenshot above, we see the default Job Listing initially has the ‘Classic’ editor section enabled by default.
    When I click ‘Remove Block’, the Gutenberry Editor doesn’t show up. The _content field is now rendered unclickable entirely.
    So, I’ll start over with a new job posting. This time, I’ll leave the Gutenberry Editor’s ‘Classic’ block, but drop some text in there. Then, I’ll click the ‘Convert to blocks’ button. Drumroll please 🥁…. nothing happens😮😯.

    What am I running?

    1. Newspack theme from this little mom and pop startup company called Automattic.
    2. What plugins might/could/possibly be conflicting? Well, they are all Automattic plugins that the Newspack crew has put out.
    3. Who is hosting this? Again, it’s still under the Automattic umbrella with Pressable!

    Is this behavior happening by ‘default’ and WP_Job_Manager is simply not compatible with the Gutten Berries?
    Is this a bug within my setup? (please don’t go there, it’s all default Automattic plugins)
    Is this a ‘future feature’ with Mike’s plugin? If so, how far out are we on this?

    Any other thoughts or suggestions?

    Thanks! -Brad

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Renatho (a11n)

    (@renathoc)

    1 year, 11 months ago

    Hi Brad!

    This is really the expected behavior because Job Manager was built with frontend usage in mind (users submitting the jobs through the submit job form). You can see it explained in this link: https://wpjobmanager.com/document/dealing-troublesome-themes/#section-7

    I explored it a little to see if I could offer you a workaround, in case you plan to create the jobs through the WP Admin. So I created this snippet for you:

    
add_filter( 'register_post_type_job_listing', function( $args ) {
	unset( $args['template'] );
	unset( $args['template_lock'] );

	return $args;
} );

    Since it’s not the default behavior, I’d recommend you test the features you are using to make sure everything will work properly with the blocks before start using. 😉

    Best,
    Renatho

    Thread Starter Brad Griffin

    (@burlesonbrad)

    1 year, 10 months ago

    https://prnt.sc/k3gX1nXEFDHc

    So, now we can use the Gutenberg to drop a .pdf, make cover images, and do everything else (whatever is wanted) without adding all types of additional plugins.

    And, thanks to you, the front end still works fine for those who want to make their own job listings.
    https://oneburleson.com/post-a-job/

    Genius! Obrigado Renatho. Obrigado!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Gutenberg Compatibility’ is closed to new replies.