Client side uploads
From Wikanual
You can allow your clients to also upload content via the client interface.
Contents |
Enabling Client Side Uploads
To enable client uploads go to Logins and click on the
enable upload
button you find for the listing. A new upload link will appear on your client facing INTERDUBS pages. Should you want to disable the upload feature again click on the
disable upload
INTERDUBS sends an email notifcation to the people associated with the login when a client upload is done. You can change the format of these mails as described in client upload notification email
Upload only
Client uploads can also be used to set up a dropbox where your clients can NOT see what they or others have uploaded. There is a global look called Upload Only that can be used to turn a login into an Upload only login. See Look#upload_only for details.
Example applications
Client side uploads can be used in a multitude of scenarios. Here some examples to give you an idea how you maybe could adopt this look for your purposes.
Resume / reel submission
You can feature on your public website a link that lets people upload their resumes. Since you use an Upload only look they can not see what others have posted. It is helpful that you can add categories in the form text of the upload. For example can you ask for "contact", "experience" etc.
Having potential employees upload their reels to INTERDUBS is beneficial since you can watch them in the fast context of the systems.
When you can point a second login with normal settings to the same folder then you can use this to communicate internally about the candidates and their work.
Project collaboration
In a project you can create a folder dedicated to material that people deliver to you for a project. Adding a login to this folder that has uploads enabled will allow you easily gather work content.
HTML page for uploads
The look and feel of the client upload pages is being controlled via two configuration settings.
HTML upload body
Similar to HTML content body this controls the html part of the page. HTML header will automatically be prepended. Like its general counterpart it contains a variable called IDXHTML_CONTENT which will be replaced via the contents of:
HTML upload content
This is the form that contains the upload. Outside the usual ones the following keywords are possible here:
IDXHTML_UPLOADF_UPID
A random number needed for the upload progress window
IDXHTML_UPLOADF_IDXCLIENT_ID The numerical ID of the segment to upload into
IDXHTML_UPLOADF_AL the 6 digit ak code that designates the login (CGI variable: al)
IDXHTML_UPLOADF_AN the 6 digit ak code that designates the file (CGI variable: an)
The following CGI variables are being used for uploads:
al type:hidden (see above) an type:hidden (see above) title type:text the title of the file in INTERDUBS, if empty then the file names gets used newfoldername type:text if set a new folder with this name will be created and the file will be put in there. note type:textarea the note that the client can add userfile type:file the input for the actual file
enabling via configuration
Client side uploads are actually enabled via a configuration. You can decide to make all of your segment upload enabled or just specific logins / links.
The following section describes the login/configuration way to enable uploads. See Enabling Client Side Uploads above for a quicker way to accomplish the same.
For a login go to the 
edit login screen and scroll down the configurations. One of them reads:
Disable upload option and it is probably enabled. Click on the 
to bring this configuration under the control of this login and then change the value to NOT being checked any longer.
Clients can not manage the content they have uploaded.
Alternatively use Droplets
You can also consider to send your clients a droplet that you created in INTERDUBS. This is specially interesting since browser based uploads have a size limit of 2GB.
