Hi,
On the homepage of the site deblauwebok.nl the widget does not appear (facebook like box).
Can you help me in solving this problem?
thnx,
sazzkia
Widget on homepage does not appear
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hello,
Yesterday I send you the question above. Something strange is happening.
Because there is an error somewhere in the website, we use http://www.design-inbeeld.nl/blauwebok temporarely as basic website.
The homepage and the widgets work on that part of the server.
When I type http://www.deblauwebok.nl I do not see the right widget.
Is there an explanation to this?
thnx in advance,
sazzkia
Hi Sazzkia
Sorry to hear about the hassle. Everything seems normal on my side now. Did you manage to resolve the problem?
Hi Andrew,
In the meantime we changed WP back to 4.2, then the widget on the right hand side appears. Also the actual website deblauwebok.nl is now active and working properly.
When using 4.3, the widget disappears. When there is no other way in the future to upgrade to 4.3 or 4.4 we will have to use an other plugin for the facebook feed.
Thank you for ur time.
Sazzkia
Thanks for the feedback. So to confirm, the only issue you’re having is that your Facebook widget stops working when you upgrade? Are you using a plugin for the widget? If so, what’s the name of the plugin? I’ll run a quick test on my side. Thanks :)
Hi Andrew,
That is correct, the plugin that is used is: easy facebook likebox by Sajid Javed
https://jwebsol.com/custom-facebook-feed-demo/
I will hear from you,
bye
Same plugin?
https://wordpress.org/plugins/custom-facebook-feed/
Hi Andrew,
Sorry, the link I send you is the link to the author.
This is the plugin:
https://wordpress.org/plugins/easy-facebook-likebox/
bye
The plugin seems to work fine in Page Builder and normal widget areas in WordPress 4.3. I have this plugin, Page Builder and the Widgets Bundle activated. If you upgrade and then run into issues it’s worth doing a plugin conflict test and that might be the problem.
thank you Andrew, we will try it in the next few weeks.
For sure :)