Thanks for your hint. The reason for the problem is the ampersand in the URL, which was not translated correctly on the server when the URL was saved in wp-admin (it does not happend by using WP CLI). I have corrected this for the next release. This should come at the end of the week.
Please note that in your case you are revealing your Google Drive API key by uploading these URLs. You should save such files locally in WordPress by uploading them and not leave them externally. Then there is no risk. At least for images, you can set this in the plugin under Settings > External files in Media Library > Images Settings > Mode for Image handling.
I would like to use the normal Google direct links (without API). Unfortunately, this does not work because the specified URL responds with the http-status 303. The normal Google direct links have the following structure:
https://drive.google.com/uc?export=download&id=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Can you also integrate this?
The URL you mentioned responds with an HTTP status 303 as this is also just a redirect. The plugin does not include any files that generate a redirect. Incidentally, Google Drive also forwards a different URL here that you could use. It has this scheme:
https://drive.usercontent.google.com/download?id=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&export=download
where the x’s must be replaced by the file ID. This works for me without any problems (possibly only after the fix I made in my development environment – so try it after the update).
The update has been published. Should now also work better with these URLs.
With the link scheme you suggested, the MP3 files can be linked to the media library. However, it does not work to play this element of the media library with an audio player. So far this only works with the API link.
Unfortunately, this does not work because Google Drive prevents you from integrating your own files via CORS. Unfortunately, this cannot be avoided unless you download the file and integrate it the normal way into the project.
