Notifications
Clear all

WPDiscuz Frontend Moderation and Defender Pro

12 Posts
3 Users
0 Reactions
2,754 Views
Posts: 36
Topic starter
(@johannes)
Eminent Member
Joined: 6 years ago

Hello,

What do you mean by that?

Reply
1 Reply
Elvina
(@elvina)
Joined: 5 years ago

Support
Posts: 1403

@johannes,

The issue is caused by the Defender Pro plugin.

It will be better if you contact the Defender Pro plugin support and ask them that question.

 

Reply
Elvina
Posts: 1403
(@elvina)
Support
Joined: 5 years ago

@johannes,

To find the reason of the issue the developers will need to modify the wpDiscuz Frontend Moderation add-on files. Please read this article to learn more about plugin editing feature: https://www.webhuntinfotech.com/enable-theme-plugin-editor-wordpress/

 

Reply
Posts: 36
Topic starter
(@johannes)
Eminent Member
Joined: 6 years ago

Hello,

I talked with the developer and they did thorough testing of any compatibility issues. They say the problem is caused by the frontend moderation plugin. 

So I would ask you to have another closer look at the problem, maybe you can find the issue.

Best wishes

Johannes

Reply
1 Reply
Elvina
(@elvina)
Joined: 5 years ago

Support
Posts: 1403

@johannes,

The developers one more time checked the issue and saw that the issue is caused by Defender Pro plugin. Please see the recorded video below:

https://www.screencast.com/t/ACB909s2

The error message:

<br><b>Uncaught Error</b>: Call to a member function to_array() on null in <b>/var/web/site/public_html/wp-content/plugins/wp-defender/app/module/audit/component/comment-audit.php</b> on line <b>155</b><br><ul><li>processGenericComment()</li><li>invokeArgs()<br><span class="qm-info qm-supplemental">wp-content/plugins/wp-defender/app/module/audit/event-abstract.php:253</span></li><li>build_log_data()<br><span class="qm-info qm-supplemental">wp-content/plugins/wp-defender/app/module/audit/component/audit-api.php:360</span></li><li>WP_Defender\M\A\C\{closure}()<br><span class="qm-info qm-supplemental">wp-includes/class-wp-hook.php:290</span></li><li>apply_filters()<br><span class="qm-info qm-supplemental">wp-includes/class-wp-hook.php:312</span></li><li>do_action()<br><span class="qm-info qm-supplemental">wp-includes/plugin.php:478</span></li><li>do_action()<br><span class="qm-info qm-supplemental">wp-includes/comment.php:1429</span></li><li>wp_delete_comment()<br><span class="qm-info qm-supplemental">wp-content/plugins/wpdiscuz-frontend-moderation/class.wpDiscuzFrontEndModeration.php:403</span></li><li>deleteComment()<br><span class="qm-info qm-supplemental">wp-includes/class-wp-hook.php:288</span></li><li>apply_filters()<br><span class="qm-info qm-supplemental">wp-includes/class-wp-hook.php:312</span></li><li>do_action()<br><span class="qm-info qm-supplemental">wp-includes/plugin.php:478</span></li><li>do_action()<br><span class="qm-info qm-supplemental">wp-admin/admin-ajax.php:175</span></li></ul><p>Es gab einen kritischen Fehler auf deiner Website.</p><p><a href=" https://wordpress.org/support/article/debugging-in-wordpress/ ">Erfahre mehr über die Fehlerbehebung in WordPress.</a></p>

Even if you deactivate the wpDiscuz plugin, each time when you try to delete the comments from the backend the issue still exists.

 

Reply
Page 2 / 2
Share:
Scroll to top