Php Wordpress插件SEO Facebook导致错误:在没有堆栈fram的情况下引发异常

Php Wordpress插件SEO Facebook导致错误:在没有堆栈fram的情况下引发异常,php,wordpress,Php,Wordpress,当我激活plugin:SEO Facebook评论代替页面评论时,我得到错误: 致命错误:在第0行未知的堆栈帧中引发异常 然后,当我启用WP_DEBUG时,我得到: ( ! ) Notice: register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPres

当我激活plugin:SEO Facebook评论代替页面评论时,我得到错误:

致命错误:在第0行未知的堆栈帧中引发异常

然后,当我启用WP_DEBUG时,我得到:

( ! ) Notice: register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in C:\wamp\www\wp-includes\functions.php on line 2944
Call Stack
#   Time    Memory  Function    Location
1   0.0005  365640  {main}( )   ..\index.php:0
2   0.0008  369280  require( 'C:\wamp\www\wp-blog-header.php' ) ..\index.php:17
3   0.0013  389656  require_once( 'C:\wamp\www\wp-load.php' )   ..\wp-blog-header.php:12
4   0.0019  405168  require_once( 'C:\wamp\www\wp-config.php' ) ..\wp-load.php:29
5   0.0028  508984  require_once( 'C:\wamp\www\wp-settings.php' )   ..\wp-config.php:92
6   0.2159  24384776    include_once( 'C:\wamp\www\wp-content\plugins\seo-facebook-comments\seofacebook.php' )  ..\wp-settings.php:195
7   0.2205  24806704    SEOFacebookComments->__construct( ) ..\seofacebook.php:594
8   0.2213  24816992    register_uninstall_hook( )  ..\seofacebook.php:95
9   0.2213  24817224    _doing_it_wrong( )  ..\plugin.php:679
10  0.2213  24818200    trigger_error ( )   ..\functions.php:2944
当我检查p行195时:
wp_register_样式('fbSEOStylesheet',$fbSEOStyleURL)

你知道这有什么问题吗,或者我可以从哪里开始调试以发现错误

使用最新版本的WordPress

更新: 当我搜索插件目录时,我找到了register_untilstall_hook的一个实例

register_activation_hook( __FILE__, array( &$this, 'install' ) );
register_deactivation_hook( __FILE__, array( &$this, 'remove' ) );
register_uninstall_hook( __FILE__, array( &$this, 'remove' ) );
更新2:
我能够修复以下错误:但我仍然在评论部分得到原始错误。有什么想法吗?

很抱歉,我没有答案,但是你可能想试试Disqs插件,它包括facebook集成。不幸的是,社交媒体API总是在变化,这类事情通常需要大量维护。