I’m having a similar issue. For the time being, it’s probably advisable to disable the Constant Contact plugin by moving the folder from Plugins to a temp folder and reinstalling the older version. I’ll look into this further…
Yeah, it looks like someone foozled line 41 of the file constant-contact-api.php . It’s calling for a file in the admin folder, contacts.php, that doesn’t exist. Oops! Hope they fix this immediately, it’s a dumb mistake that is causing my entire admin dashboard to crash.
I ran into the same issue, looks like they forgot to include the contacts.php file in the new version package.
i downloaded the previous version here:http://wordpress.org/extend/plugins/constant-contact-api/download/, and copied over the contacts.php to the /plugins/constant-contact-api/admin/ folder via FTP.
Doing this is a bit hacky, but seems to fix the issue for the time being —
Thanks @robkane, @nef426. I was able to move contacts.php over from the prior version (looks like analytics-settings.php was missing from the update as well) and got the new version working.
@adambundy,
good catch on analytics-setting.php — I missed that one somehow.
Also, I’m not sure if it’s still in use, but analytics-dashboard.php appears to be MIA as well, I copied it over just in case–
Encountering the same problems. Thanks @robkane and @nef426 for the temporary fixes.
If you copy over those php files, that should fix it and hopefully that’s the only issue with that. Nef is big $$$ for figuring it out quickly.
Same problem will try the fix
Yep same problem and fix
You’ve not packaged this properly Katz potentially 3 files missing doesn’t look like they have changed in this version as your documentation says v2.3. Please try and be more precise with your updates I imagine not many have time to keep patching – We’ve already stopped using your constant contact gravity forms plugin (it opted out some of our new and old contacts making it now impossible to use constant contact to send them emails) – no response on posts in that regard yet.
This is an issue with the WP repository; I’ve changed the stable version to 2.3.7 instead of trunk, and I think it’ll work.
Update: this does work. For some reason, WP.org won’t include all the files using the trunk.
Zach- I am not able to get in as the administrator- I get this message when I sign in; What should I do- thanks
Warning: require_once(/home/content/n/u/t/nutkings/html/wp-content/plugins/constant-contact-api/admin/contacts.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/n/u/t/nutkings/html/wp-content/plugins/constant-contact-api/constant-contact-api.php on line 41
Fatal error: require_once() [function.require]: Failed opening required ‘/home/content/n/u/t/nutkings/html/wp-content/plugins/constant-contact-api/admin/contacts.php’ (include_path=’/home/content/n/u/t/nutkings/html/wp-content/plugins/google/lib/external/google:.:/usr/local/php5/lib/php’) in /home/content/n/u/t/nutkings/html/wp-content/plugins/constant-contact-api/constant-contact-api.php on line 41
@help2day,
You will need access via FTP.
Step 1) Download the previous version at: http://wordpress.org/extend/plugins/constant-contact-api/download/
Step 2) Access your wordpress install via FTP.
Step 3) Copy the following files from the previous version download, to this location in your wordpress install: ‘/wp-content/plugins/constant-contact-api/admin/’
-contact.php
-analytics-dashboard.php
-analytics-settings.php
Once you’ve uploaded those files, it should work.
At least I wasn’t the only one with this issue yesterday. I was locked out of the admin.
Can someone please tell me if there is a way for to get my ‘old’ plugin back for my blog sidebar? A ‘definitely‘ rather than a ‘maybe’ will work?
Thanks.
Perhaps it only me… but I’m unclear whether this problem has been resolved….updating the plugin is still causing the lockout for me… I’ve had to restore the older version to continue using.
Zack–you’ve got such a fine Constant Contact plugin, please keep it working so users aren’t afraid to update and/or are forced to figure out time-consuming workarounds.
Many thanks.
