If Reply button doesn't work

Yup! I found this trick to work. I deactivated Jetpack Comments, and now the reply button works.

The proposed solution doesn’t work for me. I cleared caches, disabled Jetpack and WP Rocket caching plugin but it makes no difference. The Reply button doesn’t even show. I am using the latest version of WordPress. Browser console doesn’t seem to help.

• This reply was modified 8 years ago by Lethalmiko.

Update: I disabled every single plugin except this one but the Reply button simply does not show, whether in Chrome or Firefox.

Ok, you have JS error if it doesn’t work. JS errors mostly comes from the active theme. Please leave website URL to allow us debug it.

I changed the theme to the default WordPress themes Twenty 14, 15 and 16 and the same thing happens so it is probably not the theme. The console shows the following:
—
JQMIGRATE: Migrate is installed, version 1.4.1
diggers.news/:1 Error in event handler for (unknown): TypeError: Cannot read property ‘command’ of undefined at
chrome-extension://fhplmmllnpjjlncfjpbbpjadoeijkogc/js/hooks/content.min.js:1:228

The script with the error is:

https://diggers.news/wp-includes/js/jquery/jquery-migrate.min.js,qver=1.4.1.pagespeed.jm.C2obERNcWh.js

The original URL is:

https://diggers.news/opinion/2016/10/27/who-would-open-a-newspaper-today/

It is a locked site in beta testing but you can register to be able to look at other pages.

Thanks in anticipation.

Update: I found the solution which works here:

https://gvectors.com/forum/how-to-and-troubleshooting/reply-button-not-present/#post-983

The nested comments option was not active. I would suggest you put this as part of the solution in your post above.

I have the same issue in 4.0.6

Console shows an error with WPdiscuz cookie.

Turning off the CDN solves the issue (flushing CDN cache does not solve)

Downgrading to 4.0.4 also solved it, which is what I did.

Can you fix 4.0.6?

Hi,

I’m using WordPress 4.7.3

I disabled all the plugins except wpdiscuz. I activated default twentyfifteen theme. Besides, I also turn on nested commenting and post is allowed to comment.

The reply works normally. But when I clicked the textarea, the submit button didn’t show at all.

When I looked into the source code, it shows <div class="wc-form-footer" style="display: block;"> </div> Nothing inside div block.

Any ideas to solve this problem?

Regards

I guess I found the solution.

wc-form-footer block is blank since $this->formeStructure is empty in Form.php, which means initFormMeta() doesn’t work properply.

In my situation, wpDiscuz works normally on my localhost. Then I used all-in-one migration plugin to fully migrate my whole site to another server. Then it failed, people can click the reply button, can type in the textarea, but the submit button never shows.

Minutes ago, I just logged in the backend, and went to Comment -> wpDiscuz -> Forms. It amazingly worked after opening the default form. So I guess it needs an extra initialization for the comment form especially after migration.

Hope it helps other people who suffer from similar problems.

Regards

Please don’t search problem in wpDiscuz core, it’s outside of core. wpDiscuz is a popular plugin and dozens of thousands website use it without any issue.
I think some data is not properly inserted in database during installation or update. I’d recommend you navigate to Dashboard > Comments > Forms admin page, edit the Default Form and save it. then delete all caches and do Ctrl+F5 on post front-end.

First, I’m not searching the problem in the core. As I mentioned, it works on my localhost, but not on our real server. There must be something wrong with the migration or the server configuration. What we need to know is why it doesn’t work, and what I was sharing is the whole debugging process. Without that, would you still recommend me what we should do? Would you or could you?

Second, you don’t need to be that offensive to people who tried to read the core. I know it’s a very unusual problem. And I didn’t expect too much when I raised the question for the first time. You can just ignore me, as you did. But you don’t need to immediately recommend me after I posted the solution. Next time, don’t recommend too late.

Third, I admit it’s a nice and popular plugin. You are right, it works on dozens of thousands websites without any issue. But why we are here, and why this support forum exists here?