Have you tried:
- flushing any caching plugins you might be running, as well as server and/or browser caches.
- deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old
- switching to the Twenty Sixteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via FTP so the only one is
twentyfourteen. That will force your site to use it.
- manually upgrading. When all else fails, download a fresh copy of the latest.zip file of WP (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server. Read the Manual Update directions first.
Thread Starter
dudo
(@dudo)
Hi, thank you for your answer.
Ok, seems like that now if I deactivate the plugin that I develop (yasr) there is no problem.
If I activate it, on my dev machine I got this (instead of blank page)
Notice: Trying to get property of non-object in /home/dario/Web/wordpress_pro/wp-includes/comment-template.php on line 646
Notice: Trying to get property of non-object in /home/dario/Web/wordpress_pro/wp-includes/comment-template.php on line 925
So, I guess, something is changed in comment-template.php that broken my plugin.
I’ve just set up 2 wordpress installation on my machine: both of them use Twenty Fourteen 1.6, but the comment form are different: this is how appear on WP 4.3.1, and this, instead, is how it appear on 4.4.
If I try with another theme, same result.
On wordpress 4.3.1 if I try to hook on comment_form_after_fields it add custom field just before the comment textarea, from 4.4 it add fields at the bottom of the form.
The comment form changed in 4.4, to move the name and email fields below the form.
Here is information about that change:
Changes to fields output by comment_form in WordPress 4.4
Thread Starter
dudo
(@dudo)
Thank you Otto for your help.
I’ve simply fixed the visual issue by replacing comment_form_after_fields with comment_form_top.
Do you know why I got that notices? I’ve checked the comment_template.php on that lines and seems like that the functions get_comment_ID() and get_comment_text haven’t had significant changes.
Thread Starter
dudo
(@dudo)
I’ve found error of the white screen of the death, seems like I can’t use anymore get_the_ID() on the comment_post action.
@ipstenu I faced the same situation and followed your suggestion
flushing any caching plugins you might be running, as well as server and/or browser caches.
and I could put just one more comment for the next I am facing same situation ( blank wp-comments-post.php page ), Can you please let me know what may be the issue.
I am using
add_filter( 'wp_list_comments_args', 'restrict_replies_to_reply' );
function restrict_replies_to_reply( $args ){
global $post;
if ( $post->post_type == 'job_listing' ){
$args['max_depth'] = 2;
}
return $args;
}
Can this be a reason for the issue ?
@prafulla – This post was about WP 4.4 and is resolved, so you should make your own post.
Start with the usual debugging.
In general, it helps to make sure you go through the normal debugging steps. Have you tried:
- flushing any caching plugins you might be running, as well as server and/or browser caches.
- deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old
- switching to the Twenty Sixteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via FTP so the only one is
twentysixteen. That will force your site to use it.
- manually upgrading. When all else fails, download a fresh copy of the latest.zip file of WP (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server. Read the Manual Update directions first.
I am facing this issue with 4.6.1 and I think it is because of w3total cache, but I would like to use it will make a new thread with more detail.
Thank you for your reply .
