You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use the Requests Feature that looks still in BETA, and I could not find any upload button to upload a file.
I first created a Request Link, then I accessed that link so that I can give an answer and upload a file.
I could write text, but to upload a file was not possible.
I need to mention that I used the public Password Pusher page for this (pwpush.com).
This is a feature that I was waiting for, please advise on how to make it work.
Currently, I use pwpusher self deployed in Kubernetes. If there are any parametes or ENV vars that I should set, please let me know.
Looking forward to hear from you,
Thanks;
Andrei
The text was updated successfully, but these errors were encountered:
On pwpush.com, to add files to Requests, you have to be subscribed to either Premium or Pro. This mostly due to past abuse with file uploads. But when subscribed, you can attach files to your request and the person who responds can also attach files in their response.
As for self-hosted, I'll move requests feature over to the OSS edition eventually (no ETA as of yet) but when that happens, you will be able to upload files just the same as file based pushes.
Hi @pglombardo,
I tried to use the Requests Feature that looks still in BETA, and I could not find any upload button to upload a file.
I first created a Request Link, then I accessed that link so that I can give an answer and upload a file.
I could write text, but to upload a file was not possible.
I need to mention that I used the public Password Pusher page for this (pwpush.com).
This is a feature that I was waiting for, please advise on how to make it work.
Currently, I use pwpusher self deployed in Kubernetes. If there are any parametes or ENV vars that I should set, please let me know.
Looking forward to hear from you,
Thanks;
Andrei
The text was updated successfully, but these errors were encountered: