dropbox-api | A minimal implementation of Dropbox API v2 | REST library

Try selecting the text in Postman and right clicking, then select EncodeURIComponent in the context menu

I think with the Set Value of Variable and Get Value of Variable actions you can achieve what you're trying to do here.

This workflow provides an example of using these. You can set multiple different named variables, and then read and reuse them later. To get this workflow to work properly I had to select Ignore this action's input for the Get step, otherwise it used both the value of example (which was the filename of the file dropped onto the app) and also the output of Ask for confirmation (which was the filename again, so it tried to move the same file to the Trash twice).

When creating a variable you just choose New Variable... from the drop-down menu. You then give it a name, and leave the Value box empty (and it gets set from the Set... action's input).

Once you have a Variable set up you can also drag it into some places (from the Variable section at the bottom of the window), as I've done here to make the file path show up in the Ask for Confirmation action. You can also remove any unused variables by right-clicking on the variable in the Variable section, and choosing Delete exampleVariable

Full steps which I think would complete your full workflow could be:

1. Set Value of Variable first, to store your 'original filename' in variable original (or something), then the parts of the workflow you already have:
2. Duplicate file
3. Convert to to JPEG
4. Scale
5. Remove "copy"
6. Set Value of Variable converted to input
7. Your already-working upload shell script step
8. Get Value of Variable to read converted back in (this should have Ignore this action's input ticked)
9. Move Finder Items to Trash to remove the JPEG file (could be a shell script to delete the file immediately)
10. Get Value of Variable to read original back in (this should also have Ignore this action's input ticked)
11. Your upload shell script step again (to upload this time the original file)
12. Display happy alert message

If I plug in a valid access token and path to the code you shared, and inspect the content of the downloaded file, I see it is:

Error in call to API function "files/download": Bad HTTP "Content-Type" header: "application/x-www-form-urlencoded". Expecting one of "text/plain", "text/plain; charset=utf-8", "application/octet-stream", "application/octet-stream; charset=utf-8".

You can fix that by setting the 'Content-Type' header accordingly in your $headers.

Also, note that the path you supply in Dropbox-API-Arg should start with a /.

(And for reference, you should check the status code to see if the call failed or not.)

Try setting the correct Content-length value:

The Dropbox API /oauth2/token endpoint does not return a new refresh token during the refresh process, nor are there plans to make it do so. The official documentation for the Dropbox /oauth2/token endpoint can be found here.

The Dropbox OAuth Guide is referring to when you call /oauth2/token for grant_type=authorization_code, i.e., when first exchanging the authorization code for a short-lived token and (optional) refresh token. (Apologies the "new" there is misleading. We'll fix that up.)

When you call /oauth2/token for grant_type=refresh_token, i.e., when using a refresh token to get a new short-lived access token, it will not return another refresh token.

Out of the box, you can't. However, the DownloadFile method is quite simple: https://github.com/f4bsch/DropPHP/blob/master/DropboxClient.php#L261

My suggestion is to override this method by creating your own, CustomDropboxClient by extending the used DropboxClient library, then rewrite the file handling logic. It's using the curl library. By setting the CURLOPT_RETURNTRANSFER option, you can retrieve the data without writing it to a file.

This should give you enough hints to start this project. If you need anything, just comment.

Edit crontab file with crontab -e and add the following to that file:

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

I would suggest you to split the task in two sections. First write the files in your server using fopen in w mode. After writings, use another loop for reading the files using fopen in r mode for using in your cURL to upload in the server. Using the same handler for writing and uploading might cause the lagging problem.

You can use curl_multi_init for handling multiple cURL requests asynchronously. Here is also a post on it.