nickd32

+1 for this. I have commented inside the GitHub issue you referenced above. Thanks Hugh!

For what it’s worth, we ran into this exact same issue with WP Engine, and here’s how they fixed it. Hope this helps any WPE users…

… the issue occurring was due to the configurations we apply to all of our servers, we have Nginx as the first line being hit, thus rules setup via the apache directive .htaccess or ones that aren’t set to nginx process differently. I have applied the Nginx rule on our end to process the redirects for the path ^/podcast-download/:

location ~* ^/podcast-download/ {
proxy_pass https://localhost:6776;
}

Actually just answered my own question. Default attributes are already built in. w00t!

Maybe put it up on GitHub for users to fork? I agree that a simple mechanism to include parameters other than the defaults would be ideal.

[wp_list_categories tax=”foo”]

OK, here’s my new fix. This gets a little more tricky, since now the comment code is in a separate PHP class.

Place this in your functions.php file:

add_action( 'wp_head', 'fix_fb_comment_placement' );
function fix_fb_comment_placement() {
	$priority = apply_filters( 'facebook_content_filter_priority', 30 );
	remove_filter( 'the_content', array( 'Facebook_Comments', 'the_content_comments_box' ), $priority );
}

Place this inside your comments.php file (or wherever you want the FB comments box to go…)

<?php //Added for Official FB plugin
    $fb_comments = new Facebook_Comments();
    echo $fb_comments->the_content_comments_box();
?>

I decided to turn comments on/off based on whether regular WP comments were on for a particular post:

<?php if ( comments_open() ) {
    //Added for Official FB plugin
    $fb_comments = new Facebook_Comments();
    echo $fb_comments->the_content_comments_box();
} ?>

Note that this solution doesn’t work in the new version (1.1.8) of the plugin, as the ‘fb_comments_automatic’ filter has been removed from the plugin.

I had the same issue, and I had to disable it in the Yoast SEO plugin.

(unless there’s another way I haven’t figured out yet).

FYI, it’s also helpful to use the FB debugger tool to check a post’s thumbnail.
https://developers.facebook.com/tools/debug

@lonchbox – I found a cleaner way that only affects the FB comments (and doesn’t disturb the other elements… like buttons, etc.)

First, from the Codex…

It is also worth noting that you may need to prioritise the removal of the filter to a hook that occurs after the filter is added. You cannot successfully remove the filter before it has been added.

The trick is to add a new action hook that occurs after init — so I just chose wp_head, but there is a list of other action hooks you could use.

Here is my code.

add_action( 'wp_head', 'fix_fb_comment_placement' );
function fix_fb_comment_placement() {
	remove_filter('the_content', 'fb_comments_automatic', 30);
}

Then, in your comments.php file (or wherever you want the comments to show up, include this line of code:
<?php echo fb_comments_automatic(''); ?>

@elmo5 – I found a cleaner way that only affects the FB comments (and doesn’t disturb the other elements… like buttons, etc.)

First, from the Codex…

It is also worth noting that you may need to prioritise the removal of the filter to a hook that occurs after the filter is added. You cannot successfully remove the filter before it has been added.

The trick is to add a new action hook that occurs after init — so I just chose wp_head, but there is a list of other action hooks you could use.

Here is my code.

add_action( 'wp_head', 'fix_fb_comment_placement' );
function fix_fb_comment_placement() {
	remove_filter('the_content', 'fb_comments_automatic', 30);
}

Then, in your comments.php file (or wherever you want the comments to show up, include this line of code:
<?php echo fb_comments_automatic(''); ?>

I just found a similar plugin that gives basic theme usage stats for Multisite, and it works fine (i.e. no 500 errors)

https://www.ads-software.com/extend/plugins/wordpress-mu-theme-stats/

I think I’m going to get rid of WPMU Theme Info.

Same issue for me.

I think I found a fix! You can force a manual reset of the options this way…

1. Go to the Network Settings >> New Blog defaults page

2. In the URL at the top, add &reset=1 to the end of the link, so it looks like this screenshot:
https://cl.ly/1I2F2Q1q2X3R101h3t2c

3. Hit enter, and that should reset all the default options for you. From there, you can make your changes and hit save.

It works for me now. Hopefully it will work for you too.

Add me to the list as well.

Expected behavior = Expect settings to save in the DB when we click save

What am I experiencing? –> click save and then refresh the page and nothing saves

Yes, I had to revert back to my old version too. I think the plugin author neglected to add this fix in with the new version.

FYI – adding that code to the <head> section worked great!

Here’s my final version, modified per @ravanh ‘s suggestion.

https://pastebin.com/5srPv35b