Before going through documentation chapters, thanks for purchasing PrivateContent User Data add-on and trusting LCweb!
Each field index is unique and cannot be changed. If you delete a custom field also user's related data will be lost.
They follows worpress "sanitize title" scheme. Then can have only latin characters and dashes/underscores.
It's a boolean selector. Then only yes/no option.
You can also choose to show it in disclaimers box: will be placed at the end of forms, detached from the rest.
Be careful with this: only english format is supported: with dot splitting decimals! (eg. 15.6 and not 15,6)
By default values are allowed from 0 to 100. You can also use floating numbers to target a specific range.
This advanced method allows you to extend data validation using regular expressions. Will paass through PHP preg_match() function, use a valid format!
Displays a default text on text and textarea fields. Is useful to help users fill in the form.
Checking the option, field will be added in users list. You can sort them using the related tool on the left
Datepicker is automatically added to date fields in both backend and frontend.
If you are using a custom style for PrivateContent forms, a new option let you decide between light or dark datepicker theme.
From v5.0 PrivateContent changed its form builder layout but things are identical. Just use fields dropdown and you'll see custom forms.
Introduced in v2.3, allows you to override the default message in case of successfull form submission
Introduced in v2, this field allows you to set a page/url where users will be redirected once form has been successfully filled and data saved
User Data add-on integrates with another LCweb's add-on, Mail Actions. Going into its settings panel you'll be able to enable this notification system.
Basically you can inform admins when an user updates its data.
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:
Custom forms are visible only by logged privatecontent or Wordpress users.
Wordpress users wil be able to fill the form to test it, but no data will be saved.
Remember that "greater" and "lower" condition only work with numeric data.
While "contains" will search for at least a correspondance in user's data.
You can force users to reset their passwords. This is an extra security and privacy measure.
In PrivateContent settings (main tab), there are two new fields.
First one defines the top warning text and the second one requires Mail Actions add-on and defines whether to force users having requested a password reset.
You will be able to enable the system in "edit user" page and use it during users import.
Users forced to update their passwords will be promped by a modal lightbox in every website's page.
They can't navigate on the website unless they perform the reset.
Once custom fields have been created, you can import user data creating a proper CSV.
Basic structure is the one explained in PrivateContent documentation, then you can import which fields you want.
As first you must use the interface to add fields and select data to import for each row
Count starts from 7, columns before are occupied by standard fields. In this image:
CSV structure must reflects this setup: custom fields are not mandatory, you can leave them blank for some user for example but must reflect data type and validation.
For example if "test select" requires a number with maximum length of 2 digits, you can't import a value like 100.
A validation is performed before creating any user. At the moment is not possible to import multiple values in case of checkboxes fields.
You can also import multiple values for multi-choice fields. In the CSV field they must be split by a vertical line: "|"
The plugin 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, Polylang and qTranslate!
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 folder called "languages".
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 firstname.lastname@example.org sending your .PO and .MO files.
Otherwise they will be lost in next updates. Thanks!