Michael Simpson

It was removed due to a security concern. That has largely been addressed. There was a valid vulnerability that I fixed within 24 hours. The rest is more theoretical (you would have to be logged in as an administrator to do it…and if you are an admin, you can do whatever you want anyway). But the WP person won’t re-list until I re-code that.

That code has always been like that way, yet all of a sudden WP yanks the plugin without fully understanding where the safeguards are in the code. I would have preferred that they kept it listed so people get the update that fixes the real vulnerability, then give me some time to change other code to the standard that they want to suddenly impose.

The WP person has been really condescending to me on all the communications and I got fed up with dealing with that. I want clarification on exactly how they want things coded. You would think that the WP people would take a positive attitude toward helping plugin authors keep their plugins up to standards so they can keep contributing to the community (for free!). Instead I’m treated with contempt. I ask myself why should I bother continuing with this?

To reassure you, I plan to get it re-listed at some point. But I have to muster the time and energy to deal with people like this. In the meantime, you can find it on GitHub.

CFDB does not display the form and it cannot control displaying anything on the form. The example makes use of a CF7 hook that allows CFDB to signal that the submission is not valid. But CF7 manages the display of the form. So the question is for CF7: is there a way to signal it to stop displaying a button? I’m pretty sure the answer is no, but you would have to ask CF7 people.

That is a questions for Contact Form 7.

1. Go back to the CFDB Shortcode page.
2. Select your form and set Export to Google Spreadsheet Live Data.
3. Got to Rows tab, set orderby
4. Set any other options
5. Put the newly generated URL into your Google Sheet

That’s very odd. Be sure each form field has a unique name (no duplicates).

I don’t know how this could happen. If the form is received, it should save. CFDB doesn’t know if you are using HTTP or HTTPS. If you site is disallowing HTTP, and the form is still trying to post using HTTP, it will be blocked. Check how the form submits.

I’m publishing releases here now: https://github.com/mdsimpson/contact-form-7-to-database-extension/releases

The WP person is very condescending and unprofessional and is really rubbing me the wrong way. I’m happy to address any issues and meet any standards, but I’m at the limit of my patience. I try to be a good citizen and give back to the community. I’ve put in countless hours for close to seven years now. When I’m treated like this, it seems WP doesn’t value me or my contribution to its community.

Anyway, I put the code on GitHub and I will continue to support it. But at this point I’m not sure I want to deal with people like this to re-list the plugin on this site. I don’t need the frustration.