How do I use WPDiscuz with HivePress?

General HivePress
1

Hi, I’m trying to use wpDiscuz on ListingHive listings, and I’ve run into several issues that I hope someone can clarify for the current (2026) version of HivePress.

What I’ve already tried

1. Enabled Reviews and renamed everything to “Comments” I tried using the built‑in Reviews extension and changed all labels from “Reviews” to “Comments.” However, HivePress requires a rating value before submitting, so hiding the stars breaks the form. Leaving the stars visible works, but it’s confusing because users are commenting, not rating.

2. Tried adding wpDiscuz via the Template Editor I attempted to add wpDiscuz using:

  • Code blocks

  • Shortcode blocks

  • HTML blocks

But the Listing template containers seem locked. Custom blocks either don’t move into the correct region or replace the entire listing page with only the comment form.

3. Tried this snippet from HivePress AI but it didn’t work.

add_filter(
    'hivepress/v1/templates/listing_view_page',
    function( $blocks, $template ) {
        // Only on single listing pages
        if ( ! is_singular( 'hp_listing' ) ) {
            return $blocks;
        }

        // Get the listing post object
        $post = get_queried_object();
        
        if ( ! $post || 'hp_listing' !== $post->post_type ) {
            return $blocks;
        }

        // Get wpDiscuz comments output
        ob_start();
        comments_template();
        $comments_html = ob_get_clean();

        // Add comments to the listing page (after the main content)
        if ( ! empty( $comments_html ) ) {
            $blocks['listing_comments'] = [
                'type'    => 'content',
                'content' => $comments_html,
            ];
        }

        return $blocks;
    },
    1000,
    2
);

It looks like HivePress has changed its template system since then.
There is no listing_view_page template in my version, and the block editor doesn’t allow PHP or shortcodes in the listing content area.

What I’m trying to achieve
I want wpDiscuz to replace the default WordPress comment form on ListingHive listings, the same way it replaces comments on posts and pages.

My question
What is the current way to load comments_template() on the listing view page?

Is there a modern hook for the new template system?

Or should I override a specific HivePress template file in a child theme?

If so, which file handles the single listing view in the latest version?

Any updated guidance or code snippet for the current HivePress version would be greatly appreciated.

Thank you!

Brenda
2

Thanks for your message — our team will reply shortly.

In the meantime, you can also get instant help from our AI Assistant, familiar with all the docs and solutions we’ve shared over the years.

3

Hi @BrendaRobosa If your requirement is to hide the rating and keep comment. You can make the rating field optional, and remove it from submit form.

add_filter(‘hivepress/v1/forms/review_submit, 	function( $form ) {
if ( isset( $form[‘fields’][‘rating’] ) ) { 			
unset($form[‘fields’][‘rating’]) // Remove field from form 		
} 		
return $form; 	
}, 1000 );

add_filter(‘hivepress/v1/models/review’, function ( $model ) { 		
// Make rating not required 		
$model[‘fields’][‘rating’][‘required’] = false; 		
return $model; 	
}, 1000 );
2 Likes
4

Hi NajeebKhan, thank you so much for taking the time to reply and for sharing this snippet — I really appreciate it. Making the rating field optional and removing it from the submit form is definitely helpful, and it’s a good fallback option for me.

My main goal, though, is to attach wpDiscuz to ListingHive listings, because wpDiscuz provides a much more robust and feature‑rich commenting experience compared to the Reviews system (even when the rating is removed). I’m hoping to use wpDiscuz the same way it replaces the default WordPress comment form on posts and pages.

I’ve tried a few approaches already, including the recent snippet from HivePress AI, but it looks like the listing_view_page template no longer exists in the current version, and the block editor doesn’t allow PHP or shortcodes in the listing content area.

So while removing the rating is a good Plan B, I’m still trying to find the current recommended way to load comments_template() on the single listing page so wpDiscuz can hook into it.

If you have any guidance on the modern hook or template override for the latest HivePress version, I’d be really grateful.

Thanks again for your help!

— Brenda

5

Hi @BrendaRobosa,

The default Listing model doesn’t support WordPress comments. You can try enabling comments for Listings using the following snippet:

function comment_support_for_listings() {
    add_post_type_support( 'hp_listing', 'comments' );
}
add_action( 'init', 'comment_support_for_listings' );

If you need any further assistance or help with any customization, I’d be happy to provide a paid consultation. You can contact me on Fiverr: Customize your website | HivePress

1 Like
10

Hi,

Please try the following approach:

  1. Deactivate the HivePress Reviews plugin.
  2. Add the following snippet to the Code Snippets plugin [How to add custom code snippets - HivePress Help Center]: Making a comment system - #7 by yevhen
  3. Go to WordPress Dashboard > wpDiscuz > Forms > Default Form and, under Display comment form for post types, add hp_listing [fixing tip #2]: Missing Comment Form - wpDiscuz - WordPress Comment Plugin.
  4. For existing listings, enable the Allow comments option in the Discussion section of the listing editor: Loom | Free Screen & Video Recording Software | Loom.

After completing these steps, the expected result should look like this: Loom | Free Screen & Video Recording Software | Loom

Hope this helps

1 Like
11

This is SO cool, @kseniia :star_struck:

Cheers,
Chris :victory_hand:

1 Like
12

Thank you. I’ll try it. I hope the snippet works even though it’s from 2022.

13

While we continuously update and improve HivePress, the core principles and underlying functionality remain stable. This means that older snippets usually continue to work correctly with the latest HivePress versions.

We also tested the snippet before providing it to you, and it worked correctly in our latest test environment. So in this particular case, the age of the snippet shouldn’t be a concern.

HivePress was designed to be clean, flexible, and easy to customize, and we continue to follow these principles in our development. As a result, solutions recommended in our older topics can still remain fully applicable even after multiple updates.

14

ok sounds good. Thank you so much Kseniia.

1 Like