[Plugin: Easy Automatic Newsletter Lite] Update done – fatal error

Can you try deleting the plugin, downloading the version 2.7, uploading the new version, and activating.

Deleted the folder (local and online), downloaded the new version, unzipped it and uploaded it. Then made it all 777.
Push activate version 2.7 and have the same error …

Fatal error: Cannot redeclare class FacebookApiException in /var/www/vhosts/family-oosten.com/httpdocs/blog/wp-content/plugins/easy-automatic-newsletter/facebook-sdk/base_facebook.php on line 107

Some questions:

1. What version of WordPress is in use
2. What plugins are in use right now
3. What version of PHP is in use. Posting a PHP page with phpinfo(); function and giving URL would be great.
4. What version of EAN was in use before? 2.6?

May be reverting back to 2.6 until we get this sorted. Here is a direct link to version 2.6:
https://downloads.www.ads-software.com/plugin/easy-automatic-newsletter.2.6.zip

1] WordPress 3.4.2. (Dutch language version)

2] Akismet
Ambrosite Next/Previous Post Link Plus
BackUpWordPress
Comment Reply Notification
Countdown Widget
Easy Automatic Newsletter
Fast Secure Contact Form
FlickrSlideShow
Follow Me
Lightbox Gallery
Most Commented Widget
MP3-jPlayer
Multiple Galleries
Official StatCounter Plugin
Paulund Disable Pingbacks
Postie
Print Friendly and PDF
PRO Player
RSS Image Feed
Scroll To Top
SEO Facebook Comments
ShareThis
Smart Archives Reloaded
Smart Youtube PRO
Twitter Widget
Ultimate tag cloud widget
WordPress Importer
WP-PageNavi

3] PHP Version 5.2.10 – https://www.family-oosten.com/php_info.php

4]Previous EAN downloaded in march 2012, version 2.0

Have deleted v. 2.7, downloaded & installed v. 2.6
No problems, everything functions as with v.2.0

[Only CronJob doesn’t work since july 2012 – my solution now is to send myself a newsletter (with testmail to specified – that works) and manually forwarding it to the subscribers]

Thanks for posting that information.

Your PHP version is pretty dated. Please upgrade your PHP version to at least PHP 5.3.16. Our server is running PHP 5.3.15 at the moment. If you don’t have access to upgrade PHP or know how to I suggest contacting your host and having them perform the upgrade.

Best Regards,
George

Regarding the cronjob command you can try using the older command that worked for you before.

Try either:

wget -q https://www.family-oosten.com/blog/wp-content/plugins/easy-automatic-newsletter/ean-schedule-newsletter.php > /dev/null 2>&1

Or:
curl -s https://www.family-oosten.com/blog/wp-content/plugins/easy-automatic-newsletter/ean-schedule-newsletter.php > /dev/null 2>&1

Best Regards,
George

I’ve send an email to my host, regarding the PHP-version.

I’ve entered the first suggestion for the cronjob en will test in a week (on saturday), if not working, the second suggestion will be tested in 2 weeks.

This waiting for the crohnjob test has to do that, when crohnjob is succesfull, the ‘counter’ goes back to zero and by saturday there will be blog updates missing in the official newsletter …

Sounds good to me. Thanks for your patience.

Received response from host about upgrading from PHP 5.2.10 to PHP 5.4.7

It’s a point of discussion because of the consequences(?) for some (big) clients. They’ll keep me informed…

Depends on what you have hosted really. If you have a program for example that is using obsolete functions then the programs would fail to work and would need to be recoded to work with latest version.

I still suggest to upgrade PHP. You may want to setup a development server with latest software packages and PHP, install everything on that server, and test. If all goes well then upgrade production server. Otherwise, make whatever corrections necessary on dev server, retest, and migrate changes over to production with the upgrade.

Any word back from the host?

In the meantime the other cause is one of your plugins causing conflict. In order to work with FaceBook we got the latest version of FaceBook API. Another plugin must be using the same API and therefore causing that conflict which shows the error you originally posted.

We are looking into if we can add a check into our copy of FaceBook API to not declare the class above if already declared in another plugin.

I suspect “SEO Facebook Comments” plugin may be causing the issue. Start with disabling that, enable EAN 2.7. If it works then we know that is the root cause of conflict. If not, then try disabling all plugins, enable EAN 2.7, then enable one plugin at a time until you receive a conflict.

Regards,
George