Before going through documentation chapters, thanks for purchasing PrivateContent Files Manager add-on and trusting LCweb!
To run this add-on you must have installed at least PrivateContent v7.21
Uploaded files are stored into this folder:
Before start using you have to check a couple of server details:
Some servers have got restrictions over file and folders management, requiring FTP/SSH credentials.
Each time you enter the Files Hub page, the add-on checks these permissions.
If it cannot manage files, the warning with credentials form it's shown.
Each server has got a size limit defined by the hoster.
The add-on panel shows it in the "Restricted Files" tab
If it's too low for your needs, you can try asking the hoster for an increase.
By default WordPress supports a wide variety of file types.
However you may need to allow specific file types
The first step to allow frontend file uploads or to directly upload user private files is to create fields
Some notes about fields:
Remember it is expressed in KB and that 1KB is 1024 bytes.
Then to set a 1MB limit you don't have to use 1000 but 1024 value.
As soon as you specify an image file type among allowed ones, the plugin will show specific image size validation fields.
Use a zero value to skip those validations.
This option is essentially addressed to multi-column frontend forms.
By default the add-on will display uploaded files into a single column, while using "full-width" files will be columnized
As soon as you create upload fields, they are integrated into the PrivateContent form framework.
This means you can include them in registration forms as well as in custom forms created through User Data add-on
In the "restricted files" tab you can upload files that will be accessible only by targeted user levels.
To use folders isn't mandatory, you can also just put everything inside the root folder.
However, as good practice, in most cases is better to have a precise folders structure to keep everything clean and easier to be used through time.
Folders can be restricted and subbfolders inherit restrictions.
Obviuosly each file contained in a restricted folder will inherit those restrictions.
To stop che chained restrictions structure, just define a precise restrictions for the subfolder/file.
You can sort & search files as you prefer to better orientate.
The TAGS field could be very important to show targeted files in future: it allows comma split words.
File views are essentially ways to display stored files onto your website.
Turn it on to speed up frontend image's loading.
However it requires server permissions over direct files management: if you face issues loading images, keep it off.
Into the user dashboard > user files, each files has got a "move" icon to reorder files
You have to type one or more search terms (comma split) matching files.
Here you can take advantge of file tags: grouping various files just typing a single word.
The search will ignore folders, grouping any file found
This add-on is also natively integrated with with WordPress Block Editor (Gutenberg), Visual Composer, Elementor and Cornerstone.
Using them, you can skip the standard shortcode wizard and use the related PrivateContent tool.
For any other builder or using the old WordPress editor just open the PrivateContent shortcode wizard and select "PCFM - File Views" from the shortcode's dropdown list.
Select the view you want to show and click on "insert".
Here's a demo shortcode:
Alternatively you can always use the direct file link. It can be copied in each files list table
They can be treated as normal file type links.
Then into HTML image or video (etc.) tags, as well as video players.
Be sure you have the Google Analytics tracking code set in PrivateContent settings.
Each time users will download/see a file, it will trigger a new Analytics event related to that user.
The add-on is 100% multilanguage for both front and back ends. If a translation of your language has been created, WordPress will automatically switch between languages. Plus it is compatible with WPML and Polylang!
If you have WPML + String Translation add-on or Polylang, you can simply scan the plugin and translate strings via its UI.
Otherwise: go in the plugin folder, you'll find a two folders called "languages" and "lang_admin".
Inside you'll find the default.pot file. It contains english strings to be translated.
If you want to create or customize your language translation, follow these steps:
If you create new translations, please contact me at email@example.com sending your .PO and .MO files.
Otherwise they will be lost in next updates. Thanks!