Hi @Colin could you confirm if you tried Bart's fork? if so, any feedback pls?
Thanks
1 Like
Colin
2 October 2022 13:33
43
No, I haven't tried it, just confirmed how to install it.
2 Likes
Frida
2 October 2022 14:56
44
I only update manually when I have made changes. And that's only on a hobby basis.
2 Likes
Ah, you are talking about running the backup routine that's shown above , and using the updated dropbox node.
That's good to hear, thanks for the feedback.
I’ve been using it for quite some time and it works perfectly. The only hiccup I had was with it downgrading when I did an update to my Rpi but once that was sorted it’s been churning out backups on the daily for weeks now. I even had to use one a few weeks ago to fix something I broke.
1 Like
For those following this topic, I have created the pull request yesterday:
node-red:master ← bartbutenaers:master
opened 10:25PM - 02 Nov 22 UTC
## Types of changes
Starting from September 30th 2021, all the new Dropbox acce… ss tokens are only 4 hours valid and then they expire. Instead of entering once the access token in the node's config screen, we should generate a refresh token. That can be done by having the user to allow (in a popup window) the node to access the API of the Dropbox app (via an oauth2 authorisation flow). That refresh token will be infinite usable, i.e. it will never expire. As soon as a short-life access token expires, the long-life refresh token will be used to generate automatically a new access token. Then that new access token can be used to access the API of the Dropbox app.
This pull request has been discussed on Discourse (see [here](https://discourse.nodered.org/t/refresh-tokens-in-node-red-node-dropbox-pr-proposal/65610)).
- [X] Bugfix (breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
## Proposed changes
As discussed, the "Access token" field has been replaced by a "Refresh token" field. Which means that users that own an old access token (which is currently still infinite valid), won't be able to use that token anymore. Because if we would keep the "Access token" field, this would become confusing for users with refresh tokens: because the short-live access token would be renewed automatically continiously under the cover, but never be available in the "Access token" field on the screen.
As a result, this will be a breaking change. Therefore we have decided to bump the version number to 2.0.0.
Based on the feedback from the users, there are currently two (known) limitations:
1. The redirect url should be https, unless localhost is used.
2. The redirect url should have the same hostname as the one used to access the Node-RED flow editor. Which means you can only use localhost in the redirect url, if you use localhost to access the flow editor. Which is only possible if the browser is hosted on the same server where Node-RED is running.
A [diagram](https://discourse.nodered.org/t/refresh-tokens-in-node-red-node-dropbox-pr-proposal/65610#description-of-the-implementation-3) is also available on Discourse, which visualizes the design of this pull request.
## Checklist
- [x] I have read the [contribution guidelines](https://github.com/node-red/node-red-nodes/blob/master/CONTRIBUTING.md)
- [x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
- [ ] I have run `grunt` to verify the unit tests pass
- [ ] I have added suitable unit tests to cover the new/changed functionality
4 Likes
For info, node-red-node-dropbox has now been updated to v2
The update is a breaking change, as it uses the latest dropbox api as described in the first post in this topic, and should mean that now dropbox is a viable option for node-RED users to store their data.
Many thanks to @BartButenaers for his patience and time in creating this important update.
5 Likes
system
23 January 2023 18:43
50
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
