Iptanus File Upload
Front-end file uploads for WordPress
Let visitors upload files from any page, post or sidebar widget — into your Media library, or straight to Dropbox, Google Drive, OneDrive, Amazon S3 or an FTP server.
What it does
A form on any page
One shortcode, or a Gutenberg block. Add your own fields, filter by size, extension or user role, and run several forms in the same post.
Files go where you need
The Media library, a NextGEN gallery, an FTP server or a cloud account. Large files upload in chunks, past the server’s own limit.
You see what arrives
A file browser and activity log in the dashboard, email notifications on upload, and a viewer your logged-in users can see too.
What it looks like
Set-up and reference
- Install the plugin with the WordPress auto-installer, or download the .zip file from wordpress.org and install it from the Plugins section of your Dashboard.Or copy the
wordpress_file_uploaddirectory into thewp-content/pluginsdirectory of your site yourself. - Activate the plugin from the Plugins section of your Dashboard.
- For an upload form, go to Dashboard / Settings / Iptanus File Upload and follow the instructions in Uploader Instances.
[wordpress_file_upload]Or put the shortcode straight into the contents of any page. - For a list of uploaded files, follow the instructions in Uploaded File List Instances instead.
[wordpress_file_upload_browser]Or put the shortcode straight into the contents of any page.
- Open the page in your browser and you will see the upload form, or the list of files.
- View what has arrived from the Uploaded Files item in the Dashboard menu.
- Change the upload directory, or any other setting, from the small edit button at the top-left corner of the upload form.It opens the plugin options in a new window. If nothing appears, allow pop-up windows for your site.
- Full documentation of the plugin options is in the Options section below.
A handy Getting Started guide can be found here.
You can download the free version of the plugin by pressing the FREE version button below, or you can go for the professional version that offers multiple file uploads, captcha and much more by pressing the PRO version button. Professional licences are one-off, and their updates never expire.
The plugin offers many options for the two shortcodes, so that they can be tailored to any requirements. These options are available in the following links:
From version 2.4.1 filters and actions are supported in order to allow programmers to integrate Iptanus File Upload plugin with other plugins, extend its capabilities or perform advanced operations.
A detailed list of the plugin’s filters and actions can be found in this article.
The plugin is translated in the following languages:
- Portuguese
- kindly provided by Rui Alao
- German
- French
- kindly provided by Thomas Bastide of omicronn.fr
- Serbian
- kindly provided by Andrijana Nikolic of webhostinggeeks.com
- Dutch
- kindly provided by Ruben Heynderycx
- Chinese
- kindly provided by Yingjun Li
- Spanish
- kindly provided by Marton
- Italian
- kindly provided by Enrico Marcolini marcuz.it
- Polish
- Swedish
- kindly provided by Leif Persson marcuz.it
- Persian
- kindly provided by Shahriyar Modami chabokgroup.com
- Greek
Translations in other languages are more than welcome!.
The plugin requires to have Javascript enabled in your browser. For Internet Explorer you also need to have Active-X enabled.
Please note that old desktop browsers or mobile browsers may not support all of the above features. In order to get full functionality use the latest versions of browsers, supporting HTML5, AJAX and CSS3.
You can read the Privacy Policy and Terms of Service of the plugin in the following links:
You can also read the Google Drive Privacy Policy and Terms of Service of the plugin in the following links:
Release notes
153 versions · 847 changes
What changed in each version. Grouped by major release — these entries carry no dates.
- Fixed bug where emails could not be sent after the release of the previous version.
- Verified compatibility with latest 7.0 WordPress version.
- Added uploadid length check in wfu_ajax_action_send_email_notification().
- Added wfu_params_*, wfu_gst_* and wfu_userstate_* in periodical cleanup.
- Added Transient Options section in Maintenance Actions tab.
- Fixed SQL injection issue CVSS 9.3 from Patchstack.
- Fixed File Overwrite Race Condition when uploading files with the same filename concurrently.
- Verified compatibility with latest 6.9 WordPress version.
- Fixed bug where a file could not be downloaded from Uploaded Files Dashboard menu.
- Fixed double-escaped HTML code of text when Pro version is deactivated. Pro
- Added support for FTP over TLS (FTPS) uploads.
- Fixed bug where the visual editor of the file viewer could not be invoked when there was no upload form on the same page. Pro
- Fixed bug where alt text and description in NGG image was not stored because NGG modified its API. Pro
- Fixed bug where the visual editor threw warnings for not finding personaldata when Personal Data were deactivated from the plugin's Settings in Dashboard.
- Fixed bug where a fatal error was thrown when updating the Pro version of the plugin and the extensions had to be reloaded. Pro
- Fixed bug where Link and Remotelink columns showed HTML code instead of links, due to excessive escaping. Pro
- Modified Messenger activation workflow due to withdrawal of Send To Messenger plugin from Meta. Pro
- Corrected bug where the upload form visual editor was not opening when Material UI theme was active.
- Corrected bug where notification emails were not sent when Material UI theme was active.
- Updated vendor libraries.
- Removal of Post Method setting from free version.
- Removal of curl_exec, file_get_contents and sockets from wfu_get_request() and wfu_post_request() of free version.
- Improvements on how AJAX endpoint is provided.
- Corrections to "Requires at least" value.
- Replacement of eval() in minification function.
- Corrected warning where translatable constants where loaded before the plugin textdomain was loaded.
- Further security improvements for compliance with wordpress.org.
- Added translation for all backend of the plugin.
- Modified plugin code so that all echoed variables to HTML are escaped.
- Modified code so that all input is sanitized, including all $_SERVER, $_COOKIE and $_SESSION input.
- Plugin name changed to Iptanus File Upload.
Every version on one page, without JavaScript: the full changelog.
Free and Pro
The free version does not expire and is not a trial. Pro adds nineteen features. The full comparison and the price are on one page.
This plugin will be great if I can get it straightened out…
Small uploads work fine up to about 6-7MB. Once I get larger than that, transfers fail. I don’t get a status that it failed, the screen redraws, and it looks like I just loaded the page.
Turning on debug and shutting off every plugin except for WPFU, and using the default 2014 theme on 3.8.1, I get these messages when debug is turned on:
Notice: wp_enqueue_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /var/www/wordpress/wp-includes/functions.php on line 3049 Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /var/www/wordpress/wp-includes/functions.php on line 3049
Notice: Undefined offset: 1 in /var/www/wordpress/wp-content/plugins/wordpress-file-upload/lib/wfu_blocks.php on line 53
Here’s the shortcode:
[wordpress_file_upload uploadpath=”uploads/clients/%username%” uploadrole=”administrator” maxsize=”100″ createpath=”true” askforsubfolders=”true” chunk=”true” debugmode=”true”]
I’ve tried several different options and they all produce the same results. I do have the Pro version.
Any thoughts?
Please remove askforsubfolders attribute, although I do not think that this is the problem. The page should not reload itself. This is not caused by the plugin (or it shouldn’t normally) but it causes the upload script to be interrupted, so upload fails without any error. This means that another script reloads the page automatically after some time. This is probably why small files manage to get uploaded and large don’t.
Is it possible to give me access to the page so that I can try myself and see what happens?
Nickolas Bossinas
http://www.iptanus.com
Check your “info” email. You should have a UID/PW there that will give access. Once in you’ll be at a page that contains WPFU with the following settings:
[wordpress_file_upload uploadpath=”uploads/clients/%username%” uploadrole=”wpc_client,wpc_client_staff” maxsize=”1000″ createpath=”true” chunk=”true” debugmode=”true”]
Got it figured out…Browser compatibility issue.
How can I save settings in shotcode composer
Settings are automatically saved…. do you have any issues with that?
I’m using WordPress File Upload and can’t seem to find a way to make the userdata fields have a nice tabular format. The labels are all of different length and that staggers the data entry fields. Help please!
Shortcode used is:
[wordpress_file_upload uploadpath=”uploads/RawMP3s” uploadpatterns=”*.mp3″ showtargetfolder=”true” askforsubfolders=”true” subfoldertree=”RawMP3s” adminmessages=”true” uploadtitle=”Upload file” notify=”true” notifyrecipients=”itsastretch@dslextreme.com” notifymessage=”Dear Recipient,%n%%n% This is an automatic delivery message to notify you that a new file has been uploaded.%n%%n%File Name:%userdata5%%n%Title: %userdata1%%n%Description: %userdata2%%n%Reader:%userdata3%%n%Project: %userdata4%%n%%n%Best Regards” widths=”filename:200px, selectbutton:80px, uploadbutton:80px, progressbar:190px, message:400px, userdata:400px” userdata=”true” userdatalabel=”Title:/*Description:/*Reader:/*Project:/*File Name:”]
Perhaps you need to do some css styling…. do you know how to do that?
Yes, but I’ve never done it for WordPress and I don’t know where to begin.