Fatal error when trying to deactivate the plugin

Thanks for this.

From the looks of it, this is actually going to be an edge case, to a certain degree. We try to do some cleanup of some saved notification settings. However, in this case, we don’t have an object like expected, because we never got to the point of setting certain parts up, thus we get this error. Since it only occurs on the deactivation routine from WordPress’ API, I may not have caught this at some points during some testing.

Going to file an issue for this to harden up our deactivation routine.

In the meantime, it sounds like, from your last comment on the review, that you’re going to check on 3rd party solutions for the moment. This does help make the plugin better, regardless, so I do appreciate the support thread with the error involved.

Was re-reading the initial review you left, and I realized I missed addressing the following point:

“…on another site, it prevented all access to pages and posts(!)”

Was curious if you were willing to elaborate on that one at all.

I can’t give you any technical details, but basically, what happened was: I did a fresh install of WP, installed a bunch of plugins including CC’s, and whenever I clicked on a post, page, or “add new,” it would take me to a totally blank page. This was on Twenty Seventeen. When I deactivated the plugin (deactivation wasn’t an issue on this site), things went back to normal.

Noted. Sounds like a PHP error coming from somewhere. We’ll leave it at that though, since I’m sure you’ve moved on and made progress getting the site set up as needed.

Thanks for the feedback. ??

I am also encountering a similar issue when attempting to deactivate the plug-in, this time on a custom theme. I receive the same error message:

Fatal error: Call to a member function delete_dismissed_notification() on a non-object in /nfs/c10/h07/mnt/177206/domains/cgt.columbia.edu/html/wp-content/plugins/constant-contact-forms/constant-contact-forms.php on line 318

@cw2847, it’ll be fixed in the near future, but you should be running PHP5.4+ for the rest of the plugin. It’s not going to be a theme-related issue, to be honest.

Marking resolved as this will be fixed in version 1.2.1.