[Closed] No frontend feedback after sending the comment

Hi @horst-v,

Please let us know is the "Use WordPress native AJAX functions" option enabled or not? 

Hi @Astghik,

Yes, it is enabled.

@horst-v,

Please find the Server Error Log file and send it to us. 

Hi @Astghik,

please find log in attached zip (.log is not allowed)

@horst-v,

Could you please create a dev/staging copy of your website in some sub-domain. Make sure the problem exists and send admin details to us (info[at]gvectors.com)? You can use Duplicator to create that site.

@Astghik,

ok - can do that later on. In the meantime I sorted out the theme error message in debug.log

Now the file contains a repeating single message as follows (no other entries are there, but this is recorded every 5 seconds more the less):

[26-Mar-2020 11:16:33 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:16:38 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:16:42 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:16:47 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:16:52 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:16:56 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51
[26-Mar-2020 11:17:01 UTC] PHP Deprecated: strstr(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in C:\inetpub\wwwroot\wordpress-files\wp-content\plugins\wpdiscuz\forms\wpDiscuzForm.php on line 51

The mentioned code is:

51 if (strstr('edit-comments.php', $pagenow)) {
52 add_filter('get_comment_text', array(&$this, 'renderAdminCommentMetaHtml'), 10, 2);
53 }

Maybe this helps us both to minimize efforts.

@horst-v,

Please let us know the PHP version.

The warnings don't have any relation to the issue.

The support team noticed some other issues while checked the issue with reCaptcha add-on. We've already asked you for the information before. All old errors are not included in the file you've sent.  

Please follow the suggestion mentioned here: https://gvectors.com/forum/postid/21364/. We'll try to find the reason for the issue. 

@Astghik,

thanks for comming back. Debugging is off by default and only activated by request. After each run we delete the old logfiles to keep them small for a better overview and not tapping into old failures after they are solved.

I cleared the logs ... started a test comment ... checked the log ... no errors but the shown above.

The PHP version is 7.3.2

Working on the test site (Duplicator installation and so on ...)

@Astghik,

based on the shortcommings of Duplicator on Wordpress network multisite I decided to give up generating a copy. Additionally I don't see sense in that action because most plugins will not work on that (based on license definitions - single site licenses). It cost me to much time and I have more important work to do these days. Therefor I decided to disable WP Discuz. I will have a look into it again as soon as I will have more time for that topic. Based on Covid-19 there are more strategic and important issues on business to solve.

You can close this ticket. I'll be back ..

ok @horst-v,

Currently, I'll close the topic. Please create a new support topic if you decide to continue testing. 

In any case, wpDiscuz works fine in may websites and this is not the wpDiscuz issue for sure (it also works fine on your duplicated site). 

@Astghik,

one question: What duplicated site do you mean? wpDiscuz doesn't work fine ... we'll see ... later on

Posted by: @horst-v

Working on the test site (Duplicator installation and so on ...)

I mean this part of the post. 

@Astghik,

ah, OK. {green}:face: