Comment submit button disappeared after 4.2 update

Hi,

I can’t seem to solve this problem, I can’t find the comments_form location. Should it be in the functions.php folder?

Thanks,

Hello,

Can someone tell me what page I need to be editing and where? Is this a function I can add to my child theme functions.php? I don’t want to be editing ANY core files so I hope this is an issue that can be resolved by editing something in my child theme.

thanks!

Could you create a new thread https://www.ads-software.com/support/forum/how-to-and-troubleshooting#postform

I created a new thread here:
https://www.ads-software.com/support/topic/upgrade-to-wordpress-422-and-comment-submit-button-is-gone?replies=1#post-6933164

thanks

Hi:

I’m having the same issue on my blog, and we have not been able to resolve it with the above cut-and-paste option.

Does anyone know if Word Press is addressing this?

Has anyone attempted to ROLL BACK to the last Word Press operating system?

Thanks.

Same problem here. Using the Oxygen theme. I don’t understand where the code given above should go, so cannot implement the fix myself.

I didn’t understand where to put this replacement code at first either, but then I figured it out. I’m using the Origin theme, and the submit button had disappeared on my site.

Hope this is helpful:

1. In WordPress, go to Appearance –> Editor and select Theme Functions (functions.php). Make yourself a copy of all the text in case you screw up so you can revert back.
2. Locate the text to replace. I did this by doing a CTRL+F search of ‘id_form’ => ‘commentform’
3. I commented out the old text rather than deleting it. So beginning with the line that reads ‘id_form’ => ‘commentform’, mine now looks like this:
   /* ‘id_form’ => ‘commentform’,
   ‘id_submit’ => ‘submit’,
   ‘title_reply’ => __( ‘Leave a Reply’, ‘origin’ ),
   ‘title_reply_to’ => __( ‘Leave a Reply to %s’, ‘origin’ ),
   ‘cancel_reply_link’ => __( ‘Click here to cancel reply.’, ‘origin’ ),
   ‘label_submit’ => __( ‘Post Comment →’, ‘origin’ ),
   */
   ‘id_form’ => ‘commentform’,
   ‘id_submit’ => ‘submit’,
   ‘class_submit’ => ‘submit’,
   ‘name_submit’ => ‘submit’,
   ‘title_reply’ => __( ‘Leave a Reply’ ),
   ‘title_reply_to’ => __( ‘Leave a Reply to %s’ ),
   ‘cancel_reply_link’ => __( ‘Cancel reply’ ),
   ‘label_submit’ => __( ‘Post Comment’ ),
   ‘submit_button’ => ‘<input name=”%1$s” type=”submit” id=”%2$s” class=”%3$s” value=”%4$s” />’,
   ‘submit_field’ => ‘<p class=”form-submit”>%1$s %2$s</p>’,
   ‘format’ => ‘xhtml’
   );
4. Click Update File to save and then check to make sure it worked

Thanks for the detailed explanation, but my theme seems to be different (Celebrate) and there is no ‘id_form’ => ‘commentform’ in the functions.php folder… The only similar thing I have is <?php comment_form(); // Loads the comment form. ?> which appears in the comments.php folder. Should I be adding code on there?

Thanks!

I, too, have a different theme that uses similar code to Willvonarend. I can’t seem to find where I need to load it. (I’m still trying to figure out how to fix it, given that difference.)

Whoop, I found the solution for my theme. Here it is:

I am using a version of the formerly free Cascade theme by DevPress (it’s since become a paid theme, apparently, but I got it when it was a freebie). The fix above, involving edits to the functions.php file, doesn’t work for me since Cascade doesn’t have any comment-related stuff in the functions.php. You actually have to edit the Comments.php file, which is part of the theme.

As the theme hasn’t yet been updated, and the theme author hasn’t responded to my email, I went ahead and figured it out for myself, and I thought I’d share the solution for those who are hunting for a fix for their own blog.

Note: I don’t know about other themes. I can’t help you with other themes. This post is really just intended as some information for people who are frustratedly searching for a solution; maybe it’ll be another piece of the puzzle for some of you. I hope so!

Steps:

1. Back up everything. If you don’t, and your blog goes boom, it’s your own fault.

2. I advise you make a child theme (there’s a plugin out there that creates one for you, very one easily), copy the Comments.php file to the child theme, switch your Theme to the child theme, and then edit that theme’s Comments.php file. That way, you’ll have the original theme intact, in case something goes terribly wrong.

Note: In Cascade, there are two very similarly named files: Comments.php, and comment.php. You need to edit Comments.php.

3. If you’ve done steps 1 and 2, and are ready to proceed, look in the Comments.php file and find this block of code:

<?php comment_form( array( 'title_reply' => __( 'Post Comment', 'cascade'  ) ) ); // Loads the comment form.
?>

4. Replace that block, and only that block, with this:

<?php comment_form( array( 'title_reply' => __( 'Post Comment', 'cascade'  ),
'submit_button'        => '<input name="%1$s" type="submit" id="%2$s" class="%3$s" value="%4$s" />',
'submit_field'         => '<p class="form-submit">%1$s %2$s</p>' ) ); // Loads the comment form.
?>

That’s it.

Perhaps those whose functions.php file lacks comment-related code might find a similar fix works for their own blogs. I hope so!

Thank you, Dssouthe!

I took a chance and pasted in your code– it worked! ??

Great. It’s works. Thanks.

Great solution Gordsellar and thank you all for your help it works now.

– To replace core files in WordPress from a previous version is not a good solution.

– I suggest you all contact your respective theme developers and bring the issue to their attention so that they can fix it in their theme’s next version.

– As some of you have alluded to, this is not a WordPress core issue.

– Looks like some of you are using 4.2 or less. I encourage you to update to the current version 4.2.2

– With the exception of the OP, if you need help, as per the Forum Welcome, please post your own topic. That way you stand a good chance of getting full attention to your specific issue. Despite any similarity in symptoms, your issue is likely to be completely different because of possible differences in physical servers, accounts, hosts, plugins, theme, configurations, etc. Thus one problem, on one setup is not indicative of the functionality and reliability of an application as a whole.

@willvonarend,

Glad it worked for you! ??

Gord