[Solved] Displaying multiple error messages

@asti I have been using both plugins together for more than 1 year without this problem. It started when WPDiscuz done the most recent update. Please can you take some responsibility and fix these issues. If you cant then I should request a full refund so we can use an alternative plugin that works without conflicts. Like i said you guys have made some changes which is now becoming an issue. It is not fair that you do an update and i should have to goto BuddyPress and and them for support. When the issue started on your plugin. Can you see the logic in this !!?

Actually, it worked!! Brilliant thank you Asti 😀

Actually, it worked!! Brilliant thank you Asti 😀@asti

@asti This worked. I'm now dancing with Joy 🤗 🤗 

@asti The only problem now is the emoji window not closing. I sent you example earlier last week!!

@betazoid,

As I've already mentioned here  the issue comes from the priority-nav.min.js file. It causes the issue.

@asti hi, hope you well.

1. Just to confirm i'm having a new issue since the recent update. I  have done a quick diagnostic and deactivated most of the plugins and found the issue is coming directly from the WPDiscuz (Private comments. Please see attached screenshot as well as a snippet of the error messages displayed when it happens. My website works perfectly fine as soon as i deactivate the (Private Comments) add-on!!

//// ** ERROR MESSAGE SNIPPET HERE ** ////

Fatal error: Uncaught Error: Too few arguments to function wpDiscuzPrivateComment::wpdiscuzFoundCommentsQuery(), 1 passed in /nas/content/live/clusterview01/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected
in /nas/content/live/clusterview01/wp-content/plugins/wpdiscuz-private-comments/wpDiscuzPrivateComment.php on line 433

Call stack:

wpDiscuzPrivateComment::wpdiscuzFoundCommentsQuery()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/plugin.php:206
apply_filters()
wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php:884
WpdiscuzCore::foundCommentsQuery()
wp-includes/class-wp-hook.php:287
WP_Hook::apply_filters()
wp-includes/plugin.php:206
apply_filters()
wp-includes/class-wp-comment-query.php:954
WP_Comment_Query::set_found_comments()
wp-includes/class-wp-comment-query.php:422
WP_Comment_Query::get_comments()
wp-includes/class-wp-comment-query.php:346
WP_Comment_Query::query()
wp-includes/class-wp-comment-query.php:303
WP_Comment_Query::__construct()
wp-includes/comment-template.php:1467
comments_template()
wp-content/themes/videopro/single-video.php:133
require()
wp-includes/template.php:725
load_template()
wp-includes/template.php:672
locate_template()
wp-includes/general-template.php:168
get_template_part()
wp-content/themes/videopro/single.php:11
include()
wp-includes/template-loader.php:106
require_once()
wp-blog-header.php:19
require()
index.php:17

/// END ///

2. Please can you also show exactly where the is with the priority-nav.min.js file. Is this something you can fix from your end? 

@betazoid,

The first issue is already fixed. Please update the addon to the latest version.

2. Please can you also show exactly where the is with the priority-nav.min.js file. Is this something you can fix from your end? 

The issue can not be fixed by our side. If you enable the plugin we'll be able to point you the problem maker.