Google to discontinue ability to downgrade Google Forms

I knew the day would inevitably come when Google Forms could no longer be downgraded.  Based on a recent Google announcement, that day appears to be August 22, 2018 – very soon.  Almost certainly too soon for me to do anything about it in the plugin.

As I have noted in a number of posts and in many WordPress Support Forum threads, the change Google made back in 2015 to the HTML used for a form is significant and not well suited to how the Google Forms plugin works.  Instead of using traditional HTML form elements, Google is using DIV tags with CSS class names and Javascript to render a form.

I will take a look at it again but cannot make any promises.  If someone wants to pick up development of the plugin, it is hosted on GitHub and we can figure out how to add another developer for the plugin repository.

This announcement from Google does not bode well for the future of the Google Forms plugin.  The last time I looked into supporting the new version of forms I determined it was a non-trivial amount of work and I wasn’t even sure it was possible.  It is a fair amount of work just to get a new form to render in WordPress before I can even see what happens when it is submitted.

I know this isn’t happy news for a lot of people.  This effort started as a simple plugin to help the middle school my children attended collect some information from parents.  It has grown to 20,000+ installs, far larger than I ever expected.

For those who wonder how much has been donated over the years, the total is probably about $100.  I received a donation yesterday for the first time in roughly six months.  I didn’t write this plugin to make money (there isn’t much to make), I did it because I had a problem to solve and couldn’t find a solution.  I decided to share it because I thought it was useful and it seemed to be but I am afraid its longevity may have come to an end.

If it rains all weekend here in North Carolina like it is supposed to, I may have some time to start looking at this but I no longer have a personal use for the plugin.  My kids have all grown and I have moved on from all of the volunteer activities I used it for (mostly school and sports teams).

I don’t simply want to walk away and leave people, particularly those who use it to support their business, in a lurch but please understand, there may not be much I can do.

WordPress Google Forms v0.94-beta-1 available

I have just posted a beta build (v0.94-beta-1) of WordPress Google Forms.  This build introduces a new solution for calculating the CAPTCHA.  There have been a number of concerns about the use of the PHP eval() function and recently, an alternate solution has been posted to the WordPress Support Forum.  I have adapted the proposed solution to the plugin.

This build also addresses a concern about possible security issue with the user-agent string stored when logging submissions.  It is technically possible for a malicious user to encode the user agent string with malicious code.  This update ensures that data is sanitized before storing and presenting it.

Google Forms Beta (553 downloads)

Google Forms v0.90 RC1 available

I have addressed what I hope is the last of the security concerns with Google Forms and resubmitted to WordPress.org for approval.  In the meantime, should anyone want early access to the next update, which includes some additional debug features as well as addressing the security concerns, you can download it here.

You can also find the current development version on GitHub.

Google Forms Beta (553 downloads)

EDIT:  Due to forgetting to update the stable version tag, the version is now v0.91.

Email Users v4.8.5-beta-4 available

This afternoon I posted beta-4 of Email Users v4.8.5.  This build adds some additional debug information to help chase down slow database queries.  When in debug mode, Email Users will now report information about the query like this:

<!-- email-users.php::1391 -->
<!-- email-users.php::1410 Query #1 Memory Usage: 15.75M -->
<!-- email-users.php::1415 Query #1 Execution: 0.30101704597473s / 301.01704597473ms -->
<!-- email-users.php::1410 Query #2 Memory Usage: 20M -->
<!-- email-users.php::1415 Query #2 Execution: 0.29001688957214s / 290.01688957214ms -->
<!-- email-users.php::1410 Query #3 Memory Usage: 24.5M -->
<!-- email-users.php::1415 Query #3 Execution: 0.201012134552s / 201.012134552ms -->
<!-- 1282 -->
<!-- email-users.php::1448 -->
Email Users Beta (529 downloads)

Email Users v4.8.5-beta-3

This morning I uploaded another beta (beta-3) build of Email Users v4.8.5.  This build addresses an issue with the mailusers_update_custom_meta_filters action not being applied to User Email (it was only applied to Group and Notificationemail).  This problem was reported in the WordPress Support Forum about a month ago.

Email Users Beta (529 downloads)

Email User v4.8.5-beta-2

This evening I uploaded another beta (beta-2) build of Email Users v4.8.5.  This build addresses an issue with the user’s email preferences not being respected when using a custom meta filter.  This problem was reported in the WordPress Support Forum a few weeks back.

Email Users Beta (529 downloads)

Email Users 4.8.5-beta-1 Available

I’ve posted Email Users v4.8.5-beta-1 for testing purposes.  This is a minor update which restores functionality which was removed in 4.7.1.  See this recent thread and this old 4.7.1 thread on the WordPress Support Forum for more details on the change in 4.7.1.

The change in 4.8.5 introduces a new option (Send User Exclude Role) on the Settings page which is enabled by default to retain the current functionality.  When turned off, the user’s current role is also included in the list of roles presented as potential recipients.

Please provide any feedback ASAP as my window to fix this over the holiday break at work is small.

Email Users Beta (529 downloads)

 

WordPress Google Forms v0.88-beta-1 available

Last week I was notified my Google Forms plugin had a potential security flaw and would be de-listed from the plugin repository until addressed.  I have implemented the fixes recommended by the WordPress Security Team and am in the process of getting the plugin listed again.

I would like to enlist some additional testing besides my small suite of test cases with the updated code.

Google Forms Beta (553 downloads)

Let me know ASAP if you encountered any issues with this beta release of the plugin.

Where did Email Users go?

A week ago (July 19th) I was contacted by WordPress regarding a potential security flaw in Email Users. Email Users was “closed” (which is why it doesn’t show up at WordPress.org) until the security flaw was addressed and a new version of the plugin was tagged and release.

Due to some work issues, I did not have a chance to work on the plugin until this past weekend.  I have resolved the security concerns, committed all of the changes, and tagged a new release.  On July 26th (Sunday) I notified WordPress.org that everything (I know of) has been addressed.  At this point, I am waiting for the plugin to be opened again or notified that I’ve missed something.

I’ve uploaded v4.84. to my web site in the event anyone wants to download the update before WordPress.org makes it live again.

Email Users (381 downloads)

Google Forms development moved to GitHub

I have been toying with idea of moving development of my Google Forms plugin over to GitHUb for a while and I finally did it. Using the process outlined here, Google Forms development can now be found here. I’ve already made a few changes and pushed them into the WordPress Subversion repository from GitHub.

I’ve started looking at supporting the new version of Google Forms. What Google has done is so significantly different than prior versions that I am not if it will be possible. Google has stopped using standard HTML input elements and instead is using DIV elements with CSS classes and Javascript to handle the form. I can’t think of a technical benefit for Google to do what they did but it is their product and they can do as they see fit.

If someone wants to fork Google Forms and work on this, you are welcome to do so.