aendrew

Hi Chris!

I’ve updated the plugin to use array() instead of the square bracket syntax. Thanks for pointing that out!

To update my initial point, the performance improvements added in the most recent releases are utterly brilliant. Like, it’s practically resolved the performance issue I mentioned in my original post. Many thanks!

But yeah, agreed with Marcoevich — the thing that will take this from being “one of the best WordPress layout plugins” to “the sole WordPress layout plugin that everyone immediately installs and the only one that they consider” will be opening up the code to the community and developing it socially. While my experience has been Page Builder’s code is really solid and works amazingly, the designers I work with have complained about a few UX-related issues and it seems having more spheres of talent contributing to Page Builder would only be a positive thing.

This is a misleading and pointless review that is inflating this plugin’s overall rating. Please remove.

Oh, by the way! You might be interested to know that we built our My Year With Malala long form feature entirely using Page Builder; worked really well! Both Buzzfeed and The New Yorker carried links to it.

Though perhaps you can get an idea of why we need so many rows in our layouts…

It seems you have the right kind of OG tags now — the meta ones instead of the ogp.me ones.

If it’s still not working for you, it must be something else — sorry I can’t be more help!

The filters changed last update; the above code should now be:


/**
* Move FB Comments to own DIV.
*/

add_action('wp', 'move_fb_comments', 999999);

function hook_fb_comments_form() {
do_action('the_fb_comment_form');
}

function move_fb_comments() {
$priority = apply_filters( 'facebook_content_filter_priority', 30 );
remove_filter( 'the_content', 'Facebook_Comments::the_content_comments_box', $priority);
add_filter( 'the_fb_comment_form', 'Facebook_Comments::the_content_comments_box', 30);
}

In lieu of an actual option within the plugin to prevent it from duplicating OpenGraph metadata supplied by another plugin, add the following to your theme’s functions.php file:


/**
* OpenGraph stuff is now handled by Yoast or whatever.
* This removes Facebook's broken use of its own technology.
*/
add_action('wp_head', 'remove_fb_og_stuff', 0);
function remove_fb_og_stuff() {
remove_action( 'wp_head', 'Facebook_Open_Graph_Protocol::add_og_protocol' );
}


This is what I did:

a. Install Yoast’s WordPress SEO plugin. https://yoast.com/wordpress/seo/
b. Set up Facebook OpenGraph stuff under wp-admin -> SEO -> Social (wp-admin/admin.php?page=wpseo_social). Make sure to link either app or a valid admin user account.
c. Add the following to your theme’s functions.php file:


/**
* OpenGraph stuff is now handled by Yoast.
* This removes Facebook's broken use of its own technology.
*/
add_action('wp_head', 'remove_fb_og_stuff', 0);
function remove_fb_og_stuff() {
remove_action( 'wp_head', 'Facebook_Open_Graph_Protocol::add_og_protocol' );
}


Et voilà. It’s absolutely ridiculous Facebook’s 1st-party plugin doesn’t follow Facebook’s own API documentation when implementing OpenGraph metatags. Note that this has taken me *ages* to figure out at this point.

This is what I did:

a. Install Yoast’s WordPress SEO plugin. https://yoast.com/wordpress/seo/
b. Set up Facebook OpenGraph stuff under wp-admin -> SEO -> Social (wp-admin/admin.php?page=wpseo_social). Make sure to link either app or a valid admin user account.
c. Add the following to your theme’s functions.php file:


/**
* OpenGraph stuff is now handled by Yoast.
* This removes Facebook's broken use of its own technology.
*/
add_action('wp_head', 'remove_fb_og_stuff', 0);
function remove_fb_og_stuff() {
remove_action( 'wp_head', 'Facebook_Open_Graph_Protocol::add_og_protocol' );
}


Et voilà. It’s absolutely ridiculous Facebook’s 1st-party plugin doesn’t follows Facebook’s own API documentation when implementing OpenGraph metatags. Note that this has taken me *ages* to figure out at this point.

OKAY. Totally have this figured. It’s because of the stupid way this plugin adds metadata. Instead of the way recommended in the API documentation, it tries to use https://ogp.me/ns, which just doesn’t work.

Setting up the app in Yoast SEO makes it suddenly work. Alas, now my pages are returning invalid OpenGraph data because og:url is declared twice. Will try to find some way of removing the OpenGraph filters from this plugin and report back.

+1 on this. I have no errors, and my app ID is coming through in the debugger. I have no idea why this isn’t working.

In retrospect, maybe the plague comparison was a bit rage-y, but ermahgerd, am I sick of trying to troubleshoot this…

Update an hour later: Nope, comment moderation *still* doesn’t work.

Thanks for wasting *hours* of my time, I shan’t be darkening your doorway further. I shall also tell every developer and client I know to avoid your plugin like the plague it is.

Same deal here. To the author — You should really turn debug mode on (and run PHP 5.3+!), you’re getting crazy depreciation errors also (Or at least you are on the site where the plugin still works…).

Augh! You just *had* to go and change how the filters are set up so that the hours of work I spent in getting the comment box to display *below* the content div instead of in it are now wasted, and I must now spend the next few hours redoing that work — nevermind the hours I’ve spent in my failed attempt to get comments to show up in any sort of moderation area.

If once I get this styled again and comment moderation still isn’t working, I’m sorry, but this is going on my blacklist of plugins I tell people to never use — I don’t care how much the client wants the ability to post to its Page’s feed.