WPIntell

Source evidence

2.5.0 breaks my website

Social LikeBox & Feed · support · 2018-01-06T16:35:00+00:00

Social LikeBox & Feed plugin evidence original source source API
mixedsentiment
highseverity
0.95relevance
12replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 17 rows with source links

29.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

12 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
wshosted resolved
The new uopdate left several of my sites with 500 errors. I have found this error message. Reverting back to 2.4.9 solves the issue. PHP Fatal error occurred: require_once(): Failed opening required ‘facebook-by-weblizar-widgets.php’ Help me to revert, does the same thing to my site. Can anyone explain how to fix this Facebook widget problem? “require_once(facebook-by-weblizar-widgets.php): failed to open stream: No such file or directory” Where can we find a working version? Here… http://wpplugindirectory.org/facebook-by-weblizar/ And how to fix it? I cant even log in wp-admin? Anyone? Had some problem the last minutes. You need access your ftp website content Navigate to WordPress_Secure_Mode_01/wp-content/plugins and rename the plugin facebook-by-weblizar to a different name e.g. facebook-by-weblizar_deactivated Immediate your website will run. Than restore the plugin from your backup data This reply was modified 8 years, 4 months ago by andreaswdk . Mine to, have replaced it with Smash Balloons plugin . The plugin is missing file facebook-by-weblizar-widgets.php. Until it’s fixed, you can either use older version 2.4.9 or comment out the line 48 inside the file facebook-by-weblizar.php, ie. change the line to //require_once("facebook-by-weblizar-widgets.php"); Hi We are fixing this bug and fast updating this plugin please continue with us. Thanks. Dear User, Apologies for the version – 2.5.0 We have just fixed the code and please update your plugin version 2.5.1 . And I request you to keep it using further. Thanks Please test your updates more extensively in future. v 2.5.2 seems to have solved the issue. thank you.

Comments

12 shown
timppatoy 2018-01-06T19:11:00+00:00

Help me to revert, does the same thing to my site.

deekey1 2018-01-06T19:25:00+00:00

Can anyone explain how to fix this Facebook widget problem?

valley-forge 2018-01-06T19:30:00+00:00

“require_once(facebook-by-weblizar-widgets.php): failed to open stream: No such file or directory” Where can we find a working version?

valley-forge 2018-01-06T19:32:00+00:00

Here… http://wpplugindirectory.org/facebook-by-weblizar/

deekey1 2018-01-06T19:47:00+00:00

And how to fix it? I cant even log in wp-admin? Anyone?

andreaswdk 2018-01-06T20:50:00+00:00

Had some problem the last minutes. You need access your ftp website content Navigate to WordPress_Secure_Mode_01/wp-content/plugins and rename the plugin facebook-by-weblizar to a different name e.g. facebook-by-weblizar_deactivated Immediate your website will run. Than restore the plugin from your backup data This reply was modified 8 years, 4 months ago by andreaswdk .

Corneloues 2018-01-07T16:59:00+00:00

Mine to, have replaced it with Smash Balloons plugin .

kuuba 2018-01-08T02:10:00+00:00

The plugin is missing file facebook-by-weblizar-widgets.php. Until it’s fixed, you can either use older version 2.4.9 or comment out the line 48 inside the file facebook-by-weblizar.php, ie. change the line to //require_once("facebook-by-weblizar-widgets.php");

weblizar_support 2018-01-08T04:56:00+00:00

Hi We are fixing this bug and fast updating this plugin please continue with us. Thanks.

Weblizar – WordPress Themes & Plugin 2018-01-08T06:09:00+00:00

Dear User, Apologies for the version – 2.5.0 We have just fixed the code and please update your plugin version 2.5.1 . And I request you to keep it using further. Thanks

Paul Scollon 2018-01-08T06:20:00+00:00

Please test your updates more extensively in future.

wshosted 2018-01-08T14:20:00+00:00

v 2.5.2 seems to have solved the issue. thank you.