Forums

Hi,

Two weeks ago and without touching the backend form we started to receive this message on the front end when users submitted the form which then transfers the data to the google drive spreadsheet.
​
Warning: Invalid argument supplied for foreach() in /home/swissval/public_html/administrator/components/com_chronoforms5/chronoforms/actions/gsheet_save_gh/gsheet_save_gh.phpon line153
​
Now no data is transferred but the form is working as expected and I am hoping you might know what could be causing it.
​
I know google likes to change the security every so often, but I've not seen this error before.
​
Anything you can do to help is very welcome.
​
Many thanks
​
James

got emailed this recently:
​
Hello Google Drive Developer,

We have identified you as a Developer who has used the Drive API in the last 30 days. We are writing to let you know that on September 13, 2021, Drive will apply a security update that will change the links used to share some files, and may lead to some new file access requests. Access to files won’t change for people who have already viewed or modified these files.

Please update your code as detailed below before September 13, 2021, to avoid failing requests.

What do I need to know?
Items that have a Drive API permission with type=domain or type=anyone, where withLink=true (v2) or allowFileDiscovery=false (v3), will be affected by this security update.

In addition to the item ID, your application may now also need a resource key to access these items. Without a resource key, requests for these items may result in a 404 Not Found error (See below for details). Note that access to items that are directly shared with the user or group are not affected.

Will this change affect me?
If your application uses the Drive API to access files which have been shared with a user through link sharing, your application may be affected by this change.

What do I need to do?
To avoid errors accessing files, you must update your code for accessing files to include the appropriate resource keys. Details on how to do this for each of the affected Drive APIs is included below:

Changes to the Drive API
The resource key of an item is returned on the resourceKey field of the file metadata in the Drive API response.

If the file is a shortcut file, then the resource key for the target of the shortcut can be read from the shortcutDetails.targetResourceKey field of the same resource.
URL type fields such as exportLinks, webContentLink, and webViewLink will include the resourceKey.
Requests to the Drive API can specify one or more resource keys with the X-Goog-Drive-Resource-Keys HTTP request header.
Learn more about this change from the Drive API guide.

Changes to Apps Script
The DriveApp from Apps Script has been updated to return the resource key of a file or folder with the getResourceKey method.

Note: When fetching a file or folder, the resource key can be specified on the getFileByIdAndResourceKey or getFolderByIdAndResourceKey methods.
Changes to Drive UI Integrations
If your application is integrated with the Drive UI to create or open items, it will receive resource keys when your application is invoked from the Drive UI.

The state information for a New URL will contain folderResourceKey, which is the resource key of the folder where the new item should be created.
The state for an Open URL will contain a mapping of file ID to resource key in the resourceKeys field.
Learn more about integrating with the Drive UI on our website.

Which projects may be affected?
Your projects that have used the Drive API in the last 30 days and may be affected by this change are below:

xxxxxxxxxxxxxxxxxxxxxx
To get help with these changes, see the Drive API support options on our website.

Thanks for choosing Drive API.

Sincerely,

The Google Drive Team

Hi James,
​
The Google Email says that those changes apply from September 13 so they should not be the cause of the Warning.
​
The code round line 153 is getting a list of worksheets so maybe something has changed here. Line 153 is the foreach line:
​

    // get list of worksheets
    $url      = "https://spreadsheets.google.com/feeds/worksheets/$fileId/private/full?alt=json";
    $method   = 'GET';
    $headers  = array("Authorization" => "Bearer $accessToken");
    $req      = new \Google_Http_Request($url, $method, $headers);
    $curl     = new \Google_IO_Curl($client);
    $results  = $curl->executeRequest($req);

    // look for the specified worksheet
    // and get it's ID
    $wsheets  = array();
    $results  = json_decode($results[0], true);
    foreach ( $results['feed']['entry'] as $e ) {
      $wsheets[$e['title']['$t']] = $e['link'][0]['href'];
    }

​
It's a few years since I wrote this add-on for CFv5 and I'm no longer familiar with the code :-(
​
Bob

Hi Bob,
​
Thanks so much for coming back to me.
​
I'm not aware anything changed in the spreadsheet and tried to set up new spreadsheet in case, still no joy. I'll have another go with a test form and report back.
​
Something that has change I understand is the change from .p12 to JSON.

You can no longer download .p12 file. So i'm wondering if that's part of it.
​
I have no developer skills so am unable investigate myself really.
​
Kind regards
​
James

Hi James,
​
We are travelling today, I'll try to take a look once I'm back at a desk.
​
Bob

Thanks Bob. Looking forward to hearing from you

Ran the debugger and it returned this:
​
​

Array
(
    [GSheet Save [GH]] => Array
        (
            [0] => Worksheet GSheet not found
        )

    [25] => Array
        (
            [GSheet Save [GH]] => 404

Like you said it cannot find the worksheet, but it is there and nothing has changed. So I am wondering if it is that Google has changed the authorisation that is stopping it from seeing the worksheet.

Hi James,
​
Sorry for the delay - it's been a busy few days and I'm just about to go off for a hospital appointment.
​
After searching around I have found this page which says that Google updated their APi to v4 and withdrew v3 on 2 Aug 2021. Hopefully this will provide enough guidance to update the code.
​
Bob

Hi Bob,
​
Thanks for taking the time to find this article.
​
I have had a read and there are changes needing to be made to the code it seams but this is way over my head.
​
Will you be planning on making the changes at anytime soon?
​
Kind regards
​
James

Hi James,
​
I'm afraid that it is unlikely that I'm going to put time into updating this in the near future. CFv5 is old, and VAT rules mean that I can no longer sell it.
​
Healyhatman here has an extension for CFv6 and Max has built an Action into CFv7 that both do much the same thing.
​
Bob