Plugin doesn't reactivate after update

R u update wordpress or contact-form-7 plugin?
Anyway try this, first delete that plugin and install it once again then activate it.

I updated the contact form 7 plugin. I already tried that and even cleaned my cache options.

It didn’t work.

deprecated.php is no longer used and should not require by settings.php. Because of any unknown reason you still have the old settings.php in your plugin folder-

Make a backup of the form you are currently using and delete the plugin folder /plugins/contact-form-7 completely and manually via ftp.

Doing a new plugin installation will do the trick than.

@takayuki Miyoshi can you assume what happened here?

same problem here! I try to reinstall it but nothing happens. I will try to remove the folder.

Ok, please provide feedback if that works.

I had exactly the same problem. Fixed by completely removing the plugin and installing it again.

Didnt work the folder delete. I have my wordpress blot to openshift. Every time i try to activate the plugin i get this error message

Warning: require_once(/var/lib/openshift/123/app-root/data/plugins/contact-form-7/includes/deprecated.php): failed to open stream: No such file or directory in /var/lib/openshift/123/app-root/data/plugins/contact-form-7/settings.php on line 4 Fatal error: require_once(): Failed opening required '/var/lib/openshift/123/app-root/data/plugins/contact-form-7/includes/deprecated.php' (include_path='.:/var/lib/openshift/123/app-root/runtime/repo/lib:/var/lib/openshift/123/app-root/runtime/repo/libs:/var/lib/openshift/123/app-root/runtime/repo/libraries:/var/lib/openshift/123/app-

remove the old plugin folder via FTP
NOT with the wordpress delete function.

but when i remove the plugin i see through ssh that there is no any folder to the plugins

no folder /plugins/contact-form-7?

Than you should not get this message when you install cf7 3.9

Edit: Do you have any APC or other cache running?

Delete them and than install the 3.9. I suppose it is a cache issue than.

That’s exactly what I did and solved my problem. It was a cache issue.