bill_mcgonigle

here’s a patch to fix it by default:

--- public/templates/default/template.php.bak   2019-08-16 17:21:02.068000000 -0400
+++ public/templates/default/template.php       2019-08-16 17:37:54.600000000 -0400
@@ -1,9 +1,21 @@
 <?php if ( ! defined( 'ABSPATH' ) ) exit; ?>
-<div class="social-feed-main-container" style="width: <?php echo intval( $template_var['width'] ) ?>px;max-width: 100%">
+<div class="social-feed-main-container" style="width: <?php 
+  if( intval( $template_var['width'] ) != 0)  {
+    echo intval( $template_var['width'] ) , 'px';
+  } else { 
+    echo '100%';
+  }
+?>;max-width: 100%">
 <div
 
 id="feed<?php echo intval($id) ?>"
-style="width: <?php echo intval( $template_var['width'] ) ?>px;max-width: 100%"
+style="width: <?php 
+  if( intval( $template_var['width'] ) != 0)  {
+    echo intval( $template_var['width'] ) , 'px';
+  } else { 
+    echo '100%';
+  }
+?>;max-width: 100%"
 data-ajaxlink="<?php echo esc_url( $template_var['ajax_link'] ) ?>" 
 data-facebook="<?php esc_attr_e( $template_var['facebook_profile'] ) ?>" 
 data-fbtoken="<?php esc_attr_e( $template_var['fb_token'] ) ?>" 

It looks like this is because wssf_feed_width cannot be set in the free version but the code assumes there will be a valid value.

• This reply was modified 5 years, 3 months ago by bill_mcgonigle.

I tried again and this is the response I got. Please clarify – Facebook requires the login credentials for my WordPress site for me to to use this plugin?

-Bill

“Thanks for your submission! I reviewed your Action Type, but it did not meet our criteria. The following is a list of changes that need to be made in order for this Action Type to become available to users: Please provide a username/password for me to properly test the ‘publish’ action. 1. I am unable to test this action according to the usage instructions provided. Please include all necessary passwords, test user credentials and links to staging servers that we need to test your action. Please do not resubmit your Action Type for approval until you can consistently publish Actions with all Additional Properties with your Open Graph Test User. Thank you for developing with Facebook, Susan”

From here it looks like the code is fine but the process is buggy. It appears the people who review the Opengraph actions don’t know about the plugin, that it was written by Facebook, and that it has corporate backing. I think we’ll need to wait for the plugin team to sort this out internally.

No, it doesn’t appear that your hosting provider uses the DNS scheme as mentioned above. You shoud probably contact them as only they would know.

Your site resolves back to just104.justhost.com. It’s possible you’d have to add that to the site addresses – I’m not sure how they use that data on the Facebook side.

No, the second domain would be different. Are you using WordPress MU with domain mapping and DNS subdomains?

Apparently. Did you type anything impressive in the “Steps to Reproduce Your Action” section?

I hope the reviewers are ready for a bunch of dopes like me just tying to get some basic WordPress interaction going.

It seems to me that not providing a layer on top of the generic Facebook Apps interface to ease the integration of this plugin is a pre-1.0 design.

Follow-up: I found the version of the action adder that doesn’t ask for an object type under OpenGraph. Maybe the other one only gets presented the first time?

The icon / logo errors went away after I added the wordpress ‘real’ (not domain mapped) DNS name to the site URL’s and re-uploaded the icon on the Basic page and the Logo on the Auth Dialog page.

The reason I got this problem had to do with my MU domain mapping.

If my site’s URL is https://www.example.com, the ‘real’ site is on example.wordpress.myactualdomain.com. The real site name is what facebook sees and needs to be listed in the site URL’s. It’s at least necessary, not sure if it’s sufficient. I have both the real wordpress DNS name and the public DNS name listed now, and it’s working.

Matt, those instructions don’t match the UI facebook is giving me. Can they get updated for the current workflow?

For instance, I can choose ‘publish’ from a pop-up instead of typing it, but if I choose ‘object’ as the type, I get an error suggesting I chose ‘article’. Is this correct?

Then when I try to ‘Submit’ it complains about an icon and logo, which aren’t in the instructions. That part says that they’re both in Basic, but only icon is in basic. Logo looks to be in Advanced, but even though a logo shows up (a copy of my icon) if I submit again, it says I need a logo and icon.

Instructions with the current workflow would probably cut way down on the number of support requests here!

mod_proxy_html will do this if you have apache.

@nuroweb: gosh, I did the same stupid thing. Thanks for posting!