Hey all –
Ran into this same issue, and finally figured out a fix. The problem is that the busted version of the plugin improperly modified the “cctm_data” JSON block (option_value) in the wp_options table (*note: table name may differ, if you’re using a custom or random db table prefix)
So IF you happen to have a database backup from before this unfortunate incident, then restore it somewhere else other than your production environment (personally, I copied the raw MySQL files for the db in question to my local machine, and added them to my local MySQL install – but don’t restore the db to your live website, or you’ll lose ALL updates to your website since that backup!!), and do a search in your “wp_options” table for the option_name of “cctm_data”. Grab the “option_value” contents (a large JSON block) from that entry. Then go to your production environment, lookup the same value and replace the contents with the block you recovered from the backups.
And that should fix things in the admin.
Note that I believe that it shouldn’t matter how long ago your database backup was made – as long as you haven’t changed the custom content types / fields that you’d previously declared since the backup in question was created.
…and if you have no backups of your website – then that’s a whole other problem in and of itself… but it’s probably possible to hand-reconstruct the proper entry from the existing (bad) one. I’ll leave it to the author or someone else to figure that out, though, if that’s really needed by someone.
Hope that helps!
twykr.