Illia

Hi there! Sorry to bother you with this small ad. Actually we had this dashboard notice with a link to our CodeCanyon page in previous versions of the plugin, now we just changed it to link to Oxygen. This is our good friends and we truly believe Oxygen is an awesome product. That is why we did it. We didn’t have any paid ads in our plugin ever and have no plans to add any in future, although we receive ad proposals frequently.

Sorry again and good luck.

Hi there! Most probably the page has some location restriction or other. Please check this Facebook Help Center post https://www.facebook.com/help/778445532225441?helpref=faq_content

Hi there! It won’t work with the URL you posted. You need to create a page https://www.facebook.com/pages/creation/
Cheers!

Hi there!

Not sure who this is related to the plugin. I can’t see it anywhere on your page.

Hi there!

The 500px is a limit set by Facebook, we just can’t make it wider.

What exact error do you see? What does it say?

When I click the like icon, it change the text to ‘Potvrdi?’ that means Confirm. Then I click this text and see a popup from Facebook with this post where I can confirm it. This is a new algorithm by Facebook, we cannot rely on this in any matter.

Do you see the same error in other browsers and devices? Can you ask anyone else to check if he also see this error?

Hi there! It all works fine on our demo install. Your page is return 404 error, so we can’t check it.

Hi there! Not sure what happens with your website and how the plugin can disable it. Did this happen just after you have activated the plugin? Did it throw any Error or Warning messages?

Please post a full shortcode you have used.

Hi there! This issue is more likely from the Facebook side. Check to see if:

1. Your page is unpublished.
2. You have Age Restriction activated. Any age restriction above 13+ will cause the page plugin to not work.
3. You have Country Restrictions activated.

Any of the above will cause the page plugin not to display. You can find these settings in the General tab in your Facebook page settings.

Here is the message we see when visit https://www.facebook.com/Livonia-Soccer-Club-165911036849246/

Sorry, this content isn’t available right now
The link you followed may have expired, or the page may only be visible to an audience you’re not in.

Thanks @geoffatmm! I am glad you enjoy the plugin.

Hi there!

Yes, there is a sfp_page_plugin() function now.

<?php if ( function_exists("sfp_page_plugin") ) {
	$args = array(
		'url'		=> 'https://www.facebook.com/topdevs.net',
		'width'		=> '',
		'height'	=> '',
		'hide_cover'	=> false,
		'show_facepile'	=> true,
		'small_header'	=> false,
		'timeline'	=> false,
		'events'	=> false,
		'messages'	=> false,
		'locale' => 'en_US'
	);
	sfp_page_plugin( $args );
} ?>

The shortcode to use is [sfp-page-plugin].

No problem @johanna2patricia.

but it is annoying when a plugin stops working correctly after an update

Totally agree.

Hi everyone!

Yes, show_posts is deprecated. You can use timeline=true for shortcodes, there is also new options for events and messages tabs. Use events=true and messages=true if you want those added. Small header option is also available, use small_header=true.

If you check any options under the tabs section, it won’t get saved.

Due to WordPress widgets specific you may need to drag a new widget to your sidebar, even though the old widget have updated UI.

I still don’t understand why the author of this plugin isn’t responding.

get noticed that it’s a free plugin…

Good catch @marties. We do respond to the support threads, but unfortunately not as much as we want to. Mainly because we have a lot of other work to do that we get paid for.

Sorry for any inconveniences.

• This reply was modified 7 years, 7 months ago by Illia.

What did you do to fix it?

I believe this was something with www.ads-software.com servers (cache or something). I have made few commits to the repo with a small readme.txt changes to force WordPress update the plugin .zip file (it used the old v1.4.1 files). This doesn’t help. Then I have created a separate 1.5 tag in the repo to use instead of trunk version. Then after some time it is started to work. Not sure what exactly fixed it.